In Visual Studio go to the Debug | Exceptions | Common Language Runtime Exceptions | System and select System.NullReferenceException . In the When the exception is thrown group box, select Break into the debugger . Run your scenario. When the exception...

In VS.NET go to the Debug Menu >> "Exceptions..." >> "Common Language Runtime Exceptions" >> "System" and select "System.NullReferenceException" In the botton of that dialog there is a "When the exception is thrown:" group box, select "Break into the debugger" Run your scenario. When the exception is thrown, the debugger will stop and notify you with a dialog that says something like:

Add the optional expected attribute to the @Test annotation. The following is an example test that passes when the expected IndexOutOfBoundsException is raised: Test(expected=IndexOutOfBoundsException.class) public void testIndexOutOfBoundsException() { ArrayList emptyList = new ArrayList(); Object o = emptyList.get(0); }

Declare the exception in the throws clause of the test method and don't catch the exception within the test method. Uncaught exceptions will cause the test to fail with an error. Test public void testIndexOutOfBoundsExceptionNotRaised() throws IndexOutOfBoundsException { ArrayList emptyList = new ArrayList(); Object o = emptyList.get(0); }

When I'm debugging, the wrong source file shows up. It has the same name, but from the wrong directory. What is wrong?.

For JDebugTool to catch a thrown exception, select the Exceptions | Catch... menu item, from the menubar.

If the length of a CosNaming::Name is zero or the ID field of any NameComponent is an empty string, then InvalidName is thrown.

There are .NET Framework classes that will give you the call stack information at a particular point. Call this method inside the catch block. using System; using System.Diagnostics; using System.Reflection; using System.Text; public static void TraceCaughtException...

My application keeps on stopping with "an unhandled exception C000005" You have a bug. This is the 32 bit equivalent to Exception 13: General Protection Violation. The NT kernel will also raise it when an application has done something wrong which it has detected: invalid arguments [checked build only?], overwriting the guard bytes at the end of GlobalAlloc()'d memory & the like.

Microsoft Visual Studio .NET 2003 solution build runner is build on the base of NAnt runner, described before. Solution task is used to run the build. Projects files are expected to be wellformed XML. You may configure this runner to run NUnit tests.

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

CannotProceed exception works like a "catch all" in exception handling. If the operation cannot return successfully due to some reason (e.g. database connection time-out etc) other than the well-defined exceptions (NotFound, InvalidName, AlreadyBound or NotEmpty), then CannotProceed is thrown.

Yes, there are framework classes that will give you the Call Stack information at a particular point.

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.

The Visual Cafe debugger is set to trap ArrayIndexOutOfBoundsException exceptions by default. Xerces-J uses ArrayIndexOutOfBoundsException internally to signal exceptional, but not erroneous conditions. In order to run Xerces-J2 inside Visual Cafe's debugger, you need to turn off the trapping of these exceptions.

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

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.