When you try to use the Remote Debugging Monitor (Msvsmon.exe) in Microsoft Visual Studio on a Windows Vista-based computer, you may receive the following error message in the Configure Firewall for Remote Debugging dialog box:

The Windows Firewall is currently blocking remote debugging.

When you try to unblock the Remote Debugging Monitor, you receive the following error message:

Could not configure the Windows Firewall. Incorrect function.

Consider the following scenario:

• You create a custom application by using the Microsoft .NET Framework 2.0.
• The custom application uses the Microsoft Visual Studio for Applications (VSA) Visual Basic Runtime.
• You run the custom application on a system that has been updated to run a later version of the Microsoft .NET Framework common language runtime (CLR).

In this scenario, the custom application may behave incorrectly or may generate errors. These problems occur when you try to compile macros or when you try to run macros in the custom application.

When you are developing the custom application by using VSA, you may experience the following problem. When the custom application calls the Microsoft.VisualBasic.Vsa.VsaEngine.Compile method, an exception is thrown by the VSA Visual Basic Runtime to the host. The host may trap the exception, and the user may receive the following error message:

An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0×8007000B)

Alternatively, the host may ignore the exception, and one of the following symptoms may occur:

• The host fails unexpectedly when the user tries to run the macro that the user just compiled.
• The host does not handle the macro in any way.

In the latter case, the CLR will close the application because the application had an unhandled exception.

When you try to run macros in the custom application, you may experience one or more of the following symptoms:

• You receive an error message that a macro cannot be generated or run.
• You receive an error message that a macro or assembly cannot be loaded.
• The host application may not start or may exit unexpectedly.
• Although the host application does not report an error, the macro does not run, and the application appears to have done nothing.

Consider the following scenario. You add a Web reference to a project in Microsoft Visual Studio 2005. For the Web Services Description Language (WSDL) file that describes the Web service, the first element contains a default namespace. For example, the first element resembles the following:

<xsd:schema xmlns="http://<URL>" xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://<URL>" elementFormDefault="qualified" attributeFormDefault="unqualified">

In this scenario, you may receive the following error message:

The custom tool ‘MSDiscoCodeGenerator’ failed. Unable to import binding ‘BindingName’ from namespace ‘http://NamespaceLocation’.

Additionally, you receive the following error message in the Error List window:

Error 1 Custom tool error: Unable to import WebService/Schema.
Unable to import binding ‘BindingName’ from namespace ‘http://NamespaceLocation’. Unable to import operation ‘OperationName’. The element ‘ElementName’ is missing.

When you use the Microsoft Program Maintenance Utility (Nmake.exe) in Microsoft Visual Studio 2005, you may receive the following error message:

U1073: The build method of FileName is not specified.

You experience this problem if the following conditions are true:

• You use Nmake.exe version 8.00.50727.42 or a later version of Nmake.exe.
• You use the English version of Visual Studio 2005 Service Pack 1 (SP1) on the Japanese version of the operating system.

Note: This problem may not occur when you use earlier versions of Nmake.exe.

Consider the following scenario:

• In Microsoft Visual Studio 2005, you create multiple pages in different folders in an ASP.NET-connected application.
• These pages use the same name.
• You set a breakpoint in one of these pages.

In this scenario, a significant delay may occur when you try to debug the ASP.NET-connected application. Additionally, this delay may cause a time-out error. In this case, you receive the following error message:

Unable to start debugging on the web server. The operation has timeout.

In Windows Vista Home Basic or in Windows Vista Home Premium, you create a Microsoft ASP.NET 2.0 application by using Internet Information Services (IIS) 7.0. When you try to debug the application in Microsoft Visual Studio 2005, you receive the following error message:

Unable to start debugging on the web server. Debugging failed because integrated Windows authentication is not enabled. Please see Help for assistance.