Archive for the ‘Visual Studio’ Category

I believe Visual Studio 2010 was the latest and greatest (compared to VS2008 and prior). Well, after a clean installation of VS2010, as I tried to launch the program I received the following error  (on a dialog box)


SetSite failed for package [Microsoft.Practices.RecipeFramework and a dialog box Object reference not set to an instance of an object

The above doesn’t explain much !. I tried running Visual Studio from a command prompt using the log switch
devenv.exe /log
This logged the activity trace of launching Visual Studio under …\AppData\Roaming\Microsoft\VisualStudio\10.0\ActivityLog.xml

On reading the error log, I noticed the following two lines:

SetSite failed for package [Visual Studio Component Model Host Package]
SetSite failed for package [Microsoft.VisualStudio.Labs.SolutionNavigatorPackage,


… and this time something in the event viewer:

Faulting application name: devenv.exe, version: 10.0.30319.1, time stamp: 0x4ba1fab3
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec49b60
Exception code: 0xc0000374
Fault offset: 0x000c380b
Faulting process id: 0x11f8
Faulting application start time: 0x01cd60b0bd3f8235
Faulting application path: C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 1576fd49-cca4-11e1-8bd9-001cc48a5099


This happens because of Visual Studio is trying to load extensions that do no exist on the machine !.  To resolve this, navigate  following registry key, and make sure all directory locations exist under the given paths:

Navigate to:


And directory paths exist on your machine. Screen shot as follows:

A far better resolution could have been out-of-the-box in VS 2010 (dev.exe). Just disable the extension if path does not exist (thanks MS!)


Read Full Post »

I was assigned the task of hosting my .NET WCF service on IIS 6 over windows 2003 64 bit !!. (Don’t ask – I didn’t have a choice on the parameters involved!)

I found out that Application Extensions were missing under my deployed website, ie no svc extension.
Path: under IIS –> Default Web Site –> MySite.WCF –> Properties –> Configuration


It appears to be quite a  simple fix by running the aspnet extension registration. Screen shot as follows:

Happy configuring !

Read Full Post »

I’ve a 64bit machine that has a web-service hosted under IIS6!. This starts throwing out errors one morning as I browse to my .svc location – “Page not found 404 Error


  1. Check that the isapi.dll is pointing to v2.0
    C:\WINDOWS\microsoft.net\Framework\v2.0.50727\It appears that an overnight .NET 4 installation was pushed out and IIS 6 extensions were mapped to .NET v4. To resolve this, I manually changed the .svc extension in IIS 6 to v2.0+.
    Screen shot of my machine (under IIS –> Default Web Site –> MySite.WCF)  before I made the change
    After the change:
    Now pointing to : C:\WINDOWS\microsoft.net\Framework\v2.0.50727\aspnet_isapi.dll

    Make sure to restart IIS

  2. Make sure your IIS service account has access to the C:\windows\temp folder. Your WCF service generates temporary files behind the scene and skipping this might display errors such as: System.InvalidOperationException: Unable to generate a temporary class
  3. From your command prompt run the following command
    aspnet_regiis.exe -i –enable     
  4. Then (command prompt again),
                   cd C:\Windows\Microsoft.NET\Framework\v3.0\Windows Communication Foundation
                   ServiceModelReg.exe -i
  5. If it still doesn’t solve it, follow this MSDN article
    Location: http://msdn.microsoft.com/en-us/library/ms752252(VS.90).aspx
    Happy setting up 🙂

Read Full Post »

This post describes debugging on parallel BizTalk components (as in threads) running in VS 2010. With my current application, I submitted a message that would be routed to multiple locations. Before being routed, the file was being archived to a disk location (on the send component).

While debugging, the editor would switch between threads (as expected). I setup a breakpoint on the Archive Component, and the data-layer. In order to focus my debugging on the Archive component, I wanted to pause all other interfering threads.

To view the running thread in VS 2010 IDE, open the threads window, and select your process (appears under BizTalk Server 2010), right click and hit pause

Interestingly, if I open up the Parallel tasks window during debugging I get a diagram of all my tasks 🙂

This shows me two parallel tasks 1. ArchiveMessage… 2. Helper.Advance

Right click on Show External Code on the Parallel tasks (diagram above),

… And this would display a complete (stack) trace on how the call originated

Happy debugging 🙂

Read Full Post »

Guid.NewGuid is always unique. MSDN describes it as containing several sections for a given number – like the timestamp, clock sequence and node. As the example, generating the GUID 8743428c-ef914d059e7c4a2e856e813a
consists of the following sections:

8743428c– Low field of the timestamp
ef91 – Middle field of the timestamp
4d05 – High field of the timestamp with multiplexed version number
9e – High field of the clock sequence with multiplexed variant type
7c – Low field of the clock sequence
4a2e856e813a – Spatially unique node identifier

For more info: Click here

Just for info 🙂

Read Full Post »


This happened because I was trying to write to the context of the incoming message in my pipeline. Although I built my solution and deployed it, the compiler would skip over the line where I was setting the context.

context.Write(propertyName,propertyNamespace, propertyValue);

Solution (Maybe!):

  • Right click on the project, and hit Clean
  • Gac your assembly and restart

I guess this happened because the compiler had gone crazy after so many BizTalk restarts and assembly GACs. Thought about putting a short note on this incase someone might be trying to find out about it.

Happy building 🙂

Read Full Post »

I was struck with the proposition of using XSLT 2.0 for one of my projects. This requires a new parser (XSLT engine) as .NET 4 doesn’t come with one – out of the box. There are many XSLT 2.0 parsers available in the market, depending on your requirements and project budget constraints.

In this post, I’ll explain how to modify a VS 2010 enviornment to debug an XSLT 2.0 file.

  1. Backup your existing file
    Location: C:\Program Files\Microsoft Visual Studio 10.0\Xml\Schemas\xslt.xsd

  2. Download the file: http://www.w3.org/2007/schema-for-xslt20.xsdand save it as xslt.xsd into the above location

  3. Restart VS 2010
  4. Add a new XSLT file into your project
  5. Inside VS 2010, select XML –> Schemas
  6. Disable the version 1.0 schema. This was the backed up copy in step 1 above.
  7. Optional: Change the xsl:stylesheet version to 2.0.
    Hover your mouse over xmlns:xsl and it should read out XSLT 2.0

I’ve been using XML Spy for debugging that utilizes the added features of XSLT 2.0. Although, I should say the VS 2010 debugger should be sufficient for debugging purposes.

: Install the XML Spy Integration Package 2011 (Trial Version)

Happy translating 🙂

Read Full Post »

Older Posts »