Random outpourings of a software developer
This is an article on K2 Roles.
Personally I think that K2 have made a mistake in their handling of AD Groups as destinations.
It seems to upick the group into it’s parts as the Activity is entered. Which is great until a new user joins the team. They can’t perform actions on the item until it has been moved state.
Here is a great article on using the ASP.Net cache outside of web apps.
This is the gist of the article:
private Cache m_Cache;
m_Cache = HttpRuntime.Cache;
I have a colleague to thank for this:
This is blisteringly fast and just works.
use Core
go
checkpoint
go
backup log “Core” with truncate_only
go
DBCC SHRINKFILE ( “Core_log” )
go
use OtherDB
go
checkpoint
go
backup log “OtherDB” with truncate_only
go
DBCC SHRINKFILE ( “OtherDB_log” )
go
Kerberos is what you need to use to solve the “two hop problem”. This happens when a service that is called by a client needs to impersonate the client to another service. NTLM will simply fail to authenticate and the call is made as the annonymous user.
The process of getting Kerberos to work is actually quite simple once you understand a few details.
The concept is that you must have a chain of trust running from the server all the way back to the client.
The client needs to be using Kerberos.
The server needs to be using Kerberos.
The identity of the process running on the server needs to be trusted for delegation if it wants to call another server.
You need to set up a SPN for the called server.
The bug is that the session will only remember the first item copied to the clipboard.
The previous solution was to log off and on again – which is not appropriate for nested virtual machines.
This solution consists of killing and restarting rdpclip.exe.
I am tempted to create a utility that does just that.
declare @text varchar(1000)
set @text = ‘<a firstname=”Joe” surname=”Blogs” >42</a>’
DECLARE @idoc int
select @text
declare @name varchar(10)
declare @name2 varchar(10)
— Create an internal representation of the XML document.
EXEC sp_xml_preparedocument @idoc OUTPUT, @text
— Execute a SELECT statement using OPENXML rowset provider.
SELECT @name=surname, @name2 = [firstname]
FROM OPENXML (@idoc, ‘/a’,1)
WITH ([firstname] varchar(10),
surname varchar(20))
select @name, @name2
SELECT age=[text]
FROM OPENXML (@idoc, ‘/a/text()’,2)
EXEC sp_xml_removedocument @idoc
I recently moved an application from using the Microsoft Enterprise Application logging block to log4net.
This was caused by a problem with WCF and the EAB. There was an odd error that appeared to claim that different versions of the EAB were in use in different locations of the system (they were not!) however replacing it with the much simpler to configure log4net solved the problem. I did add a thin wrapper class so that my code is not tied to log4net.
log4net only requires that you deploy a single dll (compared to the three for EAB) and the configuartion entries are a quater the length (and don’t need a config tool to set up).
Developer Rants 