Posts Tagged ‘Visual Studio’

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 »

Follow the following steps to setup your application. This is to receive messages from a web service. I’ll explain an ASMX (SOAP) approach, and then followed by WCF

1.      Run the BizTalk Web Services Publishing Wizard (ASMX), and rename your service and method name

2.      Select the Microsoft.XLANGs.BaseTypes.dll assembly from the BizTalk Assemblies folder

3.      Select the receive location and the receive location name

4.      Once completed, an IIS receive location and BizTalk receive location would be created in your application

5.      BizTalk Artifacts created

6.      Submitting a message:

6.i.           Using Visual studio, add a reference to the above webservice
Address: http://localhost/BizTalkOnRamp/SubmitMessage.asmx

6.ii.         Use the service from Visual Studio:

 XmlDocument xDoc = new XmlDocument();
SubmitMessage submitMessage = new SubmitMessage();

=== Setting up a WCF Service =====

  1. Select the WCF Publishing Wizard
  2. Start by creating a receive location (WCF – NET TCP)
  3. Start the WCF Service Publishing Wizard
  4. Select the Metadata endpoint (MEX) option, and select the receive location name
  5. Select Publish as Schema option
  6. Rename the Service and operations, and select Microsoft.XLANGs.BaseTypes.dll assembly from the BizTalk Assembly folder
  7. Select the location name
  8. This would create an IIS location (BiztalkOnRampWCF)
  9. Run the svcutil command and then import the generated files in your solution
    Command: svcutil.exe http://localhost/BizTalkOnRampWCF/OnRampWCF.svc?wsdl 
  10. Use the service from Visual Studio
SubmitMessageRequest request = new SubmitMessageRequest();
request.part = "Sending a test message";
OnRampWCFClient message = new OnRampWCFClient();

If no subscribers were created in BizTalk, a Fault exception was returned. Using the ASMX service, did not return any errors as such.

Once a message is submitted using a WCF/ASMX service, our BizTalk solution consumes the message and processes it 8)

Happy servicing 🙂

Read Full Post »

This would purely happen due to the assembly length. In my case, the map assembly was named as COMPANY.DIVISION.TECHNOLOGY.FUNCTION.Maps and the Schema was named as COMPANY.DIVISION.TECHNOLOGY.FUNCTION.Schemas.

When the maps assembly references the schema project – BizTalk, behind the scene creates a type reference as [COMPANY.DIVISION.TECHNOLOGY.FUNCTION.Maps> + + COMPANY.DIVISION.TECHNOLOGY.FUNCTION.Schemas].This in turn becomes lengthy for the BizTalk manifest file to handle the reference and therefore crashes the Visual Studio IDE (2005 in my case)!!

Solution: Reduce the qualified name of your BizTalk Artifacts.



Read Full Post »