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.

The answer for all of these examples is the same, you can use the classes and methods in System.Diagnostics.Process to accomplish these tasks and more. Example 1. Running a command line application, without concern for the results: Private Sub Button1_Click(ByVal sender As System.Object, _ Example 2. Retrieving the results and waiting until the process stops (running the process synchronously): Private Sub Button2_Click(ByVal sender As Object, _ Example 3.

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

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

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.

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

See the article A Utility to Convert VS.NET 2003 Project Files on The Code Project . Contributed from George Shepherd's Windows Forms FAQ

skmMenu can be downloaded in one of two flavors - as a stand-alone binary (the skmMenu.dll assembly), or as a source-code project. The compiled binary is compiled for the .NET Framework version 1.1 and was compiled using Visual Studio .NET 2003. To use skmMenu on a Web site using the .NET Framework version 1.0, you will need to donwload the source code version and compile it with Visual Studio .NET 2002. To accomplish this, do the following: Manually add in the downloaded .cs and Menu.

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.

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!

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

YES! The code of the device driver you write runs in normal Win32 user mode. Therefore, you can compile and debug your code using MSDEV/MSVC++. Please refer to Technical Document #19 for more information regarding debugging your driver code with WinDriver and KernelDriver. If you need to define more than WD_CARD_ITEMS items for your card (currently 20 items, according to the definition of WD_CARD_ITEMS in windrvr.

First create an IIS application using the IIS MMC. Then in Visual Studio .NET, use the "New Project In Existing Folder" project template (at the end of the template list). It will first ask you for the project name (use the same one you created for the IIS application). Click OK button. Then enter in physical folder location. You must first create an IIS application using the IIS MMC. Then in Visual Studio .NET, create a new ASP.

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

You will need to download and install additional components. Please see the Visual Studio Developer Center for more information. No, each release of Visual Studio is tied to a specific version of the .NET Framework. The Express Editions can only be used to create applications that run on the .NET Framework 2.0.

Yes. Eiffel for .NET can be used in exactly the same way as classic Eiffel and no extra language constructs are required to produce applications. Since there are some elements of the .NET language which have no equivalents in Eiffel, such as the ability to define custom attributes, these have been extended to Eiffel for .NET so that the full features of .NET can be used. Eiffel Software (a division of ISE) is the world leader in Eiffel pure object-oriented programming tools.

The ClassWizard asks 'The ActiveX Control "..." has not been inserted into the project. Developer Studio will do this now, and generate a C++ wrapper class for it', click OK The "Add Member Variable" dialog shows up, and is asking for the name of the variable that needs to be inserted

It is very hard for us to support every Windows compiler, so we try to choose the most current and popular compilers. We are depreciating our support for Visual Studio 6.0 and .NET 2003 in favor of Visual Studio 2005, and in the future, 2008. Moving to new compilers also means we can take advantage of new features and make the build process even easier. For example, we now support building on 64-bit Windows and Windows Vista using Visual Studio 2005.

There are not that many tools out there that will support both client-side and server-side debugging. I am certain this will change as AJAX applications proliferate. I currently do my client-side and server-side debugging separately. Below is some information on the client-side debuggers on some of the commonly used browsers.

Type devenv.exe /? to get a full list of options. Contributed from George Shepherd's Windows Forms FAQ

EiffelEnvision brings strengths in several areas that result in significant benefits to the developer: Eiffel's "code once, run on many platforms" feature provides "future proofing" for companies using .NET: their users can migrate applications to and from different platforms, and can also use component libraries across platforms. Eiffel brings quite a few unique and powerful features to .NET. Most noticeably it is the only .NET language to offer multiple inheritance and genericity.

The environment for all virtual hosting plans at uplinkearth is considered to be "production". We expect that your code has been debugged prior to uploading to your virtual server. While we recognize that matching our server environment to your development environment may not be 100% possible, we do expect that most of your code is already production quality and does not require low level debugging facilities.

No. Rules extensions can be built and compiled on a separate computer, then copied to the extensions folder on the MIIS server. Installing the debugger on the MIIS computer is a good idea, since it will improve the troubleshooting experience. Top

By integrating our installation technology directly into Visual Studio .NET, we have created a new installation authoring model. From the first line of code that's written, you will have a working installation. You can now test the installation as you test the application. The result is higher quality products, easier internal testing, earlier beta availability, and a significantly more efficient development process.

Wise is an innovative company always looking for ways to use new technologies to solve customer's installation problems. We immediately saw this as an opportunity to change the way installations are created, and are the first and only installation tool vendor to capitalize on this opportunity.