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

Answer: Changes in Windows vista impact Visual Studio so that Microsoft is unable to provide support for Visual Studio .NET 2002 or Visual Studio .NET 2003 on Windows Vista. see Visual Studio on Windows Vista for additional information.

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

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

I recommend a fast computer with lots of hard disk space and lots of memory. Note that if you want to run all the features of VB .NET you need to have Windows 2000 Professional or Windows XP Professional.

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.

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.

Well, there is a compatibility problem. You can run a project from 2002 on 2003, but not visa versa. Once a 2002 is opened in 2003 it can't be opened in 2002. Of course, there are work-a-rounds but that beyond an intro class. Note: This class is about VB .NET 2003.

In accordance with our sales policy , we guarantee customer support service within one year from the date of purchase. The services include technical support, customer support and all updates and new releases for purchased product during that term. When 1-year support service expires, customer needs to renew that support at a discounted price to continue receiving support services. The renewal support purchase extends customer support by 1-year from the date of its expiration.

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

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.

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!