Visual Studio 2005 Known Issues

Issues When Using Microsoft Visual Studio

2005

This document lists issues you might encounter while using Microsoft Visual Studio 2005. Forissues related to setting up the product, please refer to readme.htm.

For a list of breaking changes between Beta 2 and RTM, please go to http://go.microsoft.com/fwlink/?LinkId=51223

For the latest known issues, see the online Visual Studio 2005 Known Issues athttp://go.microsoft.com/fwlink/?LinkId=51326

1. Visual Studio

1.1 VC++ Visual Studio 2005 Beta 2 Project File fails to open

When you use the final version of Visual Studio 2005 to open a Beta 2 C++ project that was lastloaded on a computer with an installation location for Visual Studio that is different from that on thecurrent computer, or if the project paths have changed, you might receive an error.

To resolve this issue

Edit the project settings file. Right-click on the grayed-out project node in the solution explorer andselect Edit .vcproj, which will bring up the file in the XML editor. Change the valueof the InheritedPropertySheets tag to$(VCInstallDir)VCProjectDefaults\UpgradeFromVC70.vsprops, and then reload the project.

1.2 On Windows 2000, using Start with Application Verifier produces the

message: "Application Verifier is not supported on the Operating System

running on machine_name. Please upgrade to Windows XP or above."

Windows 2000 does not support the Application Verifier.


Upgrade to Windows XP or above.

1.3 Start with Application Verifier generates the dialog box: "Application

Verifier requires an updated system file that is not detected on your machine

machine_name. Do you want to go to Windows download center to get the

update?"

Visual Studio setup does not install a system file that is required by Application Verifier. If the

Visual Studio 2005 Known Issues file:///D:/sw/My Disc (E)/vs/VSKnownIssues.htm

1 of 53 6/9/2014 2:01 PM

required version of the file is not present on your computer's operating system, you must update itbefore you can use Application Verifier.


Select 'Yes' on the dialog to open the internet browser and show the update link on the Microsoftdownload center site. Install the required update. You also can access the Microsoft downloadcenter using this link:http://go.microsoft.com/fwlink/?LinkId=49500

1.4 Toolbox in Distributed System Designers does not reflect the local

Windows language setting until Toolbox is reset.

In the Options dialog box, users can set Visual Studio to use the local Windows language. However, the Toolbox in Distributed System Designers does not reflect this setting until the Toolboxis reset.


1) Close all Distributed System Designers (Application Designer, System Designer, LogicalDatacenter Designer, and Deployment Designer).2) Right-click inside the Toolbox and then click Reset Toolbox.3) Reopen the Distributed System Designers you want to use.

1.5 Remote Debugging on Windows 98 and Windows Me

Problem 1:

If using Visual Studio 2005 to remote debug with default transport to a Windows 98 or Windows MEcomputer that is part of a domain with a Windows Server 2003-based Domain Controller, the usermay see the following error message approximately 10 minutes after starting the Windows 98/MEcomputer:

-------------------------Microsoft Visual Studio-------------------------Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor named''. Access is denied.

Cause: Server Message Block (SMB) signing is both enabled and required on Windows Server2003-based Domain Controllers.

Problem 2:


2 of 53 6/9/2014 2:01 PM

If using Visual Studio 2005 on a Windows XP or later computer to remote debug to a Windows 98or Windows ME computer, the user may see the following error message.

-------------------------Microsoft Visual Studio-------------------------Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor named ''. TheMicrosoft Visual Studio Remote Debugging Monitor on the remote computer cannot connect to thelocal computer. Unable to initiate DCOM communication. Please see Help for assistance.

Cause: "Remote Access for Anonymous Logon in DCOM" is disabled on the computer runningVisual Studio 2005.


Problem 1:

1) Set the Domain Controller policy such that SMB signing is enabled but not required.For information on how to do the same go to http://support.microsoft.com/?kbid=8874292) Restart the Domain Controller3) Restart the computer where Visual Studio 2005 is installed.4) Restart the computer running Windows 98/ME

Problem 2:

To allow "Remote Access for Anonymous Logon in DCOM" on the computer running Visual Studio2005, follow these instructions:1) At a command prompt, type dcomcnfg, and then press ENTER. Component Services opens.2) In Component Services, expand Component Services, expand Computers, and then expand MyComputer.3) On the toolbar, click the Configure My Computer button. The My Computer dialog box appears.4) In the My Computer dialog box, click the COM Security tab.5) Under Access Permission, click Edit Limits. The Access Permission dialog box appears.6) Under Group or user names, click ANONYMOUS LOGON.7) Under Permissions for ANONYMOUS LOGON, select the Remote Access check box, and thenclick OK.8) Restart the computer.

1.6 Pressing F1 on a Web service provider endpoint results in "InformationNot Found".

When you press F1 while a Web service provider endpoint is selected on an application diagram, arelevant Help topic cannot be found.


3 of 53 6/9/2014 2:01 PM


In Help, search for "How to: Define Operations for ASP.NET Web Services".

1.7 Users should not store sensitive information in custom settings or in

settings not defined as secure settings by SDM documents.

Sensitive information stored in custom settings or in settings not defined as secure settings by SDMdocuments (such as .sdm and .ad files) will appear as plain text in these files.


When using the Settings and Constraints Editor, store sensitive information only settings that aredesignated as secure settings in SDM documents. For more information, see "How to: CreateCustom Settings for Applications, Servers, Endpoints, and Zones" and "Considerations forImplementing Applications" in Help.

1.8 Starting the Itanium (IA64) native tools command prompt

When installing the tools on Itanium (IA64), a shortcut for starting the Itanium (IA64) native toolscommand prompt is not created.


The Itanium (IA64) native tools command prompt can be started by doing the following:1) Go to Start, click Run2) Type cmd3) At the command prompt, type \VC\bin\vcvars64.bat

1.9 Profiling and running instrumented modules from network shares is not

supported

Under default Visual Studio settings, running an instrumented binary from a network share results inan unhandled exception.


Copy or move the project or binary you wish to profile to your local hard drive.

1.10 Using Event Tracing for Windows (ETW) to collect event profiling data

for IIS5.1 is not supported


4 of 53 6/9/2014 2:01 PM

Trace profiling an application that targets IIS5.1 and enabling the collection of ETW events willsilently fail in the UI and report an erroneous Error VSP1432 on the command line.

1.11 IA64 profiling is not supported

IA64 profiling is no longer supported.

1.12 Stand-alone profiler does not support code coverage

When you try to run code coverage on a stand-alone profiler installation, you will see an unhandledexception.

1.13 Running code coverage against an ASP.NET application may leave

web.config in an altered state.

When running unit tests against an ASP.NET project, the test engine needs to modify theweb.config files. Sometimes these files are not cleaned up and can cause exceptions in subsequenttest runs and application runs.


Restore the original web.config file from the backup that was created during the test run.

1.14 Support for ReportViewer Control is limited on Windows 98

The Windows Forms ReportViewer control has limited support when used in applications runningon Windows98. With this control, you can only view reports previously published on a SQL Server2005 Reporting Services report server. You cannot use it to view client report definition (.rdlc) filesin local processing mode.

1.15 Code coverage for ASP.NET will not work if the IIS worker process is

running as SYSTEM

Collecting code coverage data for ASP.NET will not work if the IIS worker process is running asSYSTEM. Check MSDN for the name of the IIS worker process on your system because the nameis different for different versions of IIS. You can use Task Manager to determine what user theworker process is running under.Note: The unit tests will run correctly if code coverage is disabled.



5 of 53 6/9/2014 2:01 PM

Change the IIS worker process not to run as SYSTEM.

1.16 Trying to profile an ASP.NET application with forms authentication

enabled results in an error

If you try to profile an ASP.NET application with forms authentication enabled, you will get a website configuration error and the application will not run.


There is no known resolution.

1.17 Performing actions on Distributed System Designer diagrams while codeis running will cause Visual Studio to stop responding.

For example, adding applications to a system diagram in System Designer while the Debugger isrunning will cause Visual Studio to stop responding.


Do not run code performing actions on Distributed System Designer diagrams.

1.18 Trace profiling a shared dll will profile all processes using that dll

If you have a shared dll and want to trace profile it, you might end up profiling all processes that areusing it.


1) Turn off profiling on each process you do not want to profile using vsperfcmd -proccessoff:PID.2) Set HKCU/software/microsoft/visual studio/8.0/VSPERF/Monitor/Settings/ProcessProfile=Off,start your target processes, and then enable profiling on all processes you want to profile usingvsperfcmd -processon:PIDNote: When you have finished profiling, you must shut down all processes that are using the shareddll in order to shut down the monitor and flush the data to the report file.

1.19 How to trace profile Natively Generated (ngen'd) images

Trying to instrument an ngen'd image will report an erroneous VSP1014 error.The CLR will not load an instrumented managed binary that has already been ngen'd.



6 of 53 6/9/2014 2:01 PM

Once you have instrumented the managed binary itself and not the ngen'd image, you must do oneof the following:

1) Delete the ngen'd image so that the CLR uses the instrumented binary-or-2) Regenerate the binary using ngen.exe.

1.20 Crash if the MarkProfile profiling APIs are used and the profiler monitor

is not running

When using MarkProfile, CommentMarkProfile, or CommentMarkAtProfile that are available fromvsperf.h, you will see an application crash if the profiler monitor is not running. This will be mostnoticeable if you add the API calls and then launch them under the debugger instead of the profiler.


Start the profiler monitor using "vsperfcmd -start:sample -output:foo.vsp"

1.21 Web projects: Types defined in a GAC'ed assembly cannot be visualized

in class diagrams

Class diagrams cannot show types in a referenced assembly if all the following conditions are true:1. Class diagram resides in a web project.2. The referenced assembly is installed under the Global Assembly Cache (GAC)3. The referenced assembly is not installed under the framework directory root("Microsoft.Net\Framework\\").


Visualize the referenced type from a non-web project.

1.22 Instrumented managed dll fails to load into a website project

An instrumented managed user control hosted in a website will fail to load with the default securitysettings for .NET.


You must enable Full Trust for the local website to be able to load the instrumented dll.caspol.exe -ag 1.2 -url http://localhost FullTrust

1.23 Application Verifier is not enabled for mixed mode C++ projects. Instead


7 of 53 6/9/2014 2:01 PM

it will produce the following dialog box:

"Application Verifier is not supported for the selected debug mode. Please seesupporting documentation for more information. Click on OK to continue

debugging without verifier"

Application Verifier is not enabled for mixed mode applications even though you can select it fromthe Debug menu.


Continue debugging without Application Verifier.

1.24 Profiler driver is not being initialized correctly on Windows 2000

The first time the profiler driver is used, it needs to initialize itself. If this initialization happens onWindows 2000 Server via remote desktop session, the driver will be initialized for future sessionsbut not for the current one. If you try to start the monitor on the current session, you will see ErrorVSP1398 and the monitor will fail to start.


Do one of these:

1) Restart the computer.-or-

2) Use remote desktop to connect to a different session on the same computer.

1.25 Test runs window: Users in "Controller users" group and not in "Admin

users" are not able to connect to controller

When a user is added to the "Controller users" group and not to the "Controller admin" group thechange does not take affect until the controller service is restarted. As a result, the user cannotconnect to the controller.


Restart the controller service.

1.26 Encoding changes might not appear when a file is reloaded in the editor.

Visual Studio 2005 does not detect changes in encoding when a file is reloaded. If you havechanged the encoding of a file outside of the current editor, or performed a source control operationthat changed the encoding of a file open in the editor, Visual Studio reloads the file automatically.


8 of 53 6/9/2014 2:01 PM

The contents of the file might display incorrectly after it has been reloaded in the editor.


Close the file without saving the changes.1.On the File menu, choose Open and then select File.2.In the Open File dialog box, click the arrow adjacent to the Open button and click Open With.3.From the list in the Open With dialog box, select the editor into which you want to open thefile, such as the Binary or Resource editor. To open the file with a particular encoding, selectan editor with encoding support, such as XML Editor with Encoding.

4.

Click OK.5.In the Encoding dialog box, select the correct encoding from the Encoding drop-down list.6.Click OK.7.

1.27 Product repair occurs when installing Setup project

If Visual Studio 2003 is installed after Visual Studio 2005, then building a Setup Project from eitherversion of Visual Studio causes product repair to occur. The product repair only occurs for usersother than the one who installed Visual Studio 2003.


When the product repair occurs, allow it to complete. For the repair to be successful, it must beperformed from a user account that did not perform the installation of Visual Studio 2003 and hasadmin privileges.

1.28 Office product fails to run after installing Visual Studio 2005 Tools for

Microsoft Office project

After installing a Visual Studio 2005 Tools for Microsoft Office add-in project that contains aReg-free COM component, the Office product targeted by the add-in fails to run.


Reg-free COM is not supported for Visual Studio 2005 Tools for Microsoft Office add-in projects.

1.29 Setup and Deployment projects imported from Visual Studio 2003 fail to

be signed when built

Setup and Deployment projects imported from Visual Studio 2003 that have signing enabled will notbe signed when built in Visual Studio 2005. The following message will appear in the Error Listwindow at build time: "The file ' ' was not signed. The deployment project containsdeprecated signing properties. See Help for more information."


9 of 53 6/9/2014 2:01 PM


To enable signing, you may invoke the Software Development Kit tool, Signtool, on the build outputfrom a post-build step in the Setup and Deployment project. More information on how to do this isavailable by viewing the help topic associated with the build message referred to above. You canaccess help by highlighting the message in the Error List window and then pressing F1.

To remove deprecated signing project properties:1. Double-click the message in the Error List window2. In the dialog that appears, click 'Yes.' This will cause the deprecated signing project properties tobe removed from your project file.

1.30 Certain bootstrapper packages available with Visual Studio 2005 target

only 32-bit platform

The bootstrapper packages for .NET Framework 2.0, SQL Server Express 2005, Microsoft VisualJ# Redistributable, Windows Installer 2.0, and Windows Installer 3.1 available with Visual Studio2005 target only 32-bit platforms. If a bootstrapper built with these packages is run on a 64-bitplatform, the installation might block.


The bootstrapper packages for the 64-bit versions of the .NET Framework 2.0 and SQL ServerExpress 2005 redistributables will be made available on the Microsoft download center.

1.31 User Defined Types as Settings may cause unexpected behavior in the

settings designer

Using User-Defined Types as Settings might cause problems if the assembly in which the UDTresides is updated while the consuming project is open. If this scenario is required, you canworkaround the problem by making the UDT assembly use incremental version semantics.


If the User Defined Type that is being used as a setting resides in a class library, incrementallyversion the library to mitigate the problem. If the User Defined Type resides in an EXE, the IDEmust be closed and restarted for changes to the UDT to take affect.

1.32 No Forms property in "My" inside a User Control project

My.Forms will not be available in a User Control project



10 of 53 6/9/2014 2:01 PM


1.33 Cannot invoke an object's method through remote debugging if stopped

on Sleep

If you have the following code running on a remote computer, then attach to the running code viaremote debugging, and break as execution is inside the call to Sleep(), you will be unable toevaluate members of the variable c.

c = New c1 'assume c1 is a valid classWhile TrueThreading.Thread.Sleep(1000)End While


Step out of the Sleep(), you will then be able to evaluate objects normally.

1.34 Visual Studio 2005 Team Edition for Testers: Load Test Error Table

Contains: "Could not Find Dependent Counter Needed to Apply Threshold

Rule"

The load test result viewer's Error Table contains an error with the message Could not finddependent counter needed to apply threshold rule. The load test contains a threshold rule thatcompares one performance counter with another. This error is generated if the comparisonperformance counter does not generate an instance during a sampling interval.


Change the associated threshold rule to compare against a constant instead of anotherperformance counter. This does not affect the results of the load test beyond failing to run thespecified threshold rule and can be safely ignored.

Use the following procedure to change the counter:1. Edit the load test and select Counter Sets/Load Test/Counter Categories/LoadTest:Request/Counters/Avg. Connection Wait Time/Threshold Rules.2. Delete the Compare Counters Rule.3. Right-click to add a Compare Constant rule.4. In the rule, set Alert if Over to true, warning to .01 (10 ms) and critical threshold to .02 (20 ms).

1.35 Visual Studio 2005 Team Edition for Testers: Web test run fails with the

error, Object not set to an instance of an object

Running a coded web test with an unused data source fails with the error Object not set to an


11 of 53 6/9/2014 2:01 PM

instance of an object. This occurs because a data source is defined within a coded web test but itis not bound to any item in the test.


Remove the unused data source from the coded web test or bind a field from the data source to anitem in the test by adding a DataBinding attribute to the test class.

1.36 Visual Studio 2005 Team Edition for Testers: Set the Proxy Property of a

SoapHttpClientProtocol Implementations to Null

If you are running a load test containing unit tests that call Web services, the unit test code shouldexplicitly set the proxy property of the Web service proxy class that implementsSystem.Web.Services.Protocols.SoapHttpClientProtocol. This prevents a performance bottleneckthat can occur when the proxy must be automatically detected.

For example, if you have a Web service proxy class such as this:

[System.Diagnostics.DebuggerStepThroughAttribute()][System.ComponentModel.DesignerCategoryAttribute("code")][System.Web.Services.WebServiceBindingAttribute(Name="InstantOrderSoap",Namespace="http://tempuri.org/")]public partial class InstantOrder : System.Web.Services.Protocols.SoapHttpClientProtocol {V}

then after creating the proxy object, and before using it, explicitly set the Proxy property:

InstantOrder orderCheck = new InstantOrder();orderCheck.Proxy = new WebProxy("myproxy", true);

1.37 Cannot pass a structure to a variant property in an ActiveX EXE object

On Windows 98, you cannot pass a structure to a variant property in an ActiveX EXE object. Theproblem is that on a clean Windows 9X computer, the System DLL rpcrt4.dll was not registered bydefault, so the operating system is missing the registration key [HKEY_CLASSES_ROOT\CLSID\{B5866878-BD99-11D0-B04B-00C04FD91550}]. The invocation fails because of this missingregistration.


Go to C:\Windows\System and manually invoke RegSvr32.exe rpcrt4.dll.

1.38 New on a type parameter with cyclic constraints causes VB compiler to


12 of 53 6/9/2014 2:01 PM

hang and increases memory allocations

Pasting the code below in a console application will cause it to hang.

Class C1(Of U As U) 'the cyclic constraints here cause the later problemEnd Class

Partial Class C1(Of U)Dim x As New U 'Issue - this causes infinite looping and the memory usage keeps increasingtill memory is no longer available

End Class


Remove the cyclic constraint.

1.39 Parameters to StartupNextInstanceEvent handler will not contain

command line arguments if application is started using ClickOnce

Parameters to StartupNextInstanceEvent handler will not contain the command line arguments ofthe second instance of the application if application is started using ClickOnce. You must use theMy.Application.Deployment.ActivationUri property to get the command line arguments.


Use the ASP runtime classes to get the command-line arguments, as follows:

Imports System.Web

Dim commandLineArgs as NameValueCollection = _HttpUtility.ParseQuery(My.Application.Deployment.ActivationUri)

1.40 VB compiler doesn't support InternalsVisibleTo attribute

This attributute (among other things) exposes Friend types to other assemblies. This attribute is notsupported by the VB compiler.

Some unit testing technologies that rely on this attribute for testing private types will not work asexpected.




13 of 53 6/9/2014 2:01 PM

1.41 Some documentation for vsperfcmd.exe is missing

Documentation of vsperfcmd that describes common user scenarios is missing.

Here are some examples of common commands that you might use with vsperfcmd.exe:vsperfcmd -start:sample -output:foo.vspvsperfcmd -start:trace -output:foo.vsp -counter:g,1,0,InstructionsRetiredvsperfcmd -launch:foo.exe -args:"input arguments" -gc:lifetimevsperfcmd -attach:foo.exe -pf:1

1.42 My.Log is not available in a VB Web Control Library project.

In a VB Web Control Library project, My.Log is not available. Because My is per-project, My.Logwill be available for WebUserControls inside a Web site project, but it will not be available forclasses within Web Control Library projects that are consumed by a Website.


Use Trace.Write instead of the My.Log methods.

1.43 My.Application.Log.WriteEntry may throw an exception if user does not

have File I/O permission.

1) Create a new Console Application with the following code:

My.Application.Log.DefaultFileLogWriter.CustomLocation = "D:\temp" My.Application.Log.WriteEntry("Foo")

2) Run the application

RESULTS:Log file is created in D:\temp, but the directory D:\Documents and Settings\\ApplicationData\Microsoft\WindowsApplication1\1.0.0.0 is also created if it does not exist. In the case that theuser does not have permission to do this, an exception is thrown. This is likely to occur when usinga class library in a Web application, because the ASP.NET process does not have write permissionto any Application Data directory by default.


1) Remove the default FileLogTraceListener via app.config, and Reconfigure My.Application.Log touse a different TraceListener.2) Listen to Unhandled Exception event and continue when the event happens.3) Try/catch every logging call (or at least the ones that could conceivably be the first to execute).


14 of 53 6/9/2014 2:01 PM

1.44 References to 32-bit COM components may not work in VB and C#Applications running on 64-bit platforms

Most existing COM components are only available for 32-bit platforms and will not run in a 64-bitprocess on a 64-bit platform (although they will run correctly in a 32-bit process on a 64-bitplatform). VB and C# applications that reference these 32bit COM components will not run bydefault on a 64-bit platform because by default the application will launch as a 64-bit process.

The problem appears when a project with one or more COM references is:1. Migrated to Visual Studio 2005 and executed on 64-bit platforms

-or-2. Created using Visual Studio 2005 on 64-bit platforms.

In Visual Studio 2005, the VB and C# compilers use the platform target property to determine ifthe.exe or .dll should run in 32-bit or 64-bit CPU architecture mode. The default setting for thisproperty in Visual Studio 2005 is set to 'AnyCPU', which indicates that the application can run ineither 32-bit or 64-bit mode, depending on the host platform. In this situation you may see amessage such as "Cannot instantiate class V" when you debug or run these applications.


Set the platform target property to 'X86' for your VB or C# projects that have references to COMcomponents.

For C# Projects:1. Right click the project in the solution explorer and open 'properties'2. Choose the Build tab3. Set the Platform Target property to 'X86'

For VB Projects:1. Right click the project in the solution explorer and open 'properties'2. Choose the Compile tab3. Press the Advanced Compile OptionsV button4. Set the Target CPU property to 'X86'

Express Editions:The VB and C# Express products do not expose the Target property inside the developmentenvironment. You will need to carefully modify the project file using a text or XML editor.1. Close the project and/or solution2. Select Open File from the File menu3. Navigate to the project directory, and highlight the project file4. Press the Open button, the project file should open in the XML editor5. Locate the first section and add the following line:x861. Save the project file


15 of 53 6/9/2014 2:01 PM

2. Reopen the project and/or solution using Open Project/Solution from the File menu3. Continue with development, debugging, and testing

Alternatively, if the application is targeted to 64-bit platforms, you can ensure that the COM controlsadded to the application have 64-bit equivalents on the development and deployment computers.

1.45 Using Windows Roaming Profiles may cause first time launch message

to show on each startup.

When any one of the Visual Studio family of products is used with Windows Roaming Profiles, thefirst time launch message that says "Visual Studio 2005 is configuring the environment for first timeuse. This might take a few minutes." might appear on every session startup. This might causeunnecessary slowdowns in startup performance.


Click on the Tools > Options... Select "Import and Export Settings", and change the path under"Automatically save my settings to this file:" to a path that is NOT under the "My Documents"directory.

1.46 Installation of an Add-in that accesses DTE.CommandBars before Visual

Studio 2005 has been launched will lead to an Add-in load error

After first installing Visual Studio 2005, if an Add-in is installed that tries to get DTE.CommandBarsin its OnConnection, first launch of Visual Studio 2005 will result in the following message:

The Add-in failed to load or caused an exception. Would you like to remove this Add-in?


If you are installing Visual Studio 2005, after installation launch Visual Studio and shut it down again*before* installing any Add-ins If this Add-in was already installed and you encounter the above message, click No and closeVisual Studio. In a Command Prompt, navigate to \Common7\IDE and run thefollowing command: devenv /resetaddin *

1.47 Web service references in Visual Basic or Visual J# class libraries might

not reverse-engineer when building the class library is performed last.

In this scenario, a Visual Studio solution contains a Visual Basic or Visual J# class library, whichcontains a Web reference to a Web service. The solution also contains an ASP.NET Web site,which has a reference to the class library. After these items are added to the solution, certain


16 of 53 6/9/2014 2:01 PM

configuration file entries must be copied from the class library's App.config file to the Web site'sWeb.config file. If the class library is built after copying the configuration file entries but beforeadding an application diagram to reverse-engineer these items, only the ASP.NET Web site mightbe reverse-engineered on the diagram. Therefore, the Web service reference might not reverse-engineer as Web service consumer endpoint on the ASP.NET application and a connection to thereferenced Web service might not be reverse-engineered. If the Web reference is for a Web servicethat is not already on the diagram, then an external Web service for the referenced Web servicemight not reverse-engineer.


1. After the application diagram is added, right-click the Web reference in the class library andchoose Update Web Reference.2. Rebuild the class library.

1.48 Changing Table locations may cause connection to fail

When you change the location of a table to a different database at run time, ensure that the newdatabase contains a table that uses the same name as the one found in the original report. If thetable names do not match, the connection will fail.


Make sure that the new database contains a table that uses the same name as the one found in theoriginal report

1.49 Do not use the Null string to set the viewer Selection Formula

To set the viewer selection formula to display all of the records in a report, use the empty stringinstead of the null string. The null string fails to override the original report-selection formula.


The empty string is represented as "" or String.Empty. The null string is represented as null in C# orNothing in Visual Basic.

1.50 Migrating projects encoded in Shift-JIS may result in corrupt characters

Japanese characters encoded as Shift-JIS will not appear correctly in an ASP.NET Web Applicationthat has been migrated from Visual Studio 2002 or Visual Studio 2003 to Visual Studio 2005


Before migration, convert all of your ASP pages to UTF-8


17 of 53 6/9/2014 2:01 PM

1.51 Namespace references lost when importing a project from CrystalReports 9 or Crystal Reports 10

References to the CrystalDecisions.ReportSource, CrystalDecisions.Shared, andCrystalDecisions.Windows.Forms assemblies are lost when a Windows Project from CrystalReports 9 or Crystal Reports 10 is migrated to Crystal Reports for Visual Studio 2005.


Before you compile the application after migration, add the references manually.

1.52 Web service reference in a class library might not reverse-engineer when

a Windows and ASP.NET Web project both reference that same class library.

In this scenario, a Visual Studio solution contains an application diagram with an implementedWindows and ASP.NET application. The solution also contains a class library with a Web referenceto a Web service. The Windows and ASP.NET Web projects both reference this class library. Afterthe class library is built and the necessary entries are copied from the class library's App.config fileto both projects' configuration files, the Web reference might not reverse-engineer as a Web serviceconsumer endpoint on the Windows or ASP.NET application. A connection to the referenced Webservice might also not reverse-engineer. If the Web reference is for a Web service that is notalready on the diagram, then an external Web service for the referenced Web service might notreverse-engineer.


1. Close the application diagram.2. Remove references to the shared class library from the Windows and ASP.NET projects.3. Add the class library reference to the ASP.NET project.4. Open the application diagram.5. Add the class library reference to the Windows project.

1.53 Expanding data files in server explorer in FTP Webs can crash the IDE

If you open a FTP web site and add a data file (MDB or MDF) to the App_Data directory, then openthe Server Explorer window and expand the connection to the data fileunder the Data Connections node, the IDE can crash or hang, and you may lose any unsaved data.


Develop the web site from a local file location using a file system or IIS web site, and use the CopyWeb Site command to transfer files to and from the FTP location.


18 of 53 6/9/2014 2:01 PM

1.54 Printing or Exporting from Firefox may throw an exception

An exception may be thrown when users export or print a report from a CrystalReportViewercontrol. This problem happens when the web page includes a CrystalReportViewer control andMicrosoft Web Controls and is viewed in the Firefox web browser.


Set EnableEventValidation to False in the ASP page to allow users to print or export a report inFirefox.

1.55 Application Verifier is not enabled for mixed mode C++ projects. Instead

it will produce this message:"Application Verifier is not supported for the selected debug mode. Please see

supporting documentation for more information. Click on OK to continue

debugging without verifier"

Application Verifier is not enabled for mixed mode applications even though you will be able toselect it from the Debug menu. A dialog box will appear noting that Application Verifier is notenabled and will allow you to continue debugging without Application Verifier.


Continue debugging without Application Verifier.

1.56 Visual Studio 2005 Team Edition for Testers: Load Test Results are notStored in the Results Database Despite Proper Configuration

Load test results from a local run are not stored in the results database despite proper configurationof the load test. When this occurs, this message is displayed:"The load test results database could not be opened. Check that the load test results databasespecified by the connect string for your Test Controller (or local computer) specifies a database thatcontains the load test schema and that is currently available."The local load test results database is created during the initialization of the first local load test run.This error occurs if the user initiating the first load test run does not have sufficient privileges tocreate the database.


An administrator must initiate the first load test run to force the creation of the load test resultsdatabase.

1.57 Visual Studio 2005 Team Edition for Testers: Load Test Results Stored in

SQL Express might not be Accessible from Remote Computers


19 of 53 6/9/2014 2:01 PM

The SQL Express configuration and the Windows Firewall might block remote access to load testresults stored in SQL Express. A default installation for SQL Express disables remote access to thedatabase. Load Controller setup automatically sets the SQL Express configuration and theWindows Firewall configuration to allow remote access to SQL Express. However, setup on makesthese configuration changes if it also installs SQL Express. Visual Studio setup can also install SQLExpress but does not automatically change the SQL Express and Windows Firewall configuration toallow remote access.

The following message is displayed when the load test results viewer is unable to remotely accessto a load test result in SQL Express:

"Could not read result repository: Could not access the load test results repository: An error hasoccurred while establishing a connection to the server. When connecting to SQL Server 2005, thisfailure may be caused by the fact that under the default settings SQL Server does not allow remoteconnections."


Manually configure SQL Express and the Windows Firewall to allow remote access. Use thefollowing steps to enable remote access to SQL Express:

1. Open the SQL Server Configuration Manager by clicking Start, All Programs, Microsoft SQLServer 2005, Configuration Tools, SQL Server Configuration Manager.2. In the left pane of the SQL Server Configuration Manger, expand the node for SQL Server 2005Network Configuration and select Protocols for SQLEXPRESS.3. In the right pane, right-click Named Pipes and choose Enable.4. Right-click TCIP/IP and choose Enable.5. In the left pane, select SQL Server 2005 Services.6. In the right pane, right-click SQL Server Browser and choose Properties.7. Click the Services tab in the Properties dialog box.8. On the Services page, set the Start Mode property to Automatic and click OK.9. Right-click SQL Server Browser and choose Start.10. Right click SQL Server (SQLEXPRESS) and choose Restart.

Use the following steps to configure the Windows firewall.

1. Open the Windows Firewall dialog box and click the Exceptions tab.2. Click Add Program and Browse to find sqlbrowser.exe and click OK.3. Click Add Program and Browse to find sqlservr.exe. Click OK.4. Click Add Port and enter SQL Service for Name, 1433 for Port number, and select the TCPradio button.5. Click OK on the Windows Firewall dialog

1.58 Interop support of Long (VT_I8) is limited to WinXP

Latebound calls on Win2K or Win9x passing a Long (VT_I8) will fail. WinXP is the only supportedplatform for VT_I8 through OLE automation.


20 of 53 6/9/2014 2:01 PM


Use integer rather than long.

1.59 EnvDTE80.WindowKinds.vsWindowKindImmediate constant is incorrect

The vsWindowKindImmediate constant will not return the correct GUID for the Immediate window


Use the following GUID in place of the vsWindowKindImmediate constant: {ECB7191A-597B-41F5-9843-03A4CF275DDE}Alternatively, the following will get the correct Immediate Window GUID: DTE.Windows.Item("Immediate Window").ObjectKind

1.60 Shared Add-in wizard Setup project will not work on a computer that only

has Microsoft Office

Add-ins for Office require Extensibility.dll in order to run, which is not automatically included in theSetup project for Shared Add-ins.


In the Solution Explorer, right-click on the Add-in Setup project and select Add | Assembly. In the.NET tab, select Extensibility and press OK. Once the assembly is added, select it in the SolutionExplorer and ensure that the Register property is set to vsdraDoNotRegister

1.61 Fonts and Colors options are not reflected immediately upon reset.

A reset of environment settings can be performed by clicking Tools > Import and Export Settings...and choosing "Reset all settings". A reset of environment settings can also be performed by issuingthe command "Tools.ImportAndExportSettings /reset" inside the Command Window. In either case,the fonts and colors options are not reflected until a restart of Visual Studio.


After performing a reset operation, restart Visual Studio.

1.62 Application Verifier is not supported for DLL based projects, ATL web

service projects, and VC Smart Device projects .

Application Verifier is not supported for the following scenarios:1. Using Start With Application Verifier on a DLL project and loading it in an executable that is not


21 of 53 6/9/2014 2:01 PM

part of the solution.2. Changing the Command in Project Properties | Debugging to something other than the currentlyloaded project ($TargetPath). This applies to remote debugging as well.3. Application Verifier is not supported for ATL web service projects as these run under a differentprocess.4. Application Verifier is not supported for VC Smart Device projects as these run under a differentarchitecture.Application verifier is enabled only for the exe projects loaded in the IDE.


For scenarios 1 & 2 above, load the project of the target executables in the IDE and then useApplication Verifier. Using Application Verifier in all the above cases will work the same as a normaldebug session (Debug | Start).

2. .NET Framework

2.1 Manual test files with DBCS (double-byte character set) are not displayed

properly when running.

When you run a manual test file with DBCS in the name, you will see the manual test result window.However, the manual test is not displayed properly in that window. If you right-click on the lowersection of the window, and select Refresh, the section will hang for a few minutes and then turnblank.


Use SBCS (single-byte character set) to name your manual test files. If you want, you can use"DBCS" in the description of the manual tests.

2.2 Wrong version of msvsmon.exe gets launched on 64-bit computer running

32-bit Visual Studio 2005 and SQL Server 2005.

SQLCLR debugging will fail on a 64-bit computer, when Visual Studio 2005 (x86) and SQL Server2005 (x86) are installed. The following message is displayed:

---------------------------Microsoft Visual Studio---------------------------Unable to debug .NET code. Could not attach to SQL Server process on ''. The 64-bit version of theVisual Studio Remote Debugging Monitor (MSVSMON.EXE) cannot debug 32-bit processes or32-bit dumps. Please use the 32-bit version instead.---------------------------OK---------------------------


22 of 53 6/9/2014 2:01 PM

The 64-bit version of msvsmon.exe gets launched automatically because the operating system onthe computer is 64-bit. The 32-bit version should be launched instead because both applicationsare 32-bit. This is an architectural problem that can not be fixed at this point.


The user can manually launch the 32-bit version of msvsmon.exe when trying to do SQLCLRdebugging on the local computer.

It is not recommended that the 32-bit version of msvsmon.exe be registered to launch automatically,because this would break other 64-bit debugging scenarios.

2.3 AuthorizationStoreRoleProvider: Incorrect or obscure errors are returned

from Authorization Manager

The AuthorizationStoreRoleProvider depends on Authorization Manager. Not all error messagesreturned from AuthorizationManager indicate the root cause of a problem. Listed below are errormessages that are known to be either incorrect or vague.

"COMException (0x8007052b): Unable to update the password. The value provided as the currentpassword is incorrect."This error is really an access denied error. If all of the following conditions are met, this error canoccur: ASP.NET is deployed on IIS 5.0, Windows XP IIS 5.1, or in IIS 5.0 isolation mode onWindows Server 2003, the application is configured to use Integrated Windows Authentication, andthe policy file is located inside of the directory structure of the current ASP.NET application. IfASP.NET is running as a local computer account and attempts to access a policy store in a remoteAD or ADAM instance this error can also occur.

"More data is available"This error really means that the policy store could not be found. If the connection string points at anADAM instance, but the connection string references an ADAM partition that does not exist, thiserror can occur. For example, in the following connection string LDAP://localhost:4000/Cn=storename, DC=Partition1, if Partition1 does not exist in the ADAM instance, this error willoccur.

"The specified server cannot perform the requested operation"This error really means that the specified server could not be found. If the connection string pointsat a non-existent server, or uses a port number that AD or ADAM are not listening on, this error canoccur.

"ArgumentException: The parameter is incorrect"This error message really indicates that an LDAP query group in Authorization Manager used todetermine if a user is in a role is invalid.


For each error condition listed above, review the possible causes. If an application's configuration


23 of 53 6/9/2014 2:01 PM

matches one of the possible causes, change or fix the application's configuration based on theinformation listed above.

2.4 SQL Server Express User Instances Should be Disabled on SharedHosting Computers

ASP.NET 2.0 integrates with SQL Server Express 2005 to provide automatic creation of thedatabase required by many of ASP.NET 2.0's new application services. This functionality relies onSQL Server Express' support for spawning server processes that run with the identity of either theinteractive user or the identity of the worker process hosting ASP.NET. In un-trusted environmentssuch as on a shared hosting server, the ability to spawn SQL Server worker processes should notbe enabled due to the potential for unintentionally sharing data between ASP.NET applications.


If you are installing SQL Server Express using the standalone installer, you can use the advancedsetup options to explicitly disable support for user instancing.

Alternatively you can manually disable user instancing for an existing SQL Server Expressinstallation as follows:1. While logged in as a local box administrator, open a command window by running cmd.exe2. If osql.exe is not available from any directories listed in the PATH environment variable, changedirectories to the SQL Server Express directory that contains osql.exe.3. Connect to the parent instance of SQL Server: osql E S .\sqlexpress4. Issue the following Sql commands:exec sp_configure 'show advanced option', '1'goreconfigure with overridegoexec sp_configure 'user instances enabled', 0 goreconfigure with overridego

2.5 Persistent cookies for forms authentication now use the same timeoutsetting as session based cookies.

In previous versions of ASP.NET, persistent forms authentication cookies had a hardcoded lifetimeof 50 years. In ASP.NET 2.0 persistent form authentication cookies have their expiration date set tothe current date time plus the value of the "timeout" attribute from configuration. By default thismeans persistent cookies will have a lifetime of 30 minutes. If you want a longer lifetime you willneed to increase the value of the "timeout" attribute. In ASP.NET 2.0 this means that formsauthentication tickets stored in both session-based and persistent cookies will use the new timeoutvalue



24 of 53 6/9/2014 2:01 PM

If different timeout values are desired for persistent cookies, a developer can get a reference to theforms authentication cookie after initially setting the cookie with a method likeFormsAuthentication.SetAuthCookie. A developer can then get a reference to the cookie with a callto: Response.Cookies[FormsAuthentication.FormsCookieName]. On the resultant HttpCookie adeveloper can then set the Expires property to a different value.

2.6 Incorrect behavior of DeleteRole method on the

AuthorizationStoreRoleProvider

The DeleteRole method on the provider incorrectly throws an exception stating "Element not found"if an attempt is made to delete a non-existent role. The provider should be returning false instead.Also, if an attempt is made to delete a role that has existing users in it, the provider will return falseinstead of throwing an exception.


1. Wrap all calls to the provider's DeleteRole method inside of a try-catch block. This will ensurethat any future fixes that re-enable exceptions when deleting populated roles will not impact existingcode.2. Check to see if the role exists prior to attempting to delete the role.

2.7 ASP.NET Profile feature can fail when using Xml serialization and anon-default application identity

The default property serialization mechanism for the ASP.NET Profile feature is Xml serialization. Ifthe ASP.NET process identity is something other than ASPNET (on IIS 5.0 and IIS 5.1) orNETWORK SERVICE (for IIS 6), then the Xml serialization process will fail with an exceptionstating "InvalidOperationException: Unable to generate a temporary class." The same problem willoccur if using application impersonation. These exceptions occur because the XmlSerializer writestemporary class files into the %windir%\temp directory. By default this directory only grants " ListFolder/Read Data" permissions to the default ASP.NET accounts. Non-default ASP.NET accountsare able to write temporary files into this directory, but do not have the necessary privilege tosubsequently find the temporary classes for use by the XmlSerializer.


For secure environments, developers should use a different serialization mechansim - either binaryserialization or string serialization. For applications where the potential for accidentally sharingtemporary class files across applications is not high, the worker process or applicationimpersonation identity can be granted the "List Folder/Read Data" privilege on the %windir%\tempdirectory.

2.8 ASP.NET Session State Limitations when using SSE


25 of 53 6/9/2014 2:01 PM

SSE should only be used in development environments with ASP.NET Sql Server based sessionstate because there is no Sql Server Agent service installed with SSE. As a result the session statecleanup job never runs and session state data will accumulate in the database. You can manuallycleanup expired sessions by connecting to SSE and running the following command: "EXECUTEDeleteExpiredSessions".


Use one of the standard versions of Sql Server 2005 for production applications.

2.9 AuthorizationStoreRoleProvider: Default value for ApplicationName

results in an error from Authorization Manager.

Authorization Manager does not allow the "/" character in application names. In the absence ofapplicationName being set in configuration, the AuthorizationStoreRoleProvider follows the samelogic used by other ASP.NET providers to determine a default value for applicationName. Whenrunning within ASP.NET, this results in a value that starts with the "/" character.


Always set the applicationName attribute in configuration when using theAuthorizationStoreRoleProvider within an ASP.NET application.

2.10 On Windows 98 and Windows ME, debugging an application thatconsumes a Web Service causes the application to hang

In Visual Studio 2005, when debugging an application on Windows 98 or Windows ME thatconsumes a Web Service, the application hangs.


Disable the debugger component csm.dll, and use breakpoints to stop in the Web Service.

To disable csm.dll, please follow the instructions below:

1) On the Windows Start meu, select Run.2) In the Run dialog, type regedit.exe.3) Goto HKEY_CLASSES_ROOT\CLSID\{12A5B9F0-7A1C-4FCB-8163-160A30F519B5}.4) Verify that you are on the right registry key by checking that InprocServer32\(default) has thevalue ' :\Program Files\Common Files\Microsoft Shared\VS7Debug\csm.dll'.5) Delete the registry key (HKEY_CLASSES_ROOT\CLSID\{12A5B9F0-7A1C-4FCB-8163-160A30F519B5}).

2.11 C# Code Snippet shortcuts cannot contain non-spacing marks.


26 of 53 6/9/2014 2:01 PM

C# Code Snippets are defined in XML within .snippet files. One of the possible tags in the schemais a tag. Shortcuts can be used to quickly insert a snippet. To do so, a usersimply needs to type the shortcut string and then press Tab.

Many unicode characters are allowed within shortcut strings, but non-spacing marks found incomplex script languages are not recognized as valid shortcut characters. This means that somestrings in complex script languages cannot be used as shortcuts. If a shortcut does contain anon-spacing mark, typing the shortcut string and pressing Tab will insert a Tab character but will notinsert the snippet code.Note: The snippet shortcut will still appear in IntelliSense.


1. Choose a Unicode shortcut name that does not contain a non-spacing mark.2. Insert the snippet through the Snippet Picker UI instead of using shortcuts.

2.12 System.Net has removed the logic to time out a DNS resolve when the

timeout is less than the timeout in the unmanaged API that is called by

System.Net to perform the resolution.

In previous versions of the .NET Framework, System.Net's DNS added timeout logic to the Dnstype in order to circumvent the lengthy native timeout. Without an accurate DNS timeout, it is notpossible to set accurate timeouts for other web requests. However, to implement this timeout, theDNS resolve is offloaded to a separate thread. If the thread pool level is low, the DNS resolve maywait for an available thread until it times out, resulting in an exception being thrown. To avoid thisexception, the DNS timeout logic has been removed.



2.13 SqlCacheDependency requires initialization with a call to

System.Data.SqlClient.SqlDependency.Start

Due to changes in how query notifications work with SQL Server 2005, developers must call theStart method on SqlDependency at least once prior to using SqlCacheDependency. A logical placeto call Start is inside a web application's Application_Start method located in global.asax:

void Application_Start(object sender, EventArgs e){System.Data.SqlClient.SqlDependency.Start("connection string");}

The connection string must be the same one that will be used when issuing commands for use withSqlCacheDependency.


27 of 53 6/9/2014 2:01 PM

2.14 System.Net no longer adds a CRLF character when callingWebClient.UploadValues()

In previous versions of the .NET framework, calls to WebClient.UploadValues() would add a CRLFto the uploaded content resulting in server application failures. The CRLF characters violate theapplication/x-www-form-urlencoded content type encoding scheme, as described in the HTML 4.01specification. The CRLF is no longer added.


Use WebClient.UploadData() to add the CRLF and recompile your application or fix the serverapplication to not expect the CRLF character.

2.15 UriBuilder no longer clears the Fragment or Query properties after theyare set

UriBuilder is a type that allows building a Uri instance piece by piece. In previous .NET Frameworkversions, Query properties and Fragment properties could not be set at the same time. This errorhas been fixed in version 2.0. Query and Fragment properties are now set without having any fieldsinadvertently cleared. Applications that have worked around the previous behavior may need toadjust their logic to avoid erroneous behavior.



2.16 The permissions demanded before applying the values present in the

system.net element of an application configuration file have changed.

The permissions required to apply the settings present in the System.Net element of an applicationconfiguration file are changed from previous .NET framework versions. The permissions required toapply values from the configuration file are now the same as those required by the associatedproperty when changing the setting in code.



2.17 Sending an FTP request followed by an FTP request over SSL (FTPs) to

the same directory throws a file cannot be found exception

If an application issues a FTP request to a server, and then issues another FTP request, with SSL


28 of 53 6/9/2014 2:01 PM

enabled to the same server and path, the second request will fail. A file not found exception will bethrown. However, if the second request is not to the same path, the request will succeed.

2.18 WebRequest.ServicePoint.Address demands unrestricted webpermission only when the service point in question is a proxy server

This new demand prevents applications running in partial trust from discovering network proxyaddresses. Partially trusted applications using ServicePoint.Address API may get aSecurityException if the address points to a proxy server.


Use HttpWebRequest.Address

2.19 Exceptions to Parity between 32-bit and 64-bit behavior for Visual Studio

and .NET Framework

1. Front Page Server Extensions for IA64 WOW64

When using .NET Framework 1.1 to author a website on a remote IA64 computer running .NETFramework 1.1, FrontPage will not be a supported mechanism. Some basic functionality will workvia the fileshare mechanism.

2. J# does not support running on native 64-bit. J# code can only run in WOW64 on 64-bitplatforms.

3. SQL Server Express is not supported on 64-bit for .NET Framework 2.0.

4. There are no peformance or scalability guarantees for high-load ASP.NET applications runningon .NET Framework 1.1 in WOW64 for IA64.

5. Data breakpoints do not work with Visual Studio 2005 running on IA64 in WOW64.

6. In Visual Studio 2005, the Edit and Continue debugger feature does not work on 64-bit

7. In Visual Studio 2005, VC ATL exceptions:

- Build system doesn't register dlls targeting 64-bit on wow64

- Error ""%1 is not a valid Win32 application"" when debugging default ATL Server project on 64-bitcomputer.

- Executable to debug and URL are not prepopulated for ATL Server projects with 64-bitconfigurations


29 of 53 6/9/2014 2:01 PM

- Internet Explorer does not come up with .srf file specified by user when debugging 64-bit ATLServer project.

- Debugger type for ATL Server 64-bit configuration defaults to local windows debugger instead ofweb service debugger

- Debugging properties are not propagated to new configurations in a project. This means, forexample, that if you start out with an ATLServer project in x86 and then create a 64-bit configurationfor it, debugging will not work without changing the debuggee to be Internet Explorer.

8. There is no support for interop debugging (managed + unmanaged mixed-mode debugging) in64-bit.

9. Some MDAs are not supported on 64-bit for example: Re-entrancy, LoaderLock,PInvokeStackImbalance

10. MMX intrinsics are not supported by the IA64 and x64 C++ compilers.

11. Inline assembly is not supported by IA64 and x64 C++ compilers.

12. Most High Level Language constructs are not supported by x64 MASM.MASM does not support IA64, but we ship Intel's assembler (ias.exe)

13. In Visual Studio 2005, VC++ compiler switch /ARCH:SSE is not supported by x64 and IA64VC++ compilers.

14. The System.Diagnostics.Process.MainModule and System.Diagnostics.Process.Modules APIswill fail if running under the WOW64 on a 64bit child process.

15. 32bit and 64bit COM+ serviced components with the same GUID/CLSID cannot be registered atthe same time.

16. 64-bit SDK does not include native DBGCLR. DBGCLR will be WOW64 only.

17. 64-bit SDK does not include a native DEXPLORE.EXE. DEXPLORE.EXE will be WOW64 only.

18. There are no bootstrapper manifest packages for x64 and IA64

There is no 64-bit bootstrapper for ClickOnce or other applications. On any 64-bit computer that has.NET Framework installed, if you try to install a ClickOnce application, it fails with the messageThis version of the .NET Framework 2.0 is not supported on a 64-bit operating system. Contactyour application vendor.

This even happens for applications that are authored as 32-bit only and would have run in WOW64.

19. Visual Studio 2005 does not install on IA64

Visual Studio 2005 will not install on IA64 (no design time support for IA64). Visual C++ will have a


30 of 53 6/9/2014 2:01 PM

native IA64 command line tools installer.

20. Only Visual Studio Team System will allow building applications that target IA64

21.P/Invoke signatures with blittable types are treated differently on 64-bit because P/Invoke isimplemented differently on 64-bit, hence there are cases where incorrect P/Invoke signatures thataccidentially worked on 32-bit don't work on 64-bit.

22. Visual Studio 2005 Tools for Office is not supported on 64-bit.

2.20 When performing a refactoring operation in a C# web site, build errorsmay be reported when none actually exist

In certain cases, when performing a refactoring command in a C# web site that contains no builderrors, the user may get a warning indicating that the project or one of its dependencies does notcurrently build and that references may not be updated.This dialog can be safely ignored by clicking on the Continue or Preview buttons. The refactoringwill succeed and all references will be updated.

The following are examples of common project configurations in which this warning will be shown:- Web projects migrated from previous versions of Visual Studio, which contain a global.asax file inthe web directory and a global.asax.cs file in the App_Code directory.- Web projects in which web pages reference web user controls which in turn reference typesdeclared in the App_Code directory.


There is no known resolution. However, the warning can be safely ignored.

2.21 System.Net now registers a default FtpWebRequest implementation that

may cause applications using their own FTP component to break

Prior to .NET Framework version 2.0, applications could register a component to handle FTPrequests using System.Net's extensible pluggable protocol framework. Components for handlingdifferent web requests are registered by associating the component with a specific URI prefix. Anyweb request that matches that prefix is then handled by that component. In .NET Framework 2.0,System.Net now supports an FtpWebRequest component that is registered by default for the ftp:prefix. Any applications that are registering for this prefix (prior to this release) could now be brokenbecause the prefix (FTP) is already taken.


Update the application configuration file to remove the default FTP protocol component prior toregistering your own FTP component:


31 of 53 6/9/2014 2:01 PM

2.22 In .NET Framework 2.0, GlobalProxySelection.Select behaves differently

than in version 1.1 when an empty System.Net tag is present in the

machine.config file

In version 1.1 of the .NET Framework, specifying an empty System.Net element in themachine.config file, GlobalProxySelection.Select returns an empty web proxy instance indicatingthat no proxy is to be used. In version 2.0, the new default is that the system proxy settings (sameas what is specified in Internet Explorer) will be used in this case.


Modify the machine.config file to disable the default proxy as shown below.

2.23 System.Uri does not include the IPv6 scope ID with the host.

In previous .NET Framework versions, if you created a Uri instance using an IPv6 address, thescope ID is always included with the host address. The scope ID refers to the index of a localnetwork adapter, and has no meaning for a remote host. The scope ID also uses a '%' character inits syntax, which conflicts with the Uri escaping format of '%hh'. Including the scope ID in the hostbreaks System.Uri's ability to interoperate with other URI parsers and resolvers. In version 2.0,System.Uri no longer includes the scope ID with an IPv6 host in a Uri instance. System.Uri has alsoadded a new property, DnsSafeHost, which will return the scope ID with an IPv6 host address.


Use Uri.DnsSafeHost which will return the scope ID with an IPv6 host address

2.24 Specifying a cluster as a remote proxy through System.Transactions

configuration may throw a TransactionException during cluster failover

If a cluster is specified as a remote proxy in configuration by setting theDistributedTransactionManagerName to a cluster, a TransactionException may be thrown duringcluster failover.



32 of 53 6/9/2014 2:01 PM

To specify a cluster as a remote proxy, use the Component Services MMC to configure MSDTC touse the cluster as the remote MSDTC.

2.25 The message, "Microsoft C# 2005 IntelliSense has encountered aproblem" can appear when performing various actions in the IDE.

In certain cases, the message "Microsoft C# 2005 IntelliSense has encountered a problem. We aresorry for the inconvenience" can appear while performing various actions in the editor. The reasonin most cases is there is a failure with retrieving the source data.

Some examples of actions that could trigger this message include:- Renaming an external alias.- Performing a "find all references" in a web project with no 'runat="server"' attribute.

This is a non-fatal condition. Clicking the send report button will allow a user to safely continueworking as expected and no data will be lost.


There are two possible options to turn off display of all non-fatal error message from the C#language service. To do this, modify the registry under the registry path:

[HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0\CSharp\Options\Editor]

(1) "Watson_ReportExceptions"=dword:00000001Adding the following registry key with the specified value will disable error reporting completely.

Note: Using this registry key and turning off all non-fatal error messages from the C# languageservice can potentially prevent gathering feedback on scenarios not related to this failure.

(2) "Watson_DeferSendingUntilLater"=dword:00000000Adding the following registry key with the specified value will turn of the display of the message butwill continue to send feedback to Microsoft. The IDE will be unresponsive for a brief period asinformation is collected to send.

2.26 NullReferenceException thrown trying to get the transaction's

DistributedIdentifier during transaction promotion

Attempting to get the DistributedIdentifier on a Transaction while the transaction is promoting maycause a NullReferenceException to be thrown.


There are two ways to work around this issue.


33 of 53 6/9/2014 2:01 PM

Ensure that access to the transaction is synchronized.

-or-

Ensure that the transaction has promoted before checking the the DistributedIdentifier property.

2.27 ASP.NET Web Service proxies generated using Add Web Reference will

all use the same URL taken from the configuration file even if the service hasmultiple endpoints with different URLs

When adding a Web Reference in Visual Studio 2005, the URL of the service is automaticallypicked up from the AppSettings section in the configuration file. If the web service has multipleendpoints with different URLs, multiple proxy types will be generated but they will all use the sameURL value taken from the configuration file.


There are two possibilities:1. Edit the WSDL document and break out each service into a separate document.

-or-2. Edit the configuration file to add a key for each Web service and then read the values out in yourcode using System.Configuration.ConfigurationSettings.AppSettings. Set the URL property on yourproxy instances using these values.

2.28 Support for Nullable by default in generated ASP.NET Web Service

proxies can break existing code when proxy is re-generated

When importing a schema that contains the nullable="true" attribute for an ASP.NET Web Service,the generated proxy will contain Nullable types, whereas previously the attribute was ignored.This change may cause design time or runtime breaks in applications.


Possible workarounds are to avoid regenerating your proxy types, to recompile your code using thenew Nullable pattern, or to change the schema to not use the nullable="true" attribute.

2.29 Setting the Proxy property to null on a web service proxy instance doesnot cause the request to go directly to the server

Setting the Proxy property to null on a web service proxy instance should force the request tobypass any web proxy server settings and go directly to the server. However, this functionality doesnot currently work. The null value will be ignored and any configured web proxy server settings willbe used instead.


34 of 53 6/9/2014 2:01 PM


You can set the Proxy property on the underlying WebRequest directly by deriving from the proxytype and overriding the GetWebRequest method:

protected override WebRequest GetWebRequest(Uri uri){WebRequest req = base.GetWebRequest(uri);req.Proxy = this.proxy;return req;}

2.30 Using .NET Remoting and Runtime Serialization across different versions

of the .NET Framework

When exchanging data between an application running on one version of the .NET Framework andan application running on another version (using .NET Remoting or Runtime Serialization),exceptions may be encountered while serializing or deserializing certain Framework types. Theseexceptions indicate that these types are incompatible across the different Framework versions that is, it is impossible to send them from one version of the Framework to another.

.NET Framework 2.0 includes a technology called Version Tolerant Serialization that eliminates thisproblem. However, previous versions of the Framework still face this issue. Thus, a patch will bemade available that adds some Version Tolerant Serialization capabilities to .NET Framework 1.1.This patch will require Service Pack 1. After installing the patch, an application running on thepatched Framework will be able to communicate with an application running on .NET Framework2.0 without encountering this versioning issue. There are no plans to provide such a patch for .NETFramework 1.0.

It is worth noting that Version Tolerant Serialization only addresses versioning when using BinarySerialization, either directly or through .NET Remoting. When using SOAP serialization (eitherdirectly through the SoapFormatter class or through .NET Remoting) across different versions ofthe Framework, the versioning issues discussed above may still be encountered.


To obtain this patch, please see the following Knowledge Base article: http://support.microsoft.com/?kbid=907262.

2.31 Specifying a non default trace listener for System.Transactions tracing

does not work in partial trust

Specifying a specific trace listener for System.Transactions tracing in the configuration is notsupported in partial trust and will cause an exception to be thrown.



35 of 53 6/9/2014 2:01 PM

The default trace listener is supported in partial trust, so if no listener is specified in configuration,the traces will be caught by the default listener and printed to debug.outputstring. These traces canbe viewed in partial trust by using DBMon.exe.

2.32 Date and Time calculations in Web Services or XML Serialization

scenarios may be incorrect after migrating to .NET Framework 2.0

.NET Framework 2.0 changes the way dates and times are written to and read from XML. Thischange mostly affects the following scenarios:- Using times with an unspecified time zone or times in the UTC time zone- Interoperability scenarios with 3rd-party software that writes out time values to XML withoutspecifying a time zone or specifying the UTC time zone

The changes may cause certain date and time calculations and comparisons to become incorrect.In these cases, it may be necessary to revert to the earlier date/time behavior.


To revert to the earlier date/time behavior, apply the following configuration change:

2.33 Windows User Profiles for ASP.NET Automatic Database Creation with

SQL Server Express and IIS

The ASP.NET automatic MDF creation process for SQL Server providers using SQL ServerExpress (SSE) and IIS only works when IIS is running either as the local ASP.NET computeraccount, or as NT AUTHORITY\NETWORK SERVICE. The automatic creation process also workswhen a developer is interactively developing using Cassini (i.e. file based webs). However, whendeveloping against IIS using either a different local computer account, or a domain user account,the automatic database creation process will fail because these accounts do not have a Windowsuser profile available on the web server.


There is no resolution for this issue. Automatic database creation with SSE for IIS-based websiteswill only work for the ASPNET and NETWORK SERVICE accounts.

2.34 Unicode Surrogate Behavior with ASP.NET Providers that use SQL

Server 7.0 or 2000

ASP.NET providers that use SQLServer are constrained to the level of Unicode surrogate support


36 of 53 6/9/2014 2:01 PM

provided by SQLServer 7.0 and SQL Server 2000. SQL Server 7.0 and 2000 store and retrievesurrogate pairs losslessly. However, there is no linguistic comparison for surrogates. Surrogatecharacters are ignored during comparison operations and during uniqueness checks when usingthese versions of SQL Server. For example this means the SqlMembershipProvider will considertwo usernames that only include surrogate characters to be identical. This behavior will lead to auniqueness constraint violation if an attempt is made to create a second user with a username thatdiffers from an existing user only in surrogate characters.


There is no known resolution for these versions of SQL Server.

2.35 FileWebRequest.PreAuthenticate only returns false

Types that inherit from WebRequest inherit a PreAuthenticate property. This property is used toenable sending authentication information along with the request without waiting for a challengefrom the server. FileWebRequest does not support preauthentcation, so its PreAuthenticateproperty should always return false. In previous .NET Framework versions, if the PreAuthenticateproperty was set to true by an application, it would return true when its value was later queried. Thisis no longer the case. FileWebRequest's PreAuthenticate property will always return false.


Users should not use the PreAuthenticate property on FileWebRequest.

2.36 Using generic types with .NET Remoting and SOAP Serialization

The .NET Remoting technology supports both binary and SOAP serialization that is, remotingmessages may be represented in a Microsoft-specific binary format or as SOAP XML. However,generic types (which are a new feature in .NET Framework 2.0) may only be used with binaryserialization. The usage of generics with SOAP serialization is not supported, neither through .NETRemoting nor by using the SoapFormatter class directly.


There is no known resolution for this issue.

3. Smart Device Programmability

3.1 F11 into a DLL function is not working for X86 SmartDevice Project

1. Create a Win32 smart device project Dll with a function DllFunc with any piece of code with thisfunction exported by the dll targeting x86 platform.2. Create a Win32 smart device project exe that does a LoadLibrary on this dll and invoked the


37 of 53 6/9/2014 2:01 PM

DllFunc added to the same solution. Make sure this is set as the startup project.3. Compile, Deploy and Debug the solution.4. Try to step into (F11) into the DllFunc. F11 turns into F10 on this special DllFunc() gotten fromGetProcAddress and only on x86 platform.


View DllFunc on the debugger window to get the hex address and then setting the breakpoint onthe disassembly.

3.2 Managed attaching to a native process does not return an error

1. Create a native Console SmartDevice Project.2. Hit Ctrl F5.3. Select Tool \ Attach To Process.4. Select the Smart Device Transport & your target device.5. Select Managed debugger in the Debug engine selection dialog.6. Select your native process & attach.7. You will observe no messages.



3.3 Applying filter in break mode to an already existing breakpoint causes the

breakpoint to be ignored.

1) Create a Native application with the following codevoid foo(void){ }

int _tmain(int argc, _TCHAR* argv[]){ int i = 0;

foo();

return 0;}2) Set a location breakpoint on "return 0;"3) Set a function breakpoint on foo() at design time.4) F10 to get the application into break mode.5) Open the breakpoint window and edit the filter property of function breakpoint (by including thefilter ProcessName or ThreadName)


38 of 53 6/9/2014 2:01 PM

6) Continue (F5)7) The function breakpoint is not hit and instead we break at "return 0" statement.

The above scenario illustrates that modifying a design time breakpoint by editing the filter propertiesat break mode causes the breakpoint to be ignored.This is true for all kinds of breakpoints.


Set the breakpoint and apply the filter at design time itself. This applies only to ProcessName,ThreadName filters as ThreadId and ProcessId are not known at design time.

3.4 In Native Debugging, F10/F11 translate into a step over the body of while

loop and related constructs if the body of the loop construct spans on a single

source line.

F10/F11 do not work properly in scenarios illustrated by example below.

Example Code Snippet

1 int i = 0;2 while (i < 1000) { i++; }3 return 0;

Steps:-Press F9 on line 1 and then after the breakpoint is hit on this line press F10-Now the control is on line 2-Press F10 yet again

The issue after performing the above steps is that the debugger would stop/break at line 3 and notat line 2. That is, the breakpoint on line 2 gets ignored for repeated F10.Please note that this happens for all loop constructs that span a single source line.


Place a breakpoint with F9 on the source line with the while loop (line 2). Then the debugger wouldbreak at each F10 on line 2 while stepping through the while loop (till i increments to 1000) .

-or-

If code can be edited, re-organize the above code as follows and everything would work asexpected. 1 int i = 0; 2 while (i < 1000) 3 { i++; }


39 of 53 6/9/2014 2:01 PM

4 return 0;

3.5 Native assert dialogs for Smart Device applications may render buttons

off the screen

When an assert dialog is thrown by a Visual Studio 2005 C++ Smart Device application on a PocketPC or Smartphone, the buttons on the dialog may render off the screen


Use the scroll buttons/keys of the Pocket PC or Smartphone to manually scroll to the button.

3.6 "Copy if newer" Property semantics for Smart Device projects

In smart device projects, newness of a dll or exe file is determined by comparing the Win32versions.- If the device-side version is less than that of the desktop, the file is copied.- If the device-side version is greater than that of the desktop, the file is not copied.- If the checksums are different, the file is copied.

Newness of files other than dll and exe is based solely on checksum.Newness is not based on timestamp or size.



3.7 Visual Studio 2005 will connect to an ActiveSync device if there is an error

connecting to a TCP/IP device.

When one device (e.g. PPC) is connected through ActiveSync and you want to connect to a WinCEdevice (e.g. CEPC) through TCP/IP, if the TCP/IP connection to WinCE device fails for somereason, Visual Studio 2005 will connect to the device connected through ActiveSync.


Disconnect the device connected through ActiveSync before attempting TCP/IP connection toanother device.

3.8 Deploying an MFC dll with automation support and dynamically linked to

MFC library will fail with the error 0x8007007e while registering.


40 of 53 6/9/2014 2:01 PM

While deploying an MFC dll project with automation support and dynamically linked to MFC library,Visual Studio 2005 deploys the dll along with required dependent dlls to device under project folder.LoadLibrary() used for registering the dll looks for dependent libraries in the directory whereconman components are located and then in \Windows directory. For this reason the dll registrationfails.


Manually move or copy the required dependent dlls from the project folder to \Windows directory onthe device.

3.9 Connectivity to Device Emulator unstable when using wireless networks

that have DHCP servers configured with short lease times

On wireless networks, TCP/IP connectivity to the device emulator through Virtual Switch drivercould be unstable. This is caused by the interaction of the DHCP server implementation, the VirtualSwitch driver, and the 802.11 specification.


For stable connectivity to device emulator one of the following transports could be used.1. DMA transport

-or-2. TCP/IP transport over loopback adapter.

3.10 MUI: Localized remote tools fail to connect to device emulator when rununder non-matching system locale

When a localized version (e.g. Japanese) of Visual Studio 2005 is installed on a English MUI OS,remote tools will fail to connect to the device emulator. This is because remote tools always use thesystem locale. For the same reason, when two different locales of Visual Studio 2005 (e.g.Japanese and English) are installed side-by-side on a English MUI OS, remote tools will alwaysconnect to the English device emulator.


Change the system locale to match the Visual Studio 2005 locale.

3.11 Debugging experience sometimes is bad with default project settings for

SmartDevice VC++ applic

Visual Studio 2005 Known Issues

Documents

Transcript of Visual Studio 2005 Known Issues