The service has been tested with a C# client auto-generated from WSDL by the wsdl.exe tool. It should work fine from any .NET language.

Blue Ink was designed to work with Microsoft Visual Studio. Blue Ink's default set of templates output .sln and .proj files so you can immediately open and work with a generated solution using Microsoft Visual Studio. Yes, in most respects Blue Ink generated solutions are no different than manually coded solutions. Blue Ink generated solutions integrate fully with source control applications such as Microsoft SourceSafe either through Microsoft Visual Studio or externally.

You can set the build order of the projects by right clicking on the Solution and choosing Project Build Order and adjusting the dependencies on the Dependencies tab in the Project Dependencies window that pops up. Contributed from George Shepherd's...

It's here: http://msdn2.microsoft.com/library/default.aspx The documentation system previews some new design ideas and new URL model as described here . MSDN welcomes your feedback on the new system at that page.

The Application Files dialog does not have Add/Remove buttons. You can add files in the Solution Explorer with Add Existing File or Add Reference commands.

VC 8 compatibility is not complete in the Windows 2003 SP1 Platform SDK from Microsoft. There are guidelines for fixing the issues in Mike Wasson's blog. There are Vista Windows (Platform) SDKs available to MSDN subscribers. These provide updated headers. Note that the naming of the PSDKs is confusing: the name is the most recent Windows version supported but earlier versions are also supported. See the release notes for a particular PSDK for details.

To see the help topics within Visual Studio 2005 and Visual Web Developer 2005, go to Tools > Options. Under Environment > Help > Online (make sure "Show all settings" is checked), ensure that "Try local first" is selected. This will find the installed help files before attempting to look online. I love these Controls! They've allowed me to create a web-application that I couldn't even dream of doing without them...my boss now thinks I'm a genius!

Assuming that you have successfully installed Fast Formatter and you have any edition (except the Express edition) of Visual Studio .NET 2005 installed, the menu option should automatically appear as described in the tutorial. If it doesn't appear, then please try the following: Turn on the checkbox to the left of Fast Formatter and click the OK button. The menu option should now appear.

Install the Microsoft Platform SDK and Visual C++ 2005 and than you have to make steps written on http://msdn.microsoft.com/vstudio/express/visualc/usingpsdk/ . Import Freeswitch.sln and let's build. After importing you can ignore messages 'Solution folders are not supported in this version of Visual Studio."???The default build is the Debug build at the moment.

The source code distribution of sanos comes with project and solution files for Microsoft Visual Studio version 7. It can be compiled with Visual Studio version 6 by converting the project/solution project files in the build directory to version 6 project/workspace files. The prjconverter utility in the tools directory can be used for converting the project. This is a modified version of prjconverter by S. Rod. You can also use Microsoft VisualStudio .NET 2003 to build sanos.

Use the Microsoft Visual Studio 2005 newsgroups which you can use through the web interface or follow the directions on that that page for using an NNTP reader. For Windows Forms support, see the Forums In addition, there are a number of free and for...

Open Visual Studio and create a blank solution file (File>New Project>Other Project Types>Visual Studio Solutions>Blank Solution) Browse to the place you just created and then in the Location textbox add a new subdirectory name onto the end of the path Every time you open your ASP project you MUST use the Open Project command to browse to the .sln file you created instead of using the Open Website command.

Use our Mono Migration Analysis tool to check if everything that your application uses has been implemented in Mono or if there are special considerations to keep in mind. The Mono API today is somewhere in between .NET 1.1 and .NET 2.0, see our Roadmap for details about what is implemented.

I have code snippets that I use often. How can I manage them so I can easily used them? In Visual Studio, you can store commonly used code snippets on a tab (other than the Clipboard ring) in your Toolbox. You use drag and drop techniques to move the...

Use the ToolboxItem attribute set to false on your component or control class. This will prevent it from appearing in the Toolbox. [ ToolboxItem( false ) ] public class MyComponent : Component{..} Contributed from George Shepherd's Windows Forms FAQ

No. While Visual Studio makes deploying "ClickOnce" applications simple, there are several other ways to deploy "ClickOnce" applications. The .NET Framework SDK includes a tool named MAGE(Manifest Editor & Generator) that provides both a UI (mageui...

VB.NET can perform decent auto-formatting for code. Here is a macro that can call this Auto Formatting command for all the files in a project. Contributed from George Shepherd's Windows Forms FAQ

Microsoft didn't get its Standard C++ act together until Visual C++ 2003. (a.k.a. version 7.1) If you must use older versions of VC++, you're stuck with either the C API, or the ancient 1.7.1 release of MySQL++. This version is an unofficial third-party contribution which is known to have bugs. If it works, I'm happy for you. If it breaks, you get to keep both pieces. Microsoft is giving away a limited but functional version of Visual C++ 2005 which works just fine with MySQL++.

In the Solution Explorer right click on the project that should be the start up project for your application and choose the Set As Start Up Project option. Contributed from George Shepherd's Windows Forms FAQ