For more information about how to install Visual Studio, see Installing and Maintaining Visual Studio on the MSDN Web site.
To resolve this issue:
There's no workaround available.
This installation scenario is not supported for Microsoft Help 3.0 Beta 1.
To resolve this issue:
Uninstall Microsoft Help 3.0, and then run the installer again to fix any issues with this product.
After the .NET Framework 4 is uninstalled, repair of Visual Studio 2010 displays a message about error 1304.
To resolve this issue:
1. On the Visual Studio 2010 installation media, run \WCU\dotNetFramework\dotNetFx40_Full_x86_x64.exe, to install the .NET Framework 4 on the computer.
2. After the .NET Framework 4 is installed, go to the program installation section of the Windows Control Panel.
3. Double-click the Visual Studio 2010 installation you want to repair (either "Microsoft Visual Studio 2010 Team Suite Beta 1" or "Microsoft Visual Studio 2010 Professional Beta 1") to get Maintenance Mode options.
4. Select Repair.
When Visual Studio is being installed, a failure in the installation of a component results in the following line in the logs:
...: MSI Record result detail error code: 1935
To resolve this issue:
Error 1935 typically means that a file has put a lock on a file so that it cannot be overwritten.
Reboot the computer and try to install Visual Studio again. If a file was locked during installation, then rebooting will release the lock and Setup should be able to continue.
Visual SourceSafe does not install the registry keys that are required by the Visual Studio 2010 IDE. Therefore, it cannot be used in an integrated fashion with Visual Studio 2010 Beta 1. It can be used side-by-side with Visual Studio 2010 Beta 1 from the Visual SourceSafe Explorer. An update to Visual SourceSafe 2005 to enable this functionality is planned for a later release.
To resolve this issue:
There's no workaround available.
Installing Visual Studio English and then installing Visual Studio Japanese does not install the .NET Framework Japanese Language package.
To resolve this issue:
Look for "Microsoft .NET Framework 3.5 Language Pack SP1 - JPN" in the program installation section of the Windows Control Panel.
If this entry is not present and you require the Japanese .NET FRamework 3.5 Japanese strings, then you can get the language pack as follows:
1. Click the appropriate one of the following links.
X86: http://go.microsoft.com/fwlink/?LinkId=118096
X64: http://go.microsoft.com/fwlink/?LinkId=118114
2. Run the program, and then follow the instructions.
When you try to install the SQL Server 2008 original release version or SQL Server 2005 original release version, SQL Server 2005 SP1, or SQL Server 2005 SP2 on Windows 7 RC, you will receive a warning message that SQL Server has known compatibility issues with this version of Windows. The issues that trigger the compatibility warning have been fixed in SQL Server 2008 SP1 and SQL Server 2005 SP3. Because SQL Server 2008 original release version is redistributed by Visual Studio 2010 Beta 1, installations in which the user selects to install SQL Server together with Visual Studio may be affected.
To resolve this issue:
1. Start Visual Studio 2010 Beta 1 Setup and make sure to select "Microsoft SQL Server 2008" as an installed component.
2. When SQL Server 2008 installation starts, you will receive a compatibility warning dialog box.
3. In the dialog box, select "Run Program" to continue to install SQL Server.
4. You will then receive another compatibility warning when you run "Setup.exe". Select "Run Program" again.
5. After installation is complete, start Windows Update.
6. Click "Check for Updates".
7. Under the optional updates, you should see "Microsoft SQL Server 2008 Service Pack 1". Select it and then click "OK".
8. Windows Update will then install SQL Server 2008 SP1.
9. When installation is complete, you may be prompted to reboot.
When a custom Visual Studio Team Suite Setup is performed, if Test Tools are excluded, the Test Impact View Package will display an error message.
To resolve this issue:
Skipping the package load issue will prevent the message from appearing again. If Test Tools and Test Impact functionality is required:
1. Run Visual Studio Team Suite Setup.
2. Select Repair Mode.
3. Select Test Tools.
4. In the Visual Command Prompt window, execute: devenv /resetskippkgs
SQL Server 2008 Express might fail to install when you are installing Visual Studio 2010 Beta 1 on a computer that is running Windows XP Service Pack 2 or Windows Server 2003. This could occur when there is a language conflict between SQL Server 2008 Express and Microsoft XML Core Services (MSXML) 6.0 Service Pack 2. For example: If a user is using a German version of Microsoft XML Core Services (MSXML) 6.0 Service Pack 2, installing the English version of SQL Server 2008 Express will fail.
To resolve this issue:
To work around this issue, before you install Visual Studio 2010 Beta 1, install SQL Server 2008 Express Service Pack 1. You can download Microsoft SQL Server 2008 Express Service Pack 1 from the Microsoft Download Center. For more information, see FIX: SQL Server 2008 Setup fails if you installed the security update package 954459 for MSXML Core Services 6.0. This issue will be corrected in subsequent release of Visual Studio 2010.
If Visual Studio becomes unstable, you can put it back into a known state by repairing it.
To resolve this issue:
To repair Visual Studio:
1. In the program installation section of the Windows Control Panel, look for your version of Visual Studio (e.g., "Microsoft Visual Studio Team System 2010 Team Suite Beta 1 - ENU"). Double-click it to bring up Visual Studio Maintenance Mode.
2. In the Welcome dialog box, click "Next".
3. Click "Repair/Reinstall".
4. You will then see a progress box that shows the progress for every component that is installed, followed by a completion screen that indicates success or failure
After you have installed Visual Studio, if you want to add components that were not installed by default, follow these steps to add them.
To resolve this issue:
To add or remove Visual Studio features:
1. In the program installation section of the Windows Control Panel, look for your version of Visual Studio (e.g., "Microsoft Visual Studio Team System 2010 Team Suite Beta 1 - ENU"). Double click it to bring up Visual Studio Maintenance Mode.
2. In the Welcome dialog box, click "Next".
3. Click "Add or Remove Features".
4. This will bring up a tree that displays all of the possible features. You can either install or uninstall.
a. Selecting a feature will install it.
b. Clearing a feature will uninstall it.
c. If you have previously uninstalled a product that Visual Studio relies on and you do not see it, then clear the feature that depends on that product and then select it again. Visual Studio will try to reinstall that product.
5. When you are satisfied with the selections, click "Update" to start the update process.
6. You will then see a progress boxthat shows the progress for every component that is installed, followed by a completion screen that indicates success or failure.
If you installed Visual Studio Team System 2010 by using a Web download of the product and want to uninstall it, you must first uninstall Microsoft Team Foundation Server 2010 Beta 1 Object Model.
To resolve this issue:
In the program installation section of the Windows Control Panel, uninstall Microsoft Team Foundation Server 2010 Beta1 Object Model. When this program is uninstalled, uninstall Visual Studio Team System 2010.
We recommend that you install Visual Studio 2010 on a computer that does not have other pre-release versions of Visual Studio (Community Tech Preview, Beta, RC) or supporting components.
To resolve this issue:
All pre-release versions of Visual Studio must be removed in the correct order BEFORE the official release version is installed. We recommend that you uninstall the main product first (Microsoft Visual Studio 2010 Beta), which will remove majority of Beta components, and then remove other supporting products that may have been installed with it.
1. On the Start menu, click Run .
2. Type control appwiz.cpl, and click OK.
3. Remove all instances of Visual Studio 2010 products (e.g., Microsoft Visual Studio 2010 Team Suite).
4. Remove remaining supporting products that may be present on your computer, in the specified order. Ignore items that are not present on your computer. You can postpone rebooting until all .NET Framework components have been removed.
5. Restart the computer, if prompted during any of the uninstall steps above.
User-generated assets, such as project files and custom settings will not be removed or affected when Visual Studio 2010 is uninstalled.
Optional SxS Products
You can remove the following supporting products that are installed with Visual Studio 2010. Note: These components may also be used by other Visual Studio versions on the computer. Do NOT remove these components if you have Visual Studio 2008 installed.
Important System Updates
Visual Studio 2010 also installs the following important updates, which we recommend that you keep on your system:
Most pre-release projects can be carried forward to the release version. If you have problems, report your specific issue on the Visual Studio Express Forum, or the Visual Studio Forums.
There are no known issues.
If a user has more than one Custom Build Rule in a Visual C++ project in Visual Studio 2008 and has not changed the build order (by using the Tool Build Order UI), after conversion to Visual Studio 2010, the relative order of execution during build may change.
To resolve this issue:
This is By Design for MSBuild. In case the CBRs actually have dependencies between them, the user must specifically call them out by configuring the BeforeTargets and AfterTargets properties for every CBR.
Scenario
1) User has a Visual Studio 2008 Visual C++ project that contains two custom build rules, for example, CBR1 and CBR2 with default order.
2) When user builds by using Visual Studio 2008, CBR1 executes first and CBR2 executes next.
3) User upgrades the Visual C++ project to Visual Studio 2010.
4) Now user builds by using Visual Studio 2010, but CBR2 builds before CBR1.
Workround
1) Open the converted .vcxproj project file in the text editor.
2) Find the item group for the custom build rule.
3) Open the converted project in the IDE.
4) Right-click the file that has the file name extension that is associated with CBR2.
5) On the property page, set "Execute After" to "CBR1". This ensures that the custom build rule CBR2 runs after CBR1.
In Visual Studio 2008, Visual C++ projects $(IntDir) and $(OutDir) macros do not have a trailing slash. In Visual Studio 2010 they do. Visual C++ project conversion takes care of expressions such as $(IntDir)\, $(IntDir)\subdir, or $(OutDir)/subdir, and transforms them to $(IntDir), $(IntDir)subdir, and $(OutDir)subdir appropriately. However, if a Visual Studio 2008 Visual C++ project property contains only $(IntDir) without a slash next, it will end up the same in the converted project. Therefore, expressions such as "$(IntDir)1" are evaluated to "Debug1" in Visual Studio 2008 and to "Debug\1" in Visual Studio 2010.
To resolve this issue:
If you have to have $(IntDir) value without the trailing slash, the occurrence of $(IntDir) can be replaced by using expression $([System.IO.Path]::GetDirectoryName('$(IntDir)'))
For example, if in Visual Studio 2008, the Build Event Command Line property of a Visual C++ project contains the command "echo $(IntDir)", you can achieve the same output in Visual Studio 2010 by replacing the command with "echo $([System.IO.Path]::GetDirectoryName('$(IntDir)'))".
Visual C++ projects get retargeted to the .NET Framework 4 when you upgrade to Visual Studio 2010. Visual C# and Visual Basic projects do not. A solution that has references between these project types may not build after upgrade because a project that targets a given Framework version cannot depend on a project that targets a later version. To solve this problem, Visual C++ projects must be manually retargeted to a compatible Framework version.
To resolve this issue:
There are several ways to work around this problem:
A) Moving Visual C#/Visual Basic projects to target the .NET Framework 4 common language runtime (CLR).
1) Right-click the Visual C# project, and click "Properties".
2) On the "Application" tab, select "Target Framework" = ".NET Framework 4".
B) Moving all Visual C++ projects to target the .NET Framework 4 CLR (option 1 - this applies to a Visual Studio instance only)
1) Open the Visual Studio Command Window.
2) Type
set TargetFrameworkVersion=v3.5
3) At the command prompt, type devenv.exe.
For that instance of Visual Studio, all Visual C++ projects will target CLR 3.5. (You can target other Framework versions by changing v3.5 to v2.0 or v3.0.)
C) Moving all Visual C++ projects to target .NET Framework 4 CLR (option 2 - this applies to all Visual Studio instances of the current user)
1) Right-click "Start", then click "Computer" and then "Properties". In the properties window, click "Advanced System Settings".
2) On the "Advanced" tab, click "Environment Variables".
3) Under "User variables for user <username>", click "New" and then type
Variable Name = TargetFrameworkVersion
Variable Value = v3.5
4) Start a new instance of devenv.
For all future instances of Visual Studio, all Visual C++ projects will target CLR 3.5 (You can target other Framework versions by changing v3.5 to v2.0 or v3.0.)
D) Moving individual Visual C++ projects to target .NET Framework 4 CLR
1) In Solution Explorer, right-click a Visual C++ project, and then click "Unload Project".
2) After the project is unloaded, right-click the project and then click "Edit".
3) In the editor, search for the property group labeled "Globals".
PropertyGroup Label="Globals"
4) If a <TargetFrameworkVersion> property already exists, change its value to v3.5. If it does not exist, create the following property in the Globals property group:
<TargetFrameworkVersion>v3.5</TargetFrameworkVersion>
5) Save and reload the project.
Note:
Workarounds B), C), and D) instruct you to target one or more Visual C++ projects to the .NET Framework 3.5. For these projects to successfully build, Visual Studio 2008 must be installed on the computer.
For Visual Studio 2010 Beta 1, only online help is supported. You must have an Internet connection to view product documentation when you use the Help menu or F1.
To resolve this issue:
There's no workaround available.
When you add large files to a Setup project, the "Not enough storage is available to complete this operation" error message appears when you try to build the Setup project, even if the local hard disk has available disk space. Virtual memory usage may also increase during the build process.
To resolve this issue:
Add RAM to the build computer, or try this workaround:
The Resource Editor is not included in Visual Studio 2010 Shell (Integrated) Beta 1. You cannot use the Resource Editor to view or modify images, icons, cursors or (native) .rc resource files.
To resolve this issue:
There's no workaround available.
Due to a Visual C++ code model change in Visual Studio 2010 Beta 1, if two types have same name but are in different namespaces and if the type is referenced without being fully qualified by using the namespace, then the Class Designer cannot distinguish between them and the wrong shape might be displayed in the Class Designer.
For example, given this code:
namespace ns1{
class B{};
}
namespace ns2{
class B{};
class D : B {};
}
Class D is derived from ns2::B. However, the namespace is not fully qualified, so in the class diagram, if you want to display the base class of class D, the Class Designer will fetch the first class B in the code; that is, ns1::B.
To resolve this issue:
To work around this issue, fully qualify the type reference by using the namespace. Class Diagram will refresh automatically when the code is updated.
In the example shown, you should write:
class D : ns2::B {};
Install the .NET Framework 3.5 SP1 and Visual Studio 2010 Beta 1.
Create a console application that targets the .NET Framework 3.5 client.
Expected: The App.config file is created and appears in Solution Explorer, the file contains the <supportedRuntime> tag and the attribute Sku is set to "Client".
Current: No App.config file is created.
Impact: Visual Basic/Visual C#/Visual C++ CLI projects, where the target computer only has the .NET Framework 3.5 client installed and the application target is the Framework 3.5 client. This is not an issue if the target computer has the full Framework version 3.5 and the application target is the Framework 3.5 client.
Background: When a project that targets the Framework 3.5 client is created, the expected behavior is to create an App.config file that provides information to the CLR at run time, for example, application setting, assembly locations, etc. In this case, the file is not being created and the application fails to load.
To resolve this issue:
There's no workaround available.
Filters displayed in Solution Explorer after a solution or project is checked out from source code control are missing or incorrect.
Impact: Visual C++ and Visual C++ CLI projects.
Background: In Visual Studio 2010, information about filters is stored in a .filters file, which is adjacent to each .vcxproj project file in the file system. Checking out a .vcxproj file from source code control should automatically checks out the filters file, too. However, this feature is not currently implemented in Visual Studio 2010 Beta 1.
To resolve this issue:
To restore the correct filters: After you check out a .vcxproj file, browse to the .filters file on the Source Code Control server and manually check it out before you open your project in Visual Studio 2010 Beta 1.
After you add a generic object data source to the project, the data schema is displayed in a tree view in the Data Sources window. Later, if you modify your object by adding or removing some properties, you may find that the data schema in the Data Sources window is not correctly updated. This is because obsolete runtime types were not removed by AssemblyObsolete event.
To resolve this issue:
Reopen the project, or reload it by right-clicking the project node, clicking Unload Project, and then clickin Reload Project.
In a Visual Basic project, if user opens Class Designer and draws an inheritance line from class to interface, the operation fails and the error message, "Change has been aborted because it would prevent file ... from parsing. Please correct the error and try again", is displayed.
To resolve this issue:
In the code editor, manually write code to implement the interface.
There is a known issue when a Visual C++ Profile Guided Optimization (PGO) build is attempted by using either the X64 cross compiler or the Itanium Processor Family (IPF, also known as ia64) cross compiler. An error occurs and the message says that this SKU does not support PGO: "Profile Guided Optimization is not available in this edition of the product." If the installed SKU has support for PGO, i.e., an x86 build succeeds by using PGO, a work-around can be applied to enable cross compiler support of PGO.
This issue will be addressed in a later release.
To resolve this issue:
Copy the file in the Visual Studio installation directory, \vc\bin\pgodb100.dll, and paste it in \vc\bin\x86_amd64\ to enable X64 cross compiler PGO builds, or \vc\bin\x86_ia64\ to enable IPF cross compiler PGO builds.
Notice that a separate directory \vc\bin\amd64 is the location for the X64 native hosted tools and contains a native hosted pgodb100.dll. Do not copy or overwrite this file.
There is limited support for customization of menus and toolbars in Visual Studio 2010 Beta 1. The Customize command on the Tools menu and "Add or Remove Buttons" drop-down menu on the toolbar are not available. Customization through DTE (Design Time Extensibility) also has limitations.
To resolve this issue:
1. Menu and toolbar customizations can be exported from Visual Studio 2008 and then imported into Visual Studio 2010 by using Import and Export Settings on the Tools menu. Note: There is a known issue with vertically docked toolbars. These toolbars may display a very large icon. To work around this, refer to the following steps for moving a toolbar.
2. Some customization of Visual Studio 2010 menu and toolbars is available through DTE (Design Time Extensibility). There are known issues with adding a new or existing command to a new or existing toolbar, and those we do not recommend those customizations for Beta 1. The following DTE customizations are available for Beta 1: moving a toolbar, resetting a toolbar, deleting a toolbar, hiding/showing a toolbar, adding a new group to a toolbar, and deleting an item from a toolbar.
To customize Visual Studio 2010 by using the DTE:
1. On the Tools menu, click Macros and then click Macros IDE.
2. Click Project and then click Add Module.
3. Name the new module "Customize".
4. Add the following import to the Customize file: Microsoft.VisualStudio.CommandBars.
5. Create a Macro for the customization. Examples and known issues can be found at http://go.microsoft.com/fwlink/?LinkId=151504.
6. Save the Macro project.
7. Return to the Visual Studio IDE.
8. On the Tools menu, click Macros and then click Macro Explorer.
9. Expand the Samples node and the Customize module.
10. Double-click the macro you want to run.
On a 32-bit computer, building a Visual C# or Visual Basic project that targets a 64-bit platform will not work when it has a non-Framework assembly reference (even those that are registered in assemblyfolderex) that is targeting either x86 or x64.
Building the project results in an error (Exception from RAR)
Sample Repro:
1) Create a Visual C# console application.
2) Open Configuration manager and add a 64-bit platform.
3) Make that the active platform.
4) Add a reference. (Example: EnvDte100)
Results:
You will receive a build warning that the "ResolveAssemblyReference" task failed unexpectedly.
Building the project will result in an error with similar error message that you saw in the previous warning.
To resolve this issue:
There's no workaround available.
When you browse the "Online Template" category of the New Project dialog box, changing the .NET Framework targetdoes not filter the templates in the template list. However, you can still use the .NET Framework target drop-down to select the .NET Framework version you want the project to target. If the Framework version is not valid for the selected template, project creation will ignore the .NET Framework target drop-down selection and rely on the template to specify the target Framework version.
To resolve this issue:
There is no workaround to enable filtering.
1. Create a Visual C++ project.
2. On the View menu, click Property Manager.
3. Right-click either the "Debug" folder or the "Release" folder, and then click "Add New Project Property Sheet".
4. Notice that the path in the "Location" field is the Microsoft Visual Studio 2010 default project directory and not the created Visual C++ project directory.
5. Create a property sheet under <projectdirectory>\mypropsheets\P1.props.
6. In Windows Explorer, create a copy of p1.props in the same folder and rename it P2.props.
7. Right-click P1.props, click "Add an exisiting property sheet", and then click P2.props.
8. You will get an error message that property sheet cannot be added because of circular reference.
9. Reloading the project will fail.
To resolve this issue:
1. You can append the Visual C++ project directory to the path, or use the "Browse" button to locate the project directory. For Beta 1, create the property sheets under the project directory directly.
-or-
2. You can use Solution Explorer to add new project property sheets.
Steps for Solution Explorer workaround:
1. After the project is created, right-click it project in Solution Explorer and then click "Add New Item".
2. Select "Property Sheet (.props)" from the template list and name it P1.props.
3. Repeat steps 1 and 2 to create P2.props.
3. After the property sheets have been added to the project, on the View menu, click Property Manager.
4. In the Property Manager tool window, right-click either the "Debug" or "Release" folder and then click "Add Existing Property Sheet".
5. Locate and select the property sheet, P1.props.
6. Right-click P1.props, and then click "Add Existing Property Sheet" and add P2.props.
When users upgrade to Visual C++ 2010 from earlier versions of Visual C++, they might see some of the known issues in the Beta 1 release. Here are workarounds for all the known issues.
To resolve this issue:
1) Upgrading a project that is checked in as part of source code control does not check in newly created files.
Symptom: After conversion, a newly created project file, property sheet, or filters file will not be added to source control automatically.
Workaround: Add .vcxproj files, .vcxproj.filters files, and .props files to source control after they are converted.
2) Project that has Unicode name fails to upgrade.
Symptom: Project upgrade fails if the project name contains Unicode characters.
Workaround: Rename the project to contain ASCII characters.
3) Upgrade fails because a rule in a .rules file has a Unicode name.
Symptom: Project upgrade fails if the rule name in the .rules file cotains Unicode characters.
Workaround Rename the rule to contain ASCII characters.
4) Upgrade fails if you have custom delimiters other than ';' in your custom build rules.
Symptom: Project upgrade fails.
Workaround: In custom build rules (.rules file), if you have stringproperties that have custom delimiters other than ';' then after conversion the delimiters are not persisted. Modify the .rules file to use ';' as delimiters for string lists.
5) After conversion, custom build rules are not batching correctly on the command line.
Symptom: Files associated with the custom build rule are not batched properly on the command line when the custom build rule is executed.
Workaround
Batching in custom build rules might not work in the context of custom build rules after conversion. If you want to support batching, find the following line in <RuleName>.targets file:
<Target
Name="_BatchingRule"
BeforeTargets="$(BatchingRuleBeforeTargets)"
AfterTargets="$(BatchingRuleAfterTargets)"
Condition="'@(BatchingRule)' != ''"
Outputs="%(BatchingRule.Outputs)"
&nbs Inputs="%(BatchingRule.Identity);%(BatchingRule.AdditionalDependencies)">
Change it to:
<Target Name="_BatchingRule"
BeforeTargets="$(BatchingRuleBeforeTargets)"
AfterTargets="$(BatchingRuleAfterTargets)"
Condition="'@(BatchingRule)' != ''"
Outputs="%(BatchingRule.Outputs)"
&nbs Inputs="@(BatchingRule.Identity);@(BatchingRule.AdditionalDependencies)">
6) Upgrading property sheet fails if the preprocessor definition in the compiler has quotes in it.
Workaround:
- In Solution Explorer, right-click the project, click Properties, click C/C++, and then click Preprocessor.
- If the compiler preprocessor definition has quotes, then delete them. MSBuild automatically adds quotes for properties.
7) Libraries not linked and missing on the linker command line.
Symptom: Compile-time errors are thrown because the library that your project depends on is not correctly linked.
Workaround:
- In Solution Explorer, right-click the project, click Properties, click Linker, and then click Input.
- If libraries are missing on the command line for linker or librarian tools, use the AdditionalDependencies property for the tools to list the dependent libraries to be linked.
8) Upgrade fails because filters that have duplicate names are part of the project.
Symptom: Upgrade fails and a message that indicates that there are duplicate filters in the project file is displayed.
Workaround: Filters that have duplicate names in the same project are not supported in Beta 1. Before you convert, make sure that filters have unique names in the existing project file.
9) Upgrade fails if the project has configuration-dependent un-evaluated macros that define paths or other variables, for example, if you use $(IntDir)filename.txt to define the path of a file based on the configuration.
Workaround: If your project uses unevaluated macros for file-level properties that adopt a different value depending on the configuration in which the project is building, the upgrade will fail. Do not use macros that adopt a different value based on configuration for file-level settings.
10) Upgrade causes paths of some files that are imported in the project file to change.
Workaround: After conversion, all paths in the project file are made relative to the project file. If this is not what you want, review the converted project file to modify the affected paths.
11) Adding context-sensitive Help to an MFC project during project creation causes the creation to fail.
Workaround: Do not add context-sensitive Help to MFC projects in Beta 1.
12) The upgrade wizard is fully active and Finish button is enabled, but it appears that nothing is happening.
Workaround: The overwrite dialog box for conversion is not modal. Therefore, it might be hidden. Do not click Finish if you already clicked it once because it might restart the conversion.
13) Command-line Upgrade (vcupgrade.exe) crashes when command-line options are not specified correctly.
Workaround: Do not use invalid switches when you call vcupgrade.exe. For correct usage, type vcupgrade /?.
14) Project upgrade fails and shows this XML parsing error: (System error: -2146233088).
Symptom: If you are upgrading a project that was already upgraded from an earlier version of Visual Studio, the project might import "UpgradeFromVCX" files from $(VCInstallDir)VCProjectDefaults\UpgradeFromVC**.vsprops. If so, conversion fails and show this message: The following error has occurred during XML parsing:
File: D:\Program Files\Microsoft Visual Studio 10.0\VC\VCProjectDefaults\UpgradeFromVC60.vsprops
Line: 5
Column: 28
Error Message:
System error: -2146233088.
The file 'D:\Program Files\Microsoft Visual Studio 10.0\VC\VCProjectDefaults\UpgradeFromVC60.vsprops' has failed to load.
The project file could not be loaded. Could not find file 'D:\Program Files\Microsoft Visual Studio 10.0\VC\VCProjectDefaults\UpgradeFromVC60.props'. D:\Program Files\Microsoft Visual Studio 10.0\VC\VCProjectDefaults\UpgradeFromVC60.props
Workaround:
In the .vcxproj file, change the path from "$(VCInstallDir)VCProjectDefaults\UpgradeFromVC**.props" to "$(VCTargetsPath)\Microsoft.Cpp\Microsoft.Cpp.UpgradeFromVC**.props".
15) Build fails because the command line for tools is malformed. AdditionalOptions is missing space between values.
Workaround: After conversion for different tools, additional options might not be converted properly. This can cause build failures. For example, after conversion you may see <AdditionalOptions>/W4567%(AdditionalOptions)</AdditionalOptions>. This causes a build failure because there is no space between /W4567 and %(AdditionalOptions). In the .vcxproj file, add a space.
16) Property sheet changes are overwritten after the project is reconverted, even when the user selects not to overwrite the project.
Workaround: Conversion always overwrites the .props file, even if the user selects not to overwrite. If you have modified the already converted .vsprops->.props file, save it to another location before you start conversion. Otherwise, the changes will be lost in conversion.
Some UI elements may be displayed incorrectly when Visual Studio 2010 is run on a VMWare virtual machine that has accelerated display device support enabled. Users may also notice poor performance of Visual Studio with graphics acceleration. By default, this feature is off for VMWare virtual machines. Therefore, users who do not enable graphics acceleration should not be affected.
To resolve this issue:
Users who run Visual Studio 2010 on a virtual machine should turn off the VMWare graphics acceleration option. The WPF and Visual Studio teams are working with VMWare to improve the graphics rendering and performance of this driver before the release of Visual Studio 2010.
There is a known issue when the standalone SQL Server Management Studio is installed alongside Visual Studio 2010 Beta 1. Starting SQL Server Management Studio and trying to connect to any server causes SQL Server Management Studio to hang.
To resolve this issue:
Use SQL Server Management Studio from a SQL Server release.
User will experience a hang when the new "Navigate To" dialog box is invoked while "Show All Files" in Solution Explorer is enabled.
To resolve this issue:
Disable "Show All Files" when you plan to use "Navigate To" or do not use "Navigate To" when "Show All Files" is enabled.
Note: "Show All Files" is on by default for all projects that are created by using "Create project from existing source".
Text may appear slightly blurry. This can occur with any font, although different users may see different fonts as more or less blurred. MSGothic, the default font for Japanese system locales, is known to be more blurred than other fonts.
To resolve this issue:
We recommend that you keep the default fonts for Visual Studio, for example, Consolas for English SKUs of Visual Studio 2010. There is no alternative that is consistently sharper than MSGothic for Japanese characters, although some users find Meiryo more readable.
TrueType fonts are the least blurred of the non-default fonts. These fonts appear in bold in the font list on the Fonts and Colors page of the Options dialog box (Tools menu, Options, Environment, Fonts and Colors). The WPF and Visual Studio teams are working to improve font rendering in the text editor before the release of Visual Studio 2010.
The text editor performs poorly over Remote Desktop connections for many tasks, for example, typing and scrolling.
To resolve this issue:
Run Visual Studio 2010 on a local computer or a virtual machine, and not over a Remote Desktop connection. The Visual Studio team is working to improve Remote Desktop performance before the release of Visual Studio 2010.
If a project that targets the .NET Framework 4 contains a project reference to project that targets an earlier version of the Framework (2.0, 3.0, or 3.5), IntelliSense will not be updated between the two projects unless a build is performed. In addition, the rename refactoring and go-to-definition features will not work across the two projects because a different compiler host is used for a project that targets the .NET Framework 4 and a project that targets Framework version 2.0, 3.0, or 3.5, and symbols cannot be shared across the two compiler hosts.
To resolve this issue:
If your project does not require targeting an earlier version of the .NET Framework, you can work around this issue by targeting the .NET Framework 4 instead.
For Visual Basic projects:
1. In Solution Explorer, right-click the project, and then click Properties.
2. On the Compile tab, click Advanced Compile Options.
3. Select .NET Framework 4 on the Target Framework drop-down list.
For Visual C# projects:
1. In Solution Explorer, right-click the project, and then click Properties.
2. On the Application tab, select .NET Framework 4 on the Target Framework drop-down list.
Because the settings on the Tools -> Options -> Projects and Solutions -> VB Defaults options page are not correctly propagated, the values for Option Infer, Option Strict, Option Explicit and Option Compare may be incorrectly displayed on the Compile tab of the project properties for newly created projects. The values from the VB Defaults options page are correctly set for new projects, but they are incorrectly displayed in the UI.
To resolve this issue:
1. Save the newly-created project.
2. Close the project.
3. Reopen the project.
The new "Navigate To" feature uses a global keyboard shortcut (CTRL+,). This shortcut conflicts with the new IME on CHT.
The shortcut default architecture did not anticipate a case like this. Therefore, the default shortcut cannot be changed.
However, users can customize the shortcut themselves.
To resolve this issue:
Users can customize the shortcut themselves, as follows.
1. On the Tools menu, click Options. Expand Environment and then click Keyboard.
2. In the Press shortcut keys box, type the shortcut you want use for the command. Click OK.
When one hovers over a C++ squiggle, the tooltip is sometimes truncated and, therefore, the error text is incomplete.
To resolve this issue:
There is no workaround for the truncated squiggle tooltip in this release.
Alternative: Open the Error List Window (View->Other Windows->Error List Window) to see the same errors on the Errors tab.
Tasklist does not list C/C++ comments or user tasks.
To resolve this issue:
There is no workaround in this release.
Setting a custom background color for the Editor works once, but every new editor window will open with a white background.
To resolve this issue:
You can re-apply background color settings by opening Tools -> Options -> Environment -> Fonts and Colors and just clicking OK. There is also a patch written by a member of the Visual Studio editor development that enables custom background colors to persist. To obtain it, in Visual Studio, open Tools -> Extension Manager and search for the "BackgroundPatchExtension", or go to http://go.microsoft.com/fwlink/?LinkID=155936 and download it. After it is installed and enabled in Extension Manager, the BackgroundPatchExtension will enable the Visual Studio editor to correctly respect background color settings.
Note: This bug has been fixed for the next release of Visual Studio 2010.
When you use the mouse wheel to scroll, the text editor may scroll very slowly or sometimes not at all. Other applications scroll as expected.
To resolve this issue:
To force the mouse wheel to scroll the editor at a more reasonable pace, increase the number of lines to scroll when the wheel is turned. This setting can be found on the Wheel tab of Mouse Properties in the Control Panel. However, doing this may cause other applications to scroll faster than expected. The Visual Studio editor can also be scrolled at a reasonable pace by clicking its scroll bars or by pressing the UP ARROW or DOWN ARROW key.
Note: This bug has been fixed for the next release of Visual Studio 2010.
When you try to scroll the text editor by using a laptop touchpad, nothing happens.
To resolve this issue:
There is no workaround to fix the touchpad problem in this release.
Alternatives: The editor can be scrolled by clicking its scroll bars, by using the scroll wheel on an external mouse, or by pressing the UP ARROW or DOWN ARROW key.
Visual Studio 2010 introduces a new compiler option for referencing assemblies and COM components, "/l", which will embed interoperability types from referenced assemblies. This enables applications that interoperate with COM components to be deployed without Interop Assemblies (often referred to as Primary Interop Assemblies, or PIAs for short).
In a complex solution structure in which one component or project references a PIA by using /r, thereby introducing a dependency on the Interop Assembly, and another component or project in the same solution that references the same COM component PIA by using /l, the compiler will issue the warning, "A reference was created to interop assembly, 'xx' because of an indirect reference created by assembly, 'xx'. Consider linking assembly "xx."
To resolve this issue:
1) In the references section of Solution Explorer, right-click the assembly and then click "Properties".
3) Change "Embed Interop Types" to False.
4) Rebuild.
Or on the command line, for the offending reference, change the switch to /r instead of /l.
Visual Studio 2010 introduces a new compiler option for referencing assemblies and COM components, "/l", which will embed interoperability types from referenced assemblies. This enables applications that interoperate with COM components to be deployed without Interop Assemblies (often referred to as Primary Interop Assemblies, or PIAs for short).
If classes from the Interop Assemblies are explicitly used, the compiler will issue an error, "CoClass 'xx' can be used only as one of its applicable interfaces."
To resolve this issue:
Refactor the code to use interfaces instead of classes. For example, instead of the following code:
Microsoft.Office.Interop.Excel.Application excelApplication = new Microsoft.Office.Interop.Excel.ApplicationClass();
use this equivalent code, which creates an instance of an interface:
Microsoft.Office.interop.Excel.Application excelApplication = new Microsoft.Office.interop.Excel.Application();
Visual C# and Visual Basic projects default to target platform "x86" in Visual Studio 2010, but F# projects target "AnyCPU". An issue in the F# project system prevents solutions from containing projects that target different platforms.
To resolve this issue:
Workaround 1 - Use assembly references instead of project references.
i. For any Visual C#/Visual Basic projects that are referenced by an F# project, remove the project reference from the F# project.
ii. Add to the F# project assembly references to the output of the Visual C#/Visual Basic projects.
Workaround 2 - Use the Configuration Manager to set the Visual C#/Visual Basic projects to target AnyCPU.
i. Open Configuration Manager
ii. For any Visual C#/Visual Basic projects that are referenced by an F# project, on the "Platform" drop-down list, select "<New>".
iii. In the New Project Platform dialog box, accept the default "Any CPU" for the New Platform, but clear "Create new solution platform".
iv. Click OK, and then Close.
v. Build should now successfully build AnyCPU binaries.
Workaround 3 - Manually modify the Visual C# or Visual Basic project file to target AnyCPU.
i. For any Visual C#/Visual Basic project that is referenced by an F# project, unload the project and then edit its project file (.csproj or .vbproj).
ii. Replace all occurrences of "x86" by using "AnyCPU".
iii. Reload the project.
iv. Build now successfully builds AnyCPU binaries.
The first build of a solution that contains both F# and managed Visual C++ projects will hang, but Visual Studio will remain responsive.
To resolve this issue:
Just cancel the build, and then subsequent builds should succeed.
IntelliSense does not always work when macros that have the form %(<macro name>), most often seen as %(AdditionalOptions), are referenced in Additional Options for tools.
To resolve this issue:
You can try to delete %(<macro name>) from the command line if doing so does not affect your build process and is otherwise acceptable. The problem happens after you have converted existing Visual Studio 2008 projects to the Visual Studio 2010 format. If you had additional options set for a particular tool, then the upgraded version in the project files resembles this: <AdditionalOptions>/yourvalue %(AdditionalOptions)</AdditionalOptions> where %(AdditionalOptions) signifies inheritance (project inheriting from property sheets or file inheriting from project). If you are not using inheritance in your build process, then you can try removing %(AdditionalOptions). However, doing this might cause other things to fail.
On a computer that has both Visual Studio 2008 and Visual Studio 2010 installed side-by-side, Visual Studio 2008 cannot create Word 2007 or Excel 2007 document projects by customizing an existing document. Project creation fails with the error "The document is not customized."
To resolve this issue:
Use the following workaround to create a document project in Visual Studio 2008 from an existing document.
Uninstalling Visual Studio 2010 on a computer that also has Visual Studio 2008 may cause build errors. Building an Office application-level project or document-level project in Visual Studio 2008 may fail with the following build error: "An error occurred while attempting to persist the data. The message returned is: Could not create a persistence object for the specified file."
To resolve this issue:
To successfully build Office projects in Visual Studio 2008 again, you must repair the Visual Studio Tools for Office system 3.0 Runtime.
o In the program installation section of the Windows Control Panel, select Visual Studio Tools for Office system 3.0 Runtime and then click Uninstall/Change.
o Select Repair.
After you add a Windows Forms control to an Office designer, Visual Studio may show an "Invalid Pointer" error while the Office project is being debugged.
To resolve this issue:
To debug Office document-level projects, disable historical debugging.
1) On the Tools menu, click Options.
2) Click the Historical Debugging node.
3) Clear Enable Historical Debugging.
SharePoint 2007 Workflow projects can be created or run only on computers that have 32-bit operating systems. Currently, 64-bit operating systems are not supported.
To resolve this issue:
Install Visual Studio 2010 Beta 1 on a computer that has a 32-bit operating system that also has either Windows SharePoint Services (WSS) 3.0 or Microsoft Office SharePoint Server (MOSS) 2007 installed.
If you try to add the assembly for the Ajax Control Toolkit (1.0 or later) to the Visual Studio Toolbox by using the Choose Toolbox Items dialog box, Visual Studio 2010 Beta 1 throws a security exception. This occurs because, by default, when you download a third-party assembly such as AjaxControlToolkit.dll (as a .dll file or as extracted from a .zip file), the assembly is marked as untrusted.
To resolve this issue:
Mark the AjaxControlToolkit.dll as a trusted file for Visual Studio 2010 Beta 1, as follows:
1. In Windows Explorer, right-click the AjaxControlToolkit.dll, and then click Properties.e="MARGIN: 0in 0in 0pt">3. 3. Click Unblock to set the file as trusted. You can now add the AjaxControlToolkit to the Toolbox.
If you upgrade or retarget an ASP.NET Web application project (WAP) from .NET Framework 2.0 to .NET Framework 4, not all dependent references are added to Solution Explorer when the target runtime is changed. References such as System.Core, System.Data.DataSetExtensions, System.Web.Extensions, System.Web.Extensions.Design, and System.Xml.Linq may not be correctly added.
To resolve this issue:
Manually add these references in Solution Explorer.
When you type in a Visual Basic code nugget or script block on an ASPX, ASCX, or Master page, you will notice that the code is not automatically pretty formatted when you leave the line. Because of a bug, this aspect of the feature has been disabled for Beta 1.
To resolve this issue:
Use the formatting command to manually re-format the code after you type it.
If you retarget an ASP.NET Web project to use .NET Client Profiles, the project might not build and run correctly because .NET Client Profiles are not supported as a runtime target for any type of ASP.NET Web project. Core assemblies such as System.Web are required for Web projects, but are removed when you use .NET Client Profiles.
To resolve this issue:
To determine the target for a Web application project in Visual C#:
1. In Solution Explorer, double-click Properties.n the Pro2. On the Properties page, click the Application tab. The Target Framework field indicates the targeted runtime.
To determine the target for a Web application project in Visual Basic:
1. In Solution Explorer, double-click My Project.
2. On the Properties page, on the Compile tab, click Advanced Compile Options. The Target framework (all configurations) field indicates the targeted runtime.etermine the target for a Web site:
1. In Solution Explorer, right-click the project name and then click Property Pages.
2. In the Pro2. In the Property Pages dialog box, click the Compile tab. The Target Framework field indicates the targeted runtime.
If a Web project does not have a Web.config file and you use the Web Administration Tool in Visual Studio to administer the application, the application will throw an exception when you subsequently try to run or further administer the application. The exception message will state: "The targetFrameworkMoniker attribute is required for this application to work in an application domain or application pool running .NET Framework 4 and above, eg '<compilation targetFrameworkMoniker=".NETFramework,Version=v4.0">'. Please update Web.config, or configure the application to run using another .NET Framework version."
To resolve this issue:
After the Web Administration Tool has created a Web.config file, manually modify, or add, the compilation section in Web.config to include the required "targetFrameworkMoniker" attribute:
<system.web>p; ... other configuration sections
<compilation targetFrameworkMoniker=".NETFramework,Version=v4.0"/>
</system.w</system.web>
Package creation for projects that have non-English characters in the project name may not deploy correctly when the Visual Studio-generated ProjectName.deploy.cmd file is used.
Cause: If the generated MsDeploy package parameters contain non-English characters, then the command-line parser may covert original characters into invalid characters, and the deployment fails.
To resolve this issue:
Rename your Web application project by using English characters.
In Visual Studio 2010 Beta 1, if you use Design view to add a custom ASP.NET control that has dependent assemblies, the dependent assemblies are not automatically added to the application \Bin\ folder.
To resolve this issue:
Add the dependent assemblies to the \Bin\ folder manually.
If you are using Visual Basic in a Web application project (WAP) that targets the .NET Framework version 2.0 or version 3.5, the build process might display the following message in the Output window:
vbc : Command line warning BC2007: unrecognized option 'langversion:9.0'; ignorede="MARGIN: 0in 0in 0pt">
You would also see a corresponding warning in the error list.
To resolve this issue:
You do not have to do anything about this error; it is benign.
When you create a function literal in a Jscript file, the space between the keyword "var" and the variable name will disappear when you close the block where the variable is created.
To resolve this issue:
Turn off automatic formatting: "Format completed block on }" on the Tools.Options.Text Editor.Jscript.Formatting page.
When you are debugging client script on an ASPX page, you may be prompted that your file was edited outside the IDE and that you should reload the file, even though the file was saved in the IDE. This occurs after you hit a breakpoint in a client script block during a debug session, and then you save the file at any point after the debug session is finished. Also, if you click Yes in the reload dialog box, your breakpoints on the page will disappear.
To resolve this issue:
On the Tools menu, click Options, click Environment, and then click Documents.
Clear "Detect when file is changed outside the environment".
Packaging a database that has triggers can generate an invalid script that prevents correct deployment. This issue can affect databases such as the AdventureWorks database. The issue is that the generated package script may contain a trigger-creation statement that precedes the object-creation statements that the trigger uses.
To resolve this issue:
Download and install the "Microsoft SQL Server 2008 Management Object" from Microsoft SQL Server 2008 Feature Pack, April 2009. Visual Studio 2010 Beta 1 uses components in SQL Server 2008 to create Web packages. Install this update regardless of the version of SQL Server you have installed.
To install the Microsoft SQL Server 2008 Feature Pack, April 2009:
1. Go to http://go.microsoft.com/fwlink/?LinkID=156060
2. In the Microsoft SQL Server 2008 Management Objects section, select the appropriate file to download, based on the kind of processor on the target computer.
Types can be shared between a Web service and a referencing project. This enables the Web service and the referencing apps to share not only the shape of the data that is exchanged between the two, but also the logic that is internal to the type. To do this:
1. Add a project reference to the assembly that contains the shared type.n the Add Service Reference dialog box, click Advanced.
3. Select Reuse Types and then click OK.
PROBLEM:
When Visual SWhen Visual Studo 2010 Beta 1 and Visual Studio 2008 SP1 are installed on the same computer, adding a Web service reference that has 'Reuse types' enabled will fail on Visual Studio 2008. Type reuse will not work even after Visual Studio 2010 Beta 1 is uninstalled.
To resolve this issue:
1. In the "Add Service Reference" dialog box, click "Advanced" to go to the "Service reference settings".
2. Turn off "Reuse types in referenced assemblies" in the "Service reference setting" dialog box, and then close the dialog box and continue adding the reference.fter the service reference is added, open the map file for the newly added service reference by clicking the "Reference.svcmap" node under the reference in Solution Explorer.
4. In the map file (which is in XML), change the "ReferenceAllAssemblies" setting from "false" to "true", and save the change.
5. In Solutio5. In Solution Explorer, right-click the "Reference.svcmap" node for the newly added reference, and then click "Update service reference".
In SvcConfigEditor, after a custom binding extension, binding element extension, behavior extension, or standard endpoint extension is added in the "Advanced->Extensions" node, the extension cannot be accessed. It does not appear when you select "Add Binding/Binding Element/Service Behavior/Standard Endpoint Element Extension" in a newly created binding, service behavior, or standard endpoint node, or it does not appear when you select Binding Element of Binding Property or Standard Endpoint Element of Kind Property in a newly created endpoint node.
To resolve this issue:
Manually add these extensions in the configuration files.
On a 64-bit operating system, in SvcConfigEditor, if you open a type browser and click "GAC" on the left side of the screen, no types are displayed. The type browser is used in several scenarios, for example, browse for the service contract when you add a new service endpoint, or browse to add new extensions of binding, binding element, service behavior, and standard endpoint element, etc.
To resolve this issue:
There's no workaround available.
If you want to add a service reference to a .NET Framework 4 workflow project, the services in the same solution cannot contain duplicate operation names even if they are in different namespaces, for example, when you create one WCF service project and one version 4 Declarative WF service project in the same solution and both services have the same operation name. The problem occurs when you try to add a service reference from the WCF service to the WF one and then build the solution. The build fails with the following message: "The item "obj\Debug\GetData.g.cs" was specified more than once in the "Sources" parameter. Duplicate items are not supported by the "Sources" parameter."
To resolve this issue:
Do not use duplicate operation names.
In a WF project, after a service reference to a WCF service that contains one-way operations is added, there is an execution excepton that is caused by compile errors in the generated activities that correspond to one-way operations. The error is in the InArgument expression "New OperationName() With { .value = value }".
To resolve this issue:
Open the generated activities that correspond to one-way operations, which will be shown in ServiceReferences/ServiceReferenceName/Reference.svcmap by clicking "Show All files" in Solution Explorer. Change the InArgument expression to "New ServiceReferenceName.OperationName() With { .value = value }".
When the following scenario occurs, some variables in code-behind will be generated in duplicate.
1. Drag and drop a data type from Data Source Window to WPF designer, such as OrderID in Order table.
(This data type is the only one from some container object that customers drag and drop, that is, no other data type under Order nor Order has been dragged into WPF designer.)
2. Undo the operation in WPF designer.
3. Drag and drop a data type that is from the same container object (for example, CustomerID in Order).
To resolve this issue:
Instead of using Undo, delete the control directly from WPF designer.
If you use Undo, delete the relevant generated code in code-behind after the Undo.
At times, the designer may show an exception state.
To resolve this issue:
Close the document after any designer exception is encountered, and then reopen it.
The Silverlight designer supports Silverlight 3 to the same level as it supports Silverlight 2. Therefore, you can use the designer to build Silverlight 3 applications, but you can only use Silverlight 2-level features.
To resolve this issue:
If you want to use Silverlight 3 features such as external resource dictionaries, use the XAML editor instead of the designer.
In Silverlight projects, the toolbox is empty
To resolve this issue:
If the toolbox is empty or does not show the correct controls, try the following workarounds. Each of these options may solve this problem. If one does not work, try the others:
Option #1: Right-click the toolbox and then click Reset Toolbox.
Option #2: Right-click the toolbox and then click Choose Items to manually add controls.
Option #3: Close Visual Studio, delete the hidden *.tbd files in C:\Users\<user>\AppData\Local\Microsoft\VisualStudio\10.0\, and then restart Visual Studio.
Design-time support for the TabControl and Expander controls is unreliable in WPF, and unavailable for Silverlight projects.
To resolve this issue:
Use XAML editing to work with these controls.
Referencing a resource dictionary that is embedded in an external assembly (by using the Source="pack://application" syntax) is not currently supported and will prevent the designer from loading.
To resolve this issue:
There is no workaround other than to attach these resource dictionaries to your current project and reference them directly (by using the Source="Dictionary1.xaml" syntax).
The following syntax may cause problems in Beta 1:
<Window.Resources>
<ResourceDictionary Source="Dictionary1.xaml"/>
</Window.Resources>
To resolve this issue:
Use the following syntax instead:
<Window.Resources>
<ResourceDictionary>
<ResourceDictionary.MergedDictionaries>
<ResourceDictionary Source="Dictionary1.xaml"/>
</ResourceDictionary.MergedDictionaries>
</ResourceDictionary>
</Window.Resources>
Dragging a Control or UserControl that is defined in a Visual Basic class library from the toolbox and dropping it on the design surface may cause the following error:
Could not load file or assembly 'Microsoft.VisualBasic, Version=2.0.5.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
To resolve this issue:
Try any one of the following options:
Option #1: Manually add a reference, and then add the control in XAML.
Option #2: Build on the command line.
Option #3: Put your controls in the same project. For controls in the same project, drag and drop works.
Option #4: After you drag and drop, close and then restart Visual Studio.
There are several common XAML load scenarios that may prevent the designer from loading. Here are workarounds for some of the cases.
To resolve this issue:
1. Bound properties that have no get accessor. Workaround: Add a private get accessor.
2. Using non-public converters. Workaround: Make the converter public.
3. Opening loose XAML files that are not associated with the current project. Workaround: Add the XAML file to your project.
- For Silverlight, controls cannot be created by dragging from Toolbox directly to the XAML.
- For WPF, controls created by dragging from Toolbox directly to XAML adds superfluous namespace declarations.
To resolve this issue:
We recommend that you drag controls to the designer.
Extensibility interfaces have changed in Visual Studio 2010 to support extensibility for Silverlight and WPF, and broaden support across Visual Studio 2010 and Blend3.
Control design times must be recompiled for Visual Studio 2010 and must implement IProvideAttributeTable instead of IRegisterMetadata.
These issues block control distribution in Visual Studio 2010 Beta 1:
The automated "toolbox control installation" method documented for earlier versions of Visual Studio is not working in Beta 1 for Silverlight. To populate the toolbox in Beta 1 with custom controls or user controls, you can either build them as part of your project or add them to your project by using the "Choose Items" dialog box that you can access by right-clicking the toolbox.
The ability to specify toolbox icons and control design times is also limited in Beta 1. Control design-times written for Visual Studio 2008 will not load in Visual Studio 2010. Expect issues in Beta 1 in getting Visual Studio 2008 design-times to work alongside Visual Studio 2010 design-times, and expect issues in getting icons to load correctly in Visual Studio 2010.
To resolve this issue:
There's no workaround available.
An error occurs when you are working with a declarative flowchart service (workflow service that uses the flowchart activity) in the designer.
To resolve this issue:
Copy the System.Activities.Design.dll assembly into the \bin\ folder of the project.
Compiling a workflow class that declares a property such as the following one causes Visual Studio to crash:
string mSharePointUrl;
public string SharePointUrl
{
get { return SharePointUrl; }
set { SharePointUrl = value; }
}
To resolve this issue:
Do not name the property by using the same name as that of the variable that stores it.
When you type an invalid expression in an Assign activity, a validation error occurs (a little red exclamation mark is displayed next to the edit box). When you fix the invalid expression by changing the variable type, the little red exclamation mark does not disappear.
To resolve this issue:
You must delete the assign activity and then create a new assign activity to use the new variable type.
In a workflow, when you try to bind a Variable<T> to an InArgument<Nullable<T>> where T is a primitive type, the expression throws a validation exception that T "is not assignable to System.Nullable`1" of T.
To resolve this issue:
In the expression, do an explicit cast to Nullable<T> by using the CType function (http://msdn.microsoft.com/en-us/library/4x2877xb(VS.80).aspx), or a similar type-conversion function (for example, DirectCast, TryCast).
When you write a workflow that contains custom activities that reference a value type that is defined in a different assembly, you must reference the assembly that contains the value type in the workflow assembly.
To resolve this issue:
To the workflow project, add a reference to the assembly that contains the value type.
Expression Text Box (ETB) is a control that is used when a custom activity designer is written. When you use this control, if you do not set the MaxLines property, one of two problems may occur:
1) When you click the ETB in Visual Studio, the value of MaxLines grows to MaxInt.
2) Visual Studio hangs.
To resolve this issue:
Explicitly set the value of the MaxLines property of the ETB.
If a user opens an existing solution that has breakpoints set and starts debugging, the debugger does not stop at the breakpoints.
To resolve this issue:
Modify the workflow by adding an empty sequence, and then rebuild and try debugging again.
On a 64-bit operating system, in the debugger, the Locals window does not show variables, the Immediate window does not recognize variables, and the Call Stack window shows unfriendly names.
To resolve this issue:
There's no workaround available.
WF Debugger in Visual Studio 2008 does not work after Visual Studio 2010 is uninstalled.
To resolve this issue:
Run Visual Studio 2008 Setup in maintenance mode and select Repair/Reinstall.
WF Debugger in Visual Studio 2010 does not work after Visual Studio 2008 is uninstalled.
To resolve this issue:
Run Visual Studio 2010 Setup in maintenance mode and select Repair/Reinstall.
Visual Studio shows the following message if you add an InvokePowerShell Activity to a Workflow, and Windows PowerShell is not installed on your operating system:
"Workflow Designer encountered problems with your document. Could not load file or assembly 'System.Management.Automation' ... or one of its dependencies. The system cannot find the file specified."
To resolve this issue:
Install Windows PowerShell.
Programmatically calling $input.MoveNext()in Windows PowerShell 2.0 fails in some cases, and scripts that use $input.MoveNext() produce unintended errors and results.
To resolve this issue:
Use the PowerShell verb foreach instead of calling MoveNext() when you iterate an array. For example:
Avoid the following code:
While ($input.movenext())
{
$input.current
}
Use this instead:
foreach ($x in $input)
{
$x
}
The current version of Visual Studio does not automatically add to a project file the referenced assemblies of activities that are not included in the .NET Framework. Therefore, adding an InvokePowerShell<TResult> to a workflow without referencing System.Management.Automation.dll raises a SEHException.
To resolve this issue:
Install Windows PowerShell and then add the reference assembly System.Management.Automation.dll to the Visual Studio Project file.
When you create a custom activity designer, if you include an expression textbox on the designer, the binding of the textbox to the owner activity is not set up by default. When you use this expression textbox in the custom activity designer at design time, it may cause Visual Studio to crash.
To resolve this issue:
Add the OwnerActivity attribute to the ExpressionTextBox element of your activity designer, as shown in the following example:
<sadv:ExpressionTextBox OwnerActivity="{Binding Path=ModelItem, Mode=OneWay}"
Expression="{Binding Path=ModelItem.Text, Mode=TwoWay, Converter={StaticResource A}}"
ExpressionType="{x:Type s:String}"/>
The Path and Mode are not restricted to the values shown in the example. They can be any valid value. For example, Mode could be set to TwoWay instead of OneWay.
When you are connected to a remote computer that is running Visual Studio 2010 and you are editing an expresion in an expression textbox, the IntelliSense highlighting may be too dark to read.
To resolve this issue:
No workaround when connected to a remote computer that is running Visual Studio 2010. This issue does not occur when you use Visual Studio 2010 on a local computer.
When you are editing in an expression textbox, a list of non-relevant errors may be displayed in the Error List pane.
To resolve this issue:
These errors can safely be ignored. They do not affect the workflow at runtime. Building, or closing and reopening the designer makes the errors disappear.
The Windows 7 RC SDK is not included in Visual Studio 2010 Beta1.
To resolve this issue:
To target the Windows 7 RC SDK, you must install the <a href="http://go.microsoft.com/fwlink/?LinkID=150217&clcid=0x409">Windows 7 RC SDK</a>.
After the SDK is installed, refer to the <a href="http://go.microsoft.com/fwlink/?LinkID=150335&clcid=0x409">Visual C++ Blog</a> for information about how to get the Windows 7 RC SDK to appear in the Platform Toolset drop-down list.
To work correctly, the Visual Studio Team System Profiler requires some Team Explorer components to be installed. Although these components are installed together with VSTS, the problem is limited to custom installations that include the Team System Profiler but exclude Team Explorer.
To resolve this issue:
1. Run Setup.exe.
2. Select Repair.
3. Go to the custom configuration installation screen.
4. Ensure that "Team Explorer" is selected for installation.
The new debugger windows, Parallel Tasks and Parallel Stacks, include various annotations that get updated when the user switches the current thread or task (yellow icon, blue highlight) and the current stack frame (yellow arrow, green arrow).
These annotations may occasionally stop updating and, therefore, present stale information. The negative experience is amplified when the user switches the thread/task/stackframe through these two windows and, because the visual feedback is unreliable, is not sure whether the action had any effect.
To resolve this issue:
A. Continue to the next breakpoint/step, and both windows will correctly refresh their annotations.
-or-
B. To refresh the views without moving from the current breakpoint/step:
1. In the Parallel Tasks window, toggle the Hexadecimal Display by using the shortcut menu.
2. In the Parallel Stacks window, toggle the External Code option by using the shortcut menu.
-or-
C. If you are running VSTS, leave Historical Debugging turned On (which is the default).
When a user presses BACKSPACE in the T-SQL editor, an error dialog box may appear with the text: "The specified ITextSnapshot doesn't belong to the correct TextBuffer." Pressing BACKSPACE in this editor also may occasionally cause Visual Studio to crash.
To resolve this issue:
Clicking OK in the error dialog box will dismiss it and let the user continue working. There is no known workaround for the sporadic crash.
Saving or pressing F5 during a debug session in ASP.NET may cause a dialog box to appear. The dialog box states that the document was modified outside the source editor and asks whether the user would like to reload it. After it appears the first time, this dialog box will be shown every time the user attempts to save or start debugging.
To resolve this issue:
On the Documents page in the Options dialog box (Tools menu, Options, Environment, Documents), clear "Detect when file is changed outside the environment" and click OK. The dialog box will no longer appear.
For Beta 1, when a project is targeting an earlier version of the .NET Framework (2.0, 3.0, or 3.5), Edit and Continue (EnC) will be disabled during debugging. This means that you cannot modify your code in debug-time and have the changes applied when the instruction pointer (IP) is moved to the next statement. The root cause of this issue is that the assembly that is generated by the compiler on build and the assembly generated by the compiler in design-time are incompatible to use for EnC.
To resolve this issue:
If your project does not have to target an earlier version of the Framework, you can work around this issue by targeting the .NET Framework 4 instead.
For Visual Basic projects:
1. In Solution Explorer, right-click your project and then click Properties.
2. On the Compile tab, click 'Advanced Compile Options'.
3. Select '.NET Framework 4' on the 'Target Framework' drop-down list.
For Visual C# projects:
1. In Solution Explorer, right-click your project and then click Properties.
2. On the Application tab, select '.NET Framework 4' on the 'Target Framework' drop-down list.
For Beta 1, when you work in a project that targets an earlier version of the .NET Framework (2.0, 3.0 or 3.5), custom debugger visualizers and type proxies will not load. Only the standard Text, XML, and HTML visualizers will work in these projects. This means that debugger features such as the Results View for previewing IEnumerable objects will only be available for projects that target the .NET Framework 4.
To resolve this issue:
If your project does not have to target an earlier version of the Framework, you can work around this issue by targeting the .NET Framework 4 instead.
For Visual Basic projects:
1. In Solution Explorer, right-click your project and then click Properties.
2. On the Compile tab, click 'Advanced Compile Options'.
3. Select '.NET Framework 4' on the 'Target Framework' drop-down list.
For Visual C# projects:
1. In Solution Explorer, right-click your project and then click Properties.
2. On the Application tab, select '.NET Framework 4' on the 'Target Framework' drop-down list.
Visual Studio closes when you close a layer diagram during validation. The following repro steps describe this scenario:
1. Create a layer diagram.
2. Right-click the layer diagram, and then click Validate Architecture.
3. While validation is running, close the layer diagram.
4. V4. Visual Studio closes.
To resolve this issue:
Do not close the layer diagram while validation is running.
The following MSBuild task does not work on a layer diagram when the diagram is in the Solution Items folder or in a modeling project:
msbuild /t:ValidateArchitecture
The following error will occur:
Error MSB4057: The target "ValidateArchitecture" does not exist in the project.
Note: Validating a layer diagram in the Visual Studio IDE will work correctly.
To resolve this issue:
Create or move the layer diagram to a Visual C# or Visual Basic project in the solution.
When you create a lifeline on a sequence diagram, Visual Studio creates an unspecified type that is linked to that lifeline and has the same name. You can view this unspecified type by looking in the UML Model Explorer. However, you cannot delete this type as long as the linked lifeline exists.
To resolve this issue:
Delete all instances of the lifeline that are linked to the unspecified type.
When you generate a sequence diagram from Visual C# code that references Visual Basic code in the same solution, no lifelines appear for the Visual Basic code.
To resolve this issue:
Perform one of the following steps:
In Solution Explorer, right-click the Visual Basic project, and then click Properties. On the Compile tab, change the Platform property to Active (Any CPU).
-or-
Generate a separate sequence diagram for the Visual Basic code.
When you generate a sequence diagram, the diagram will open and continue to be populated with data during the generation process. If you try to edit the diagram before the generation process finishes, Visual Studio will behave unpredictably or stop running.
To resolve this issue:
Do not modify the sequence diagram file during the generation process. Wait until the process finishes before you modify the diagram.
The following actions might cause unexpected behavior on a component diagram:
- Copy and paste components that have ports or interfaces.
- Copy and paste ports.
- Drag and drop ports from the UML Model Explorer.
For example, extra ports or interfaces might appear on components.
To resolve this issue:
Use ports only on components that contain parts, for example, when you want to add delegations between ports on an outer component and the parts inside a component. In this scenario, you must add ports to the outer component.
If you add ports, avoid the following actions:
- Copy and paste ports.
- Copy and paste reference ports.
- Copy and paste components that have ports. You can still create views of a component that has ports by dragging and dropping from the UML Model Explorer.
- Add more than one interface to each port.
In other scenarios, add interfaces directly to the component or to the parts inside the component instead.
The following scenarios have some issues:
1. Open your solution.
2. On the View menu, click Architecture Explorer.
3. In the first column of Architecture Explorer, under Visual Studio, click Class View or Solution View.
4. When you browse the following code elements, Architecture Explorer will not show the expected results:
- The same namespace is used in multiple projects will not show all classes in that namespace.
- Global namespaces will not show elements in those namespaces correctly.
- Lambda expressions will not appear correctly. Method calls in lambda expressions will not appear.
To resolve this issue:
No current workaround is available, except refactoring the code.
Large solutions might take some time to generate a dependency graph.
You might also encounter performance issues when you navigate the graph. Solutions that have approximately 150 classes or fewer can be expected to work with reasonable performance.
The steps for this scenario are as follows:
1. Open your solution.
2. On the Analyze menu, point to Visualize Code Dependencies, and click any option to generate a dependency graph.
To resolve this issue:
Open only a few projects in a separate new solution that is independent of the original solution, and then generate a dependency graph.
Version control: We recommend that you do not merge changes in model files and diagrams because the current file formats and tools are not optimized for this use.
To resolve this issue:
For more information, see "Managing Models and Graphs Under Source Control" in the Visual Studio Help.
Video recording in Visual Studio Team System Test Edition will not work if Windows Media Encoder is not installed.
To resolve this issue:
To enable video recording in Visual Studio Team System Test, Windows Media Encoder must be installed. Use the follwoing link to install Windows Media Encoder: http://go.microsoft.com/fwlink/?LinkId=135985
If you are running Windows Vista or Windows 7, you must also install a support update by using the following link: http://support.microsoft.com/kb/929182
If you are running Windows Server 2008, you must also install Desktop Experience by using the Server Manager. This will require you to reboot your computer.
To enable building and running a coded UI test on a build agent as part of the build process, Visual Studio Team System must be installed.
The build agent does not include the assemblies that are required to build and run a coded UI test.
To resolve this issue:
There's no workaround available.
If you create a coded UI test from an action recording that has implicit mouse hover actions, the coded UI test might not run successfully.
When the Test Runner plays back an action recording that has implicit mouse hover actions, these actions are ignored by the Test Runner. When you play back these actions from a coded UI test, the test cannot ignore these implicit mouse hover actions and might fail.
To resolve this issue:
All the implicit hovers present in the generated code must be removed manually.
A data-driven coded UI test that retrieves data from your Team Foundation Server will not run on remote test agents.
The coded UI test uses the Test Management client assembly to connect to Team Foundation Server and retrieve the data. This assembly is not installed on test agents.\
To resolve this issue:
There's no workaround available.
When a coded UI test is rerun, the following error can occur:
"The test adapter 'UnitTestAdapter' threw an exception while running test 'CodedUITestMethod1'. Exception has been thrown by the target of an invocation. External component has thrown an exception."
This occurs if the record and playback engine is in an incorrect state when you rerun the test.
To resolve this issue:
a. Stop the QtAgent32.exe process by using Task Manager.
-or-
b. Before you run the coded UI test, on the Tools menu, click Options.
Select Test Tools, Test Execution, and then clear "Keep Test Execution Engine running between test runs".
If you run tests on a Visual Studio 2010 Beta 1 Test Load Agent that is installed on Windows 7, the test run might not finish if the computer name contains lower case characters.
To resolve this issue:
Step 1: Click Start and then click Run.
Step 2: Type regedit and click OK.
Step 3: Locate the following key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\ComputerName\ActiveComputerName.
Step 4: Change the value in "ComputerName" to uppercase.
Step 5: Locate the following key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\ComputerName\ComputerName.
Step 6: Change the value in "ComputerName" to uppercase.
Step 7: Restart the computer.
Using the same client to run both Visual Studio 2008 load tests and Visual Studio 2010 load tests will break the ability to import and export test results in Visual Studio 2008.
If you run load tests by using a Visual Studio 2010 client and then use the Visual Studio 2008 load test results manager, you will encounter errors that indicate that the results manager dialog box was unable to read the Visual Studio 2010 results.
Also, load tests exported from Visual Studio 2008 cannot be imported into Visual Studio 2010.
To resolve this issue:
The workaround is to use two separate databases for your results, one for Visual Studio 2008 and one for Visual Studio 2010. The new Excel reporting feature in Visual Studio 2010 looks for the load test database, so the best workaround is to rename the Visual Studio 2008 load test database.
Before running a 2010 load test on your computer, rename the Visual Studio 2008 load test database.
1. Close all Visual Studio instances.
Run the Visual Studio Command Prompt as Administrator (can be 2008 or 2010).
3. Run
sqlcmd -S .\sqlexpress
1> EXEC sp_renamedb 'LoadTest', 'LoadTest2008'
2> GO
4. Start Visual Studio 2008
5. On the Test menu, click Administer Test Controllers.
6. Change the load test results store to the renamed database.
a) Click ...
b) Under "Select or Enter a Database Name", type "LoadTest2008".
If you run Visual Studio 2010 tests before you rename the database, you must remove the Visual Studio 2010 results from the database:
1. In Visual Studio 2010, open a load test.
2. Click the Open and Manage Test Results icon.
3. Select the 2010 test results and click Export.
4. Delete the 2010 test results.
5. Follow the earlier steps to create two databases.
6. Open Visual Studio 2010 and use Open and Manage test Results to import the Visual Studio 2010 results back into the database.
Symptom: When a user tries to save a load test that has multiple networks specified (or when the user tries to enable the network emulation diagnostic data adapter), a message box is displayed to prompt the user to bind the network emulation driver. If you are using a 64-bit computer, this dialog box is displayed correctly but the binding is not correctly set up.
[This applies to Visual Studio Team Test, Visual Studio Team System, and the load test agent on 64-bit computers.]
To resolve this issue:
Perform the following steps at an administrative command prompt.
1. Change directories to <drive>\Program Files\Microsoft Visual Studio 10.0 Network Emulation\Driver\.
[Note: Make sure that you do not select "Program Files (x86)" on the path.]
2. Execute the following command:
start /wait snetcfg.exe -v -l .\ -c s -i ms_sfilter
3. To determine whether the command succeeds, look at the properties of the network card for the computer, or you notice that the dialog box is no longer displayed. You should only have to perform this workaround one time for each computer.
A user cannot run a data-driven web or unit test that uses a .csv file, Microsoft Excel spreadsheet, or Microsoft Access database file as the data source in 64-bit mode because there is no 64-bit version of Jet OLE DB Provider to access these files. If a user tries to run the test, the test will stop or fail. If it is a unit test, the following error message is displayed:
The unit test adapter failed to connect to the data source or to read the data. For more information on troubleshooting this error, see "Troubleshooting Data-Driven Unit Tests" (http://go.microsoft.com/fwlink/?LinkId=62412) in the MSDN Library.
Error details: The 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine.
To resolve this issue:
1. Import the .csv file, Microsoft Excel spreadsheet, or Microsoft Access database file into Microsoft SQL Server database tables.
2. Change the test to use the Microsoft SQL Server database tables created in Step 1 as the data source.
3. Run the test in 64-bit mode.
The template that is required for writing an end-to-end workflow that 1) compiles the sources, 2) builds the application, 3) deploys the built application to virtual machines, and 4) runs the specified tests is not available in the Visual Studio Team System 2010 Beta 1 release.
To resolve this issue:
The workflow template will be available on the VSTS Lab Management team blog. (blogs.msdn.com/lab_management) after May 25, 2009.
When you import a virtual machine template that contains operating system profile information from Virtual Machine Manager (VMM) into Microsoft Test and Lab Manager, sensitive parameters such as domain credentials, product key, and administrator password in that profile are not imported. There is no notice that this information was not imported. As a result, a virtual environment created from that template might fail.
To resolve this issue:
After you import the virtual machine template from VMM into Test and Lab Manager, open the Advanced properties of the template and re-enter the missing operating system profile information.
A virtual environment might show that it is in a 'Mixed' state even though all the virtual machines in it are in the same state. This can happen when certain actions that are performed outside of Lab Management cause the state of virtual machines to change. For example, if a Hyper-V host on which the virtual machines are running is rebooted or if a user who is viewing the environment in Environment Viewer manually shuts down each of the virtual machines, the state of the envrionment might not get updated accurately.
To resolve this issue:
If all virtual machines in an environment are in a 'Stopped' state and the environment is in 'Mixed' state, select the environment and 'Stop' it. If all virtual machines in an environment are in the 'Running' state and the environment is in 'Mixed' state, select the environment and 'Start' it.
If you create a second copy of a virtual environment that has network isolation, when another copy is already running without network isolation, there might be network conflicts and incorrect registration of DNS records. This issue will be corrected in a future release.
To resolve this issue:
If you run two or more copies of the same virtual environment simultaneously, make sure all environments are running in isolated networks.
When you perform an operation such as a Start or a Snapshot of a virtual environment, that operation might fail and display a error message that indicates that there was a "hardware management error" on the physical host. This error could be caused by one or more known issues in Hyper-V, WS-Management, or other components of Windows.
To resolve this issue:
Review the error messages dislayed in Microsoft Test and Lab Manager and in the Jobs status section of System Center Virtual Machine Manager (VMM). Identify the physical hosts on which the hardware management errors occurred and confirm that all Windows patches recommended in the Lab Management scenario of the Team Foundation Server Installation Guide are installed. If the hardware management error is caused by a winrm timeout, then increase the timeout period by executing the following command on the physical host: 'winrm set winrm/config @{MaxTimeoutms = "1800000"}'. If the host in VMM is in the 'Not Responding' state, then do the following steps in sequence until the host responds: (i) In VMM, refresh the host. (ii) Restart the VMM agent on host (iii) Restart the host. If none of these steps work, remove the host and re-add it to the VMM host group. Warning: removing and readding the host deletes the association between Lab Management and all virtual machines and environments deployed on that host in this release.
Virtual environments that are configured to use network isolation might not be truly isolated, and the status of their network isolation capability might show as 'incomplete' or 'failed'. This can happen if the Visual Studio Team System lab agent fails to start in the typical 30-second time-out period for starting up Windows services.
To resolve this issue:
Use the Environment Viewer to connect to the virtual machines (VM) in the affected environment and increase the service startup time-out period in Windows. On every virtual machine, create or edit the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control. Assign the entry, ServicesPipeTimeout of type DWORD, a decimal value of 60000. Close the registry editor. Use the Microsoft Test and Lab Manager to stop, and then restart, the virtual environment. We recommend that you make this registry edit immediately after you install the lab agent in your VM templates.
There are no known issues.
© 2009 Microsoft Corporation. All rights reserved.