The Glorious Monster: Fixing BizTalk ENTSSO Failure on Windows Vista

A link back to an incredibly useful post by the Glorious Monster. I encountered this problem after having installed .net4 on our Biztalk server. I advise taking note of Giuseppe Dimauro's comment - if you are running in an x64 environment like ourselves, you need to run regasm from the 'C:\Windows\Microsoft.NET\Framework64\v2.0.50727\' directory

The Glorious Monster: Fixing BizTalk ENTSSO Failure on Windows Vista

My final prompt looked like this:
C:\Windows\Microsoft.NET\Framework64\v2.0.50727>regasm "C:\Program Files\Common
Files\Enterprise Single Sign-On\SSOSQL.dll"

Once again, massive thanks to The Glorious Monster for saving my ass today!

Can't deploy a WCF Service App from Visual Studio into IIS 7

One of the problems i encountered when trying to deploy a WCF Service App was this little doozie:

'Cannot add duplicate collection entry of type 'add' with unique key attribute 'name' set to 'ScriptHandlerFactory''

I got around it by adding the following line into the <handlers> tag of the tag in my web.config file and redeploying:

< remove name="ScriptHandlerFactory"/>
< remove name="ScriptHandlerFactoryAppServices"/>
< remove name="ScriptResource"/>

Also, this line at the BEGINNING of the <modules> tag :

< remove name="ScriptModule"/>

That seemed to fix it for me!

Dude, where are my WCF Data Classes?

I encountered an annoying quirk about the current implementation of WCF today - I created a class which had a data contract, saved, built and published my project and updated the service reference in my client to make sure it had all been deployed properly. On viewing the contents of the service in the object browser, my newly created class was not there! Why?!? The reason is that The data contract is deemed worth publishing unless something is using the thing. So, to get around the problem, i created a function that called used the data class, rebuilt/published and hey presto! it appeared in my list of available classes.