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

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

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

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.

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

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

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.

The Visual Studio Express Editions are an expansion of the Visual Studio and SQL Server product line to include fun, simple and easy-to-learn tools for non-professional developers like hobbyists, students and novice developers who want to build dynamic Windows applications, Web sites, and Web services.

One approach to govern user levels with JSP pages is to assign a user object reference to each person's session. The simple example below declares a User interface with concrete StandardUser and AdminUser classes. The User interface only has one method, a boolean isAdmin() method that you can check before outputting key page contents.

Yes. You can use the Visual Studio Team Foundation Server MSSCCI Provider Beta 2, but be sure to disable strong name validation.

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

Wise for Visual Studio .NET is a specially designed Wise product that operates within the Visual Studio interface, with the full functionality of the Wise installation authoring environment. Wise for Visual Studio .NET™ is the only full-featured installation product embedded directly into Microsoft® Visual Studio® .NET. Our participation in the Visual Studio Integration Program and our close partnership with Microsoft gives us exclusive access to Microsoft technology.

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.

No. QuickAdmin is a standard .NET control, so just needs to be referenced when compiling your C# code.

To my knowledge, none of the Cygwin developers have done this, but we have this report from the mailing list that it can be done this way: Use the impdef program to generate a .def file for the cygwin1.dll (if you build the cygwin dll from source, you will already have a def file) impdef cygwin1.dll > cygwin1.def Create a file "my_crt0.c" with the following contents #include <sys/cygwin.h> #include <stdlib.

This project is my hobby and the last thing I want to do in my spare time was use a language or environment I don't enjoy (I code on Macs during the day, and that's enough pain ^_^). I like C#, and I love Visual Studio. Just about any argument you can create against it can be countered, so don't even try. If you don't like it, you don't have to use it; I know that this is certainly my philosophy with other languages/environments!

How can I get around the synchronization issue such that deletes and renames from VS.NET do not get synchronize with VSS as described in Q305516.

No. Designer does not use any code from the Eclipse Visual Editor project (and vice versa). Both the Eclipse VE and Designer are native Eclipse applications that are based on the Eclipse GEF (Graphical Editor Framework) libraries.

Mainsoft for Java EE provides two new project types, Visual C# for Java EE and Visual Basic for Java EE, which are very similar to Visual Studio C# and VB project types. The Mainsoft project types extend multiple functionalities, such as: Build process: The Microsoft compiler creates the MSIL DLL and then invokes the Mainsoft for Java EE compiler. Once the build is complete, Mainsoft for Java EE deploys the final Web Java binary as a WAR (Web Archive) file, onto the Java EE application server.

Unfortunately not, since the Visual Studio Express Edition has a limited support for extensibility that does not match the tight integration needs of Mainsoft for Java EE. You need to install Visual Studio Standard or Professional Edition to use Mainsoft for Java EE.

Mainsoft provides Java EE project templates for Web applications, portal applications, Web services, Web control libraries, console applications, and class libraries. You can use any Java class library in your project and consume Web services. Yes. Mainsoft-based ASP.NET Web applications and Web services are Java EE servlets. Mainsoft ASP.NET project templates include the web.xml servlet deployment descriptor file that you can update to configure your Java EE security settings.

The MSDN Library for Visual Studio 2005 provides access to legacy documentation via the MSDN Online search provider, accessible from the Search page. Access to legacy documentation is also available on earlier editions of the MSDN Library installed on your computer.