When your application is launched from Visual Studio in Debug mode, you will see all trace and debug messages in the Output window. Contributed from George Shepherd's Windows Forms FAQ

When your application is launched from the VS.NET IDE in Debug mode, you will see all trace and debug messages in the Output window calling:

In VS2003, debug info for unmanaged code is turned off by default. This is why you will not see the call stack including code in the System DLLs. To enable debugging for unmanaged code go to your project properties dialog and turn on as shown here: Contributed...

In IE go to Tools/Internet Options.../Advanced Tab and clear the "Disable Script Debugging" check box options. In VS.Net in your project properties dialog, select "Debugging" under "Configuration Properties" and make sure that "Enable ASP.Net Debugging" is turned on. You can then set break points in script code in VS.Net in custom script files or the application aspx file. VS.Net should give you detailed debugging information for variables in the scope just like other high-level languages.

You need to use a second instance of Visual Studio to debug the one that's running the code. Put your control on a form. Start a second instance of Visual Studio and choose the Debug | Processes menu item. Double-click devenv.exe and choose Common...

Using dual monitors is one way to tackle this problem. If you happen to be running on a terminal server machine there's an even better way to do this. Create a terminal server session to your own machine and start the exe in the terminal server window...

No. The value of this property is not stored in the project files. It is stored in extra files created by the IDE when a solution is loaded (VS .NET 2003 uses a hidden .suo file next to the .sln solution file). The format of these files is not known to CMake and cannot be generated. In some versions of VS the files are binary and not human readable. The path to the SDK libs (user32.

When filing bugs, it is often necessary to get a trace (generally +relay, but specific DLLs have their own debug channels). To retrieve a trace, run: Then ATTACH /tmp/output.txt to the bug. If the resulting file is larger than 1 MB, compress it with 'bzip2 -9' or 'rzip -9' before attaching.

This is possible if the same listener was added more than once to the Listeners list in Trace. This is possible even if an assembly that you linked to makes an additional entry for the same listener. Perform a check like this before adding a listener...

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.

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.

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...

Yes. In order to do this you will need to buy Visual Studio Team Foundation Server and a Client Access License for proper communication with the server. Team Explorer, which is included with Team Foundation Server, is a stand alone client that uses the Visual Studio 2005 shell providing a UI for source control, work item tracking and all the other features. For more information on licensing Visual Studio Team System (including Team Foundation Server) see the Team System Licensing White Paper.

Assuming that you have successfully installed C-Sharpener For VB, the menu option should automatically appear. If it doesn't appear, then try the following: Turn on the checkbox to the left of C-Sharpener For VB and click the OK button. The menu option should now appear.

No, but for non-Java programs it helps. The suggested compromise is to build it with debug, develop your traces, then strip the debug information when shipping the product. This is fully discussed in Chapter 6 of RootCause for C++ User's Guide, "Building a Traceable Application".

You can view the Java console in a Web Start application by turning on the Web Start Java Console. In the Web Start application choose to Preferences under the file menu. Choose the Advanced tab. Under Output Options, check "Show Java Console". The next time you run any Web Start applications a console window will be displayed.

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