I have been writing an application that loads large amounts of data into the a database. The process of loading the data into the database goes through several steps requiring a considerable amount of time to complete. The long processing time is not a matter of concern from the application stand point. However, frequently the application throws a "ContextSwitchDeadlock was detected" message that says the following: Message: The CLR has been unable to transition from COM context 0x20450a0 to COM context 0x20452f0 for 60 seconds. The thread that owns the destination context/apartment is most likely either doing a non pumping wait or processing a very long running operation without pumping Windows messages. This situation generally has a negative performance impact and may even lead to the application becoming non responsive or memory usage accumulating continually over time. To avoid this problem, all single threaded apartment (STA) threads should use pumping wait primitives ...
This article describes the basics of Visual Studio setup and deployment projects. Subsequent articles will cover advanced topics, including more on custom actions, .NET installer classes, and how to build an upgrade for the product. Introduction Setup and deployment projects have always been a part of the Visual Studio.NET environment. Setup projects can be used to build various deployment packages, most notably Windows Installer setups packaged as MSI files. I’ll start with a basic setup that installs a C# Windows forms program and adds a shortcut to it. First, select Setup Project , grouped under Setup and Deployment in the Other Project Types section. Choosing this will give you an empty project for adding your deployment units. With the project selected in Solution Explorer, the View->Editor choice gives you a selection that includes File System – this is where you add your files and shortcuts. Application Folder ...
Run svcutil.exe specifying metadata address Open the visual studio command prompt or locate the svcutil.exe from the command prompt c:\programefiles\microsoft sdks\windows\v6.0A\bin> svcutil.exe "http://localhost/managecrm/managecrm.wsdl" /language:C# //use above if you want to generate the proxy in c# c:\programefiles\microsoft sdks\windows\v6.0A\bin> svcutil.exe "http://localhost/managecrm/managecrm.wsdl" /language:VB //Use above if you want to generate the proxy in VB To Get the helpwith svcuitl.exe use the following command c:\programefiles\microsoft sdks\windows\v6.0A\bin> svcutil The output.config and proxy class will be generated in the "c:\programefiles\microsoft sdks\windows\v6.0A\bin"
Comments