For the most current version of the Release Candidate (RC) Readme, click here.
For Beta 2, the latest version of the Readme is available here.
For Beta 1, the latest version of the Readme is available here.
1.2 Supported Operating Systems:
When users try to install Visual Studio on an encrypted drive, installation will fail because, even though the drive appears to be writeable, it is not.
To resolve this issue:
Install on a non-bitlocked drive, for example, the system drive.
Visual Studio 2010 Setup and/or the .NET Framework 4 Setup fails with a 1603 error code, or blocks running in Program Compatibility Mode.
Windows Program Compatibility Assistant indicates that Visual Studio Setup might not have installed correctly, and prompts to reinstall by using the recommended setting (Program Compatibility Mode).
To resolve this issue:
Visual Studio Setup cannot run in Program Compatibility Mode. Ensure that the compatibility mode setting is not enabled system-wide or for the Visual Studio Setup application in particular.
Check the manual setting
Compatibility mode could have been set manually on the Compatibility tab on the executable file properties.
Check Program Compatibility Assistant registry settings
Compatibility mode could have been set by Program Compatibility Assistant on previous failed or canceled attempts to run Visual Studio setup.exe.
Rerun Visual Studio Setup
Related KB Article:
If Roaming profiles are used when the home folder is disconnected from the network, Setup will fail because folder redirection issues are caused by the way that MSI installs products.
To resolve this issue:
Configure your Roaming profiles to use the local path instead of the remote connection path, or ensure that the remote home folder path is available during installation.
To switch to the local profile, following these steps:
On the domain server:
1. Set roaming profiles for the targeted user (for example, myuser), as follows:
Right-click user myuser in AD, and then click Properties. On the "Profile" tab, in the Profile path, type a UNC path that resembles \\domainserver\Rprofiles\%username% (for example, \\10.50.209.130\Rprofiles\myuser). Note: "\\domainserver" is the AD server IP, "\Rprofiles" is the new folder that will store all user roaming profiles, "\username" is the user (myuser in this example) login name.
2. Set the home folder for the targeted user, as follows:
Local path of the home folder:
Select Local path, type a local path that resembles c:\Rprofile, which will be created on the client computer for the user (myuser). Do not use a UNC path.
On the client computer:
1. Log on the client as administrator and add to the Administrator Group the user that you created on the AD server (myuser in this example).
2. Create the local path by using the path that you used in step 2 of the domain-server procedure (c:\Rprofile in this example).
3. Log on the client as the new user (myuser in this example).
4. Log off the client after the first logon. The local profiles will be saved automatically to the roaming profiles path on the server, that is \\domainserver\Rprofiles\%username% (for example, \\10.50.209.130\Rprofiles\myuser).
5. Go back to the domain server and open the user folder (c:\Rprofiles). Notice that there is a new folder (c:\Rprofiles\myuser) and many files in the folder. These files are the roaming profiles. They are synchronized automatically with the user folder on the client on logoff.
Visual Studio 2010 may also install the following important updates. We recommend that you keep them on your system:
To resolve this issue:
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.
Network issues occasionally cause corrupted files when the files are downloaded and then installed, or when the files are installed over the network. This issue manifests itself by a message in the %temp%\dd_install*.log that resembles this:
[05/16/09,17:47:12] VC 10.0 Runtime (x86): MSI Record result detail: Error 1330.A file that is required cannot be installed because the cabinet file e:\dev10dvd\wcu\vcruntimes\x86\vc_runtime_x86.cab has an invalid digital signature. This may indicate that the cabinet file is corrupt.
[05/16/09,17:47:12] VC 10.0 Runtime (x86): MSI Record result detail error code: 1330
[05/16/09,17:47:13] InstallReturnValue: GFN_MID Chained VC Runtime 2010 Beta1 x86, 0x643
To resolve this issue:
Download the installation files locally and then restart the installation.
When Visual Studio is installed on a Netbook, the navigation buttons at the bottom of the dialog box may not appear.
To resolve this issue:
In this case, check your display resolution to ensure that you have allowed for the minimum required resolution:
- 800x600 @ 100% DPI scaling
- 1024x768 @ 125% DPI scaling
- 1280x1024 @ 150% DPI scaling
When you install Visual Studio 2010, if you unplug your USB drive, then your installation might either prompt for source or fail to install due to missing temporary files.
To resolve this issue:
Either unplug all USB Drives before you install Visual Studio or do not unplug these drives during Setup because some temporary files may get copied and used on the drive that has the largest amount of free space.
To create a SharePoint project, you must have SharePoint 2010 installed on the same computer that has Visual Studio 2010.
To resolve this issue:
Install SharePoint Foundation 2010 or SharePoint Server 2010 on the computer that has Visual Studio 2010.
This section applies to Visual Studio 2010 RC. For instructions about how to uninstall earlier versions, see:
All pre-release versions must be removed in the correct order BEFORE the official release version is installed. We recommend that you uninstall the main product first (for example, Visual 2010 Ultimate), which removes the majority of the components. Then, uninstall other supporting products that may also have been installed.
To resolve this issue:
User-generated assets such as project files and custom settings are not removed or affected by uninstalling Visual Studio.
1. Open "Programs and Features" in Control Panel (also known as Add-Remove Programs):
2. Uninstall all instances of Visual Studio 2010 products (for example, Visual 2010 Ultimate).
3. Uninstall other installed supporting products, in the specified order. (Ignore items that are not present on the computer.)
a. The .NET Framework 4 Language Pack
b. The .NET Framework 4 Extended (reboot, if prompted)
c. The .NET Framework 4 Client (reboot, if prompted)
This section applies to Visual Studio 2010 RC (release candidate). For instructions about how to uninstall earlier versions, see:
All pre-release versions must be removed in the correct order BEFORE you install the official release version. We recommend that you uninstall the main product first (Visual Studio 2010), because that removes the majority of the components. Then, uninstall other supporting products that may also have been installed.
To resolve this issue:
User-generated assets, such as project files and custom settings are not removed or affected by uninstalling Visual Studio.
1. Open "Programs and Features" in Control Panel (also known as Add-Remove Programs):
2. Uninstall all instances of Visual Studio 2010 products (for example, Visual Studio 2010 Ultimate).
3. Optionally, uninstall the following supporting products that may have been installed with Visual Studio 2010. NOTE: These components may also be used by other product suites on your computer.
a. Web Deployment Tool
b. Silverlight 3 SDK
c. Visual Studio 2010 Tools for SQL Server Compact 3.5 SP2
d. SQL Server Compact 3.5 SP2
e. SQL Server 2008
f. SQL Server 2008 Native Client
g. SQL Server 2008 R2 Management Objects
h. SQL Server System CLR Types
4. Uninstall other remaining supporting products, in the specified order. (Ignore items that are not present on your computer.)
a. The .NET Framework version 4 Language Pack
b. The .NET Framework version 4 Extended (reboot, if prompted)
c. The .NET Framework version 4 Client (reboot, if prompted)
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 install optional components on Windows XP or earlier versions of Windows
In Control Panel, on the Add or Remove Programs page, select the product edition you want to add to and then click Change/Remove.
In the Setup wizard, click Next.
Click Add or Remove Features.
In the Select features to install list, select the items that you want to install and then click Update.
To install optional components on Windows Vista or Windows 7
In Control Panel, on the Programs and Features page, select the product edition you want to add to and then click Uninstall/Change.
In the Setup wizard, select Add Optional Products and then click Next.
Select the components you want to install and then click Next.
Follow the remaining instructions.
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 on Windows XP or earlier
In Control Panel, on the Add or Remove Programs page, select the product edition you want to repair and then click Change/Remove.
In the Setup wizard, click Next.
Click Repair or Reinstall.
Follow the remaining instructions.
To repair Visual Studio on Windows Vista or Windows 7
In Control Panel, on the Programs and Features page, select the product edition you want to repair and then click Uninstall/Change.
In the Setup wizard, select Repair or Reinstall and then click Next.
Follow the remaining instructions.
If you have uninstalled a product, which is required for some functionality and was installed by Visual Studio 2010 Setup, then you might notice that this component was never shown in the Customize Setup tree nor in the Add or Remove features tree. How can you get this component back?
To resolve this issue:
Open Add or Remove features, and select Visual Studio 2010. Find the feature that is related to the missing feature, for example, if you are missing Web Deployment Tools, then select the Web Deployment Feature. Click Update. This will reinstall the Web Deployment Tools companion product.
When a solution or a project file is opened in Visual Studio, code is executed to load the project. This code, in the form of build tasks and targets, can contain any action that the creator includes.
To resolve this issue:
Solution and project files should be treated the same as any executable or script file. Be sure that you trust the source of files that you intend to open.
On Windows Vista and Windows 7 development computers, files under detected dependencies in Setup projects may not appear. This could cause the dependent files to be incorrectly excluded from the deployment package. For example, if a Setup project has a dependency on msxml6.dll, the Setup project does not display this under detected dependencies and does not include it in the deployment package.
To resolve this issue:
Change the type of the TypeLib registry entry to REG_SZ. For example, the following steps demonstrate how to display msxml6.dll as a detected dependency. For other files, open the GUID that corresponds to the file that does not appear.
1. Run regedit as an administrator.
2. Navigate to this subkey: "HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\TypeLib\{F5078F18-C551-11D3-89B9-0000F81FE221}\6.0\0".
3. Right-click the "0" key, and then go to Permissions.
4. Add "write" permissions for yourself or for all administrators.
5. Rename the "win32" key under the "0" key to "win32.bak".
6. Create a new "win32" key.
7. Set the default value of the new "win32" key to the path of msxml6.dll as a REG_SZ type. This should be the same path as the default value of the "win32.bak" key, except that any environment variables in the string should be expanded before you write the value into the "win32" registry key. For example, if the "win32.bak" key default value is "%SystemRoot%\System32\msxml6.dll", the new "win32" key default value is "C:\Windows\System32\msxml6.dll".
If the .NET Framework 3.5 SP1 bootstrapper package is selected in the Prerequisite dialog box for a Setup project or in ClickOnce publishing, and also the "Download prerequisites from the same location as my application" option is selected, you may see 57 build errors including the following one:
The install location for prerequisites has not been set to 'component vendor's web site' and the file 'dotNetFx35setup.exe' in item 'Microsoft.Net.Framework.3.5.SP1' cannot be located on disk.
To resolve this issue:
Update the Package Data
Download and Extract the Core Installation Files
You can now delete the files and folders you downloaded and extracted in steps 2 and 4.
Download the Language Pack Support Files
|
Language |
Architecture |
Source URL |
Destination |
|
Chinese (Simplified) |
x86 |
zh-CHS\DotNetFX35\x86 | |
|
x64 |
zh-CHS\DotNetFX35\x64 | ||
|
Chinese (Traditional) |
x86 |
zh-CHT\DotNetFX35\x86 | |
|
x64 |
zh-CHT\DotNetFX35\x64 | ||
|
English |
x86 |
N/A |
N/A |
|
x64 |
N/A |
N/A | |
|
French |
x86 |
fr\DotNetFX35\x86 | |
|
x64 |
fr\DotNetFX35\x64 | ||
|
German |
x86 |
de\DotNetFX35\x86 | |
|
x64 |
de\DotNetFX35\x64 | ||
|
Italian |
x86 |
it\DotNetFX35\x86 | |
|
x64 |
it\DotNetFX35\x64 | ||
|
Japanese |
x86 |
ja\DotNetFX35\x86 | |
|
x64 |
ja\DotNetFX35\x64 | ||
|
Korean |
x86 |
ko\DotNetFX35\x86 | |
|
x64 |
ko\DotNetFX35\x64 | ||
|
Portuguese - Brazil |
x86 |
pt-BR\DotNetFX35\x86 | |
|
x64 |
pt-BR\DotNetFX35\x64 | ||
|
Russian |
x86 |
ru\DotNetFX35\x86 | |
|
x64 |
ru\DotNetFX35\x64 | ||
|
Spanish |
x86 |
es\DotNetFX35\x86 | |
|
x64 |
es\DotNetFX35\x64 |
The Setup.exe bootstrapper created by using the Web Setup project template does not install on computers with IIS7 until the IIS6 compatability layer is installed. You may see the following error message: "Installation was interrupted".ue:
Complete the following steps to install the IIS 6 compability layer:
1. Open Control Panel, and then open Programs and Features.
2. Click Turn Windows features on or off.
3. Expand Internet Information Services, expand Web Management Tools, and then expand IIS 6 Management Compatibility.
4. Select IIS Metabase and IIS 6 configuration compa5.
5. Click OK.
When devenv /useenv is used in Visual Studio 2010, Visual C++ directories settings from Visual Studio 2008 cannot be migrated from .vssettings file.
To resolve this issue:
Start Visual Studio 2010 by using "devenv" and not "devenv /useenv" if you want to migrate Visual Studio 2008 settings.
1. Run devenv.
2. Migrate Visual C++ 2008 directories from .vssettings file.vssettin3.
3. Close devenv.
"Inherited Project Property Sheets" property from C++ projects has been removed.
To resolve this issue:
Use Property Manager to add property sheets to the project or remove them. To open Property Manager, in Visual Studio, on the View menu, click Property Manager.
Managed Incremental Build for Visual C++ managed projects is not supported.
To resolve this issue:
No workaround is available.
When an x64 platform is created from a Win32 platform for C++ projects, the TargetEnvironment property is not correctly copied. This may cause a link error.
To resolve this issue:
1. Right-click the project.
2. Bring up property pages for the project.
3. Go to "Link->Ad4. Change property "Target Machine" to "Machine X64 (/MACHINE:X64)".
When native C++ include paths are imported from Visual Studio 2008, the user paths forcibly go before SDK paths. This prevents applications from being built if some header file names overlap.
To resolve this issue:
1. Open Property Manager by clicking Property Manager on the View menu.
2. Expand the project node and then expand the configuration|Platform nodes, and for each configuration|Platform, notice the "Microsoft.cpp.<Platform>.users" file. These are the files for the global settings, and they resemble the earlier VC++ Directories.
3. Right-click the "Microsoft.cpp.<Platform>.users" file, and then click Properties.
4. In the property page window, click "VC++ Directories" in the left pane, add a new path after $(IncludePath) in the property grid, delimited by a semicolon for "Include Directories".
5. Click the down arrow for "Include Directories" and then click "Edit"; in the dialog box that appears, use the arrows in the upper pane to move the directories.
Renaming in the IDE a C++ Windows Forms file that is checked into source control causes an error.
To resolve this issue:
Check out the file in source control.
Rename it, and then check it in.
When a Visual C++ add-in project is converted to Visual Studio 2010 and then built, it may cause the following error:
error C2871: 'Extensibility' : a namespace with this name does not exist
This build error is caused by a missing reference to the shared assembly that is located, after the conversion, at %ProgramFiles(x86)%\Common Files\microsoft shared\MSEnv\PublicAssemblies\extensibility.dll.
To resolve this issue:
1) Right-click the add-in project and then click References.
2) In the References section of the dialog box, click Add New References.
3) Click the Browse tab of the Add Reference dialog box.
4) Navigate to %ProgramFiles%\Common Files\Microsoft Shared\MSEnv\PublicAssemblies, select extensibility.dll, and click Add.
5) Rebuild the project.
The EULA shown in Extension Manager may contain extra space in a text license. The dialog box renders every carriage return and every line feed character as a new line. This creates extra blank lines when a licence agreement is rendered.
To resolve this issue:
You can fix these formatting issues by using the Visual Studio editor.
1) Open your file in the text editor.
2) On the Edit menu, click Find and Replace and then click Quick Replace.
3) Under Find options, use Regular Expressions.
4) Find what: \xD\xA.
5) Replace with \xD.
6) Click Replace All.
If you use the Visual Studio SDK to generate a WPF toolbox control, and you use whitespace characters in the project name, the assembly that is generated will also contain whitespace characters in the file name.
This can cause instability when you work with the control by using the WPF designers and the toolbox.
To resolve this issue:
1) Right-click your project in Solution Explorer and then click "Properties".
2) In the Assembly Name field, remove all whitespace characters.
3) Rebuild.
By default, the New File dialog box is configured to look in the same directory as the Visual Studio installation. In your Isolated Shell application, you can configure this dialog box to look in a different folder.
To resolve this issue:
1) In your Isolated Shell solution, locate and open the <SolutionName>.Application.pkgdef file under the Shell Customization project folder for the startup project.
2) Append the following text to this file, replacing <NewDirectory> with a subdirectory in your application's protected installation location:
[$RootKey$\Projects\{A2FE74E1-B743-11d0-AE1A-00A0C90FFFC3}\AddItemTemplates\TemplateDirs\{DA9FB551-C724-11d0-AE1F-00A0C90FFF"TemplatesDir"="<NewDirectory>"
[$RootKey$\Projects\{2150E333-8FDC-42A3-9474-1A3956D46DE8}\AddItemTemplates\TemplateDirs\{DA9FB551-C724-11d0-AE1F-00A0C90FFFC3}\/1]
"TemplatesDir"="<NewDirectory>"
Miscellaneous files added to a Visual Studio project or item template project are not included in the zip file that is generated during the project build.
To resolve this issue:
For each file you want to include in your project, set the BuildAction to "ZipItem". This will generate in your bin directory a custom zip file that contains all the required files.
The pkgdef format does not allow the "]" or "[" characters because they are reserved for the beginning and end of tokens.
To resolve this issue:
Do not use "]" or "[" in your pDo not use "]" or "[" in your pkgdef file except for tokens.
When you reset your user data and import a Visual Studio 2008 settings file, the contents under Projects and Solutions in the Options dialog box display incorrect values. ue:
1) On the Tools menu, click Options.
2) Click the Projects and Solutions Node.
3) Manually change the Projects location, User project templates location, and User item templates location to the new locations. If necessary, remove the extra "1" at the end.
In an add-in, when <Assembly: ComVisible(True)> is modified to <Assembly: ComVisible(False)> the add-in fails to load.
To resolve this issue:
This is not supported. Add-ins are built on top of a COM infrastructure, and although the add-in is written in managed code, the assembly ComVisible attribute must still be set to true.
When you create an add-in, and change the Framework target to a version that is earlier than the .NET Framework 4, build warnings will occur. This happens because there are additional references that are added to support the .NET Framework 4.
To resolve this issue:
Remove the following references from your add-in project:
EnvDTE100
Microsoft.CSharpMicrosoftSystem.Core
When you build a VSIX deployed project or item template that targets the Web, you must put the template in a specific directory for it to show up correctly in the New Project dialog box or New Item dialog box. If the directory structure in the VSIX is incorrect, the template may appear at the root of C# or Visual Basic.
To resolve this issue:
1) Put the item or project template zip file under ...\Template\CSharp\Web\ or ...\Template\VB\Web\, relative to the root of your VSIX file.
2) In your source.extension.vsixmanifest file, add a project or item template reference that points to this file.
SolutionPersistenceRegistrationAttribute code must be added to your project before the attribute can be used.
To resolve this issue:
If you use the SolutionPersistenceRegistrationAttribute class in your code when you autogenerate a pkgdef file, you must add the code found in the MPF Sources in your Visual Studio SDK installation. The source can be found in ..\VisualStudioIntegration\Common\Source\CSharp\RegistrationAttributes\SolutionPersistenceRegistrationAttribute.cs.
Help Library Manager (HLM) uses the BITS service to download content. If HLM is started by using the "Run as" feature, BITS will not be able to schedule jobs because the service is available only to the logged-on user account.
To resolve this issue:
When you download content, start HLM under the user account that is currently logged on.
Setup does not remove local Help content when you uninstall Visual Studio. The default location for the local content directory changed between Beta 2 and this release.
To resolve this issue:
If you have already uninstalled Visual Studio, you can manually delete the files in the local Help content directory. If you did not reuse the Beta 2 local Help content directory you must manually delete the Beta 2 content directory to remove it from your computer.
On Windows Server 2008 systems that have Internet Explorer running with restricted permissions, the offline Help viewer search button and the code snippet tabs might not be clickable.
To resolve this issue:
You can add 127.0.0.1 to the I.E. trusted sites. Alternatively, for the search button issue, you can press ENTER to perform the search.
When you are running Help Library Manager (HLM) on Windows XP, if you attempt to set the local content store to a UNC path (path starts with \\), HLM displays a misleading error message. When HLM checks that the local store directory is a valid and writeable location, it incorrectly reports that the UNC path is a system directory. This causes HLM to display a misleading error message.
To resolve this issue:
This is no workaround.
Visual Studio switches from hardware-accelerated rendering to software rendering when it is running in virtualized environments. Installing the HyperV role causes Visual Studio to fail to detect the correct rendering settings.
To resolve this issue:
To manually enable hardware-accelerate rendering:
1) On the Tools menu, click Options.
2) Under Environment, on the General page, in the "Visual experience" group, clear the "Automatically adjust visual experience based on client performance" option.
3) Select "Use hardware graphics acceleration if
4) Click OK.
User Keywords color settings imported from Visual Studio 2008 do not get reflected in Visual C++ 2010.
To resolve this issue:
There is no workaround.
During debugging, the IntelliSense live error reporting (red wavy underlines) and QuickInfo tooltip information are not available for C++. This is because the tooltip UI gets used by expression evaluator during debugging and wavy underlines are not available because they depend on QuickInfo to be available.
To resolve this issue:
There is no workaround. Currently, live error reporting and tooltip information are not supported for C++ during debugging.
IntelliSense is not available for C++/CLI in this release of Visual Studio. However, all browsing features (ClassView, GotoDef, Find All References, Navigate To, etc) are still available for C++/CLI.
To resolve this issue:
There is no workaround. IntelliSense for C++/CLI is not supported in this release of Visual Studio.
It is not currently possible to automatically generate JScript event handlers for client-side controls in User Controls (ASCX files) in Visual Web Developer. This means that double-clicking on the control in design view or using the navigation bar in source view will not generate an event handler. For example, it is not possible to automatically generate an onclick event handler for <input id="Button1" type="button" value="button" />
To resolve this issue:
There are two possible workarounds:
1. The first workaround is to generate the desired event handler in a temporary Web form (ASPX file), and then paste the generated code from the Web form file into the user control file.
a. Create a temporary Web form webform.aspx.
b. Add the desired control (e.g., <input id="Button1" type="button" value="button" />).
c. Generate the desired event handler (e.g., double-click the button in design view to generate an onclick event handler).
d. Copy the generated event handler and attributes to your user control. E.g., copy onclick="return Button1_onclick()" to the button markup in your user control, and copy the generated script entry to the user control as well.
<script language="javascript" type="text/javascript">
// <!CDATA[
function Button1_onclick() {
}
// ]]>
</script>
2. The second workaround is to type the event handler manually into the code when you are working with user controls.
There are no known issues.
If you have a SharePoint solution that contains two site definitions, and you create a site by using the first site definition, you get the following error if you attempt to create a site based on the second site definition:
Error
The template you have chosen is invalid or FAILED hr detected (hr = 0x81071e44)
To resolve this issue:
Either close and restart Visual Studio, or end the vssphost4.exe process by using Task Manager.
You cannot invoke the URL picker from properties of the CSSLink control and the DateTimeControl.
To resolve this issue:
There is no workaround.
If you add customized server control to the project, the assembly that contains the control is not automatically added to the \bin\ directory when you compile the project. As a result, the assembly is not deployed to the SharePoint server when you run the project.
To resolve this issue:
Add the custom assembly in the Advanced page of the Pacakage Designer.
Content types are not deployed when Visual Studio 2010 RC is used with Sharepoint 2010 Beta 2.
Sharepoint 2010 Beta2 does not support the 'Inherits' attribute that is used in Content types created by Visual Studio 2010 Tools for SharePoint development. This causes deployment failure. Without the 'Inherits' attribute, the sandbox content types cannot inherit custom fields from the base content type.
To resolve this issue:
In the 'elements.xml' file of the content type, remove the 'Inherits = true' line.
For Sandboxed solutions, if the content type inherits from a base content type that has custom fields, then the inherited content type has to have the field refs (from the base content type) copied in its elements.xml for the fields to show up in the inherited content type.
If you attempt to deploy a BDC model that is created in Visual Studio 2010 to SharePoint Foundation 2010, you get the following error message:
Error 1 Failed to load receiver assembly "Microsoft.Office.SharePoint.ClientExtensions, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" for feature "SharePointProject4_Feature2" (ID: 90146a35-91c1-4d4d-ac01-8cd24614b540).: System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Office.SharePoint.ClientExtensions, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' or one of its dependencies. The system cannot find the file specified. the file specified.
File name: 'Microsoft.Office.SharePoint.ClientExtensions, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c'
at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
at System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
at System.Reflection.Assembly.Load(String at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject()
To resolve this issue:
Perform one of these actions:
- Create a feature event receiver that enables the import of solution packages (.wsp files) that contain BDC models, as outlined in the document http://go.microsoft.com/fwlink/?LinkID=165499&clcid=0x4095499.
- Upgrade to either Microsoft SharePoint Search Express or SharePoint Server 2010.
Team build of SharePoint projects is not supported by out-of-box functionality of TFS/Team Build because of the dependency on SharePoint and custom build targets and tasks.
To resolve this issue:
MSDN article here: http://go.microsoft.com/fwlink/?LinkID=165499 will provide step-by-step instructions for customers to manually enable build and packaging of SharePoint projects on a TFS/Team Build computer. We expect the article to be available when Visual Studio 2010 is released.
In Visual Studio 2010, several new Visual C# and Visual Basic language features are not available in SharePoint projects.
To resolve this issue:
There is no workaround.
Execution does not stop at breakpoints that are set in the XML markup of an application page or Visual Web Part.
To resolve this issue:
1. On the Debug menu, click Options and Settings.
2. In the Options dialog box, click General, and then clear "Require source files to exactly match the original version".
On the second deployment of a SharePoint workflow, a older version of the workflow may be displayed in the Workflow Designer during debugging. In addition, not all build errors are displayed at times. This is only a display issue with the Workflow Designer; the correct workflow is run in SharePoint.
To resolve this issue:
Change the signature of the assembly that is being stored in the Global Assembly Cache (GAC) on subsequent deployments. The easiest way to do this is to change the assembly version. To avoid this problem, edit the assembly.cs or assembly.vb file to auto-increment the assembly version number on every build.
Breakpoints set on the Workflow Designer do not break correctly in SharePoint projects.
To resolve this issue:
Set breakpoints in the workflow code file, either workflow.cs or workflow.vb. Breakpoints in the code file will break correctly.
When you convert a solution to the Visual Studio 2010 format, you are prompted to back up your solution to a given location. In this location, projects will be backed up but Web sites will not be. The only file that should change during the Web site conversion process is your web.config file, and it will only change if you choose to upgrade to the .NET Framework 4.
To resolve this issue:
Create manual backups of your Web sites before conversion.
Visual Studio 2010 installation reports that the Silverlight runtime failed to install with a disk space error if a newer version of the Silverlight end user runtime is installed.
To resolve this issue:
Silverlight is is an optional component. If an installation failure is encountered, the user can ignore the failure. Visual Studio 2010 will verify that the developer runtime is present at design-time when it opens a Silverlight project and will prompt the user to download the latest version of the developer runtime if it is not installed.
Users who are using the Visual Basic profile may encounter situations where the Silverlight XAP file is not copied to the hosting Web project when they build or run their solutions. This is caused by a profile setting in which only the Start Project and its dependencies are built. In this case, however, the start project is the Web project, and it does not have a dependency on the Silverlight project. This causes the Silverlight project to not be built/updated.
To resolve this issue:
Under Tools -> Options -> Projects and Solutions -> Build and Run, clear the "Only build startup projects and dependencies on Run" check box.
There are no known issues.
The WPF & Silverlight Designer Team (Cider Team) has just launched a team blog at: http://blogs.msdn.com/wpfsldesigner/default.aspxesigner/default.aspx
The initial content will focus on the Designer tool set, walkthroughs using the Designer, FAQ, and posts. Additionally, you can leave feedback for the Cider Team on the blog.
1. Set the environment settings for Visual Studio to C# environment settings.
2. Create a Visual Basic workflow project.
3. Click in any expression editor.
4. While focus is in the expression editor, Visual Studio hangs.
To resolve this issue:
Move focus from the expression editor before you press F6.
This problem is reproducible on Windows Server 2008 Enterprise 64-bit operating systems.
1. Create a workflow application that targets the .NET Framework 3.0 or 3.5.
2. Create a workflow that has validation errors.
3. Close the workflow document, so that the workflow file is closed and the validation errors are still visible in the error list.
4. Double-click an error. Notice that the workflow designer fails to load.
To resolve this issue:
Open the workflow document before you double-click errors..
There are no known issues.
When you try to open an IntelliTrace file that has the extension *.tdlog from Visual Studio 2010 Beta 2, an error occurs that prevents the file from being opened. This is due to a file name extension change between Beta 2 and this release. The new file name extension for IntelliTrace files is *.iTrace to match the brand of the IntelliTrace.
To resolve this issue:
Change the extension from ".tdlog" to ".iTrace" and the file should open correctly.
If Visual Studio crashes or is stopped from Task Manager, IntelliTrace log files that were created while debugging will not be deleted when Visual Studio exits.
To resolve this issue:
Open "Tools -> Options -> IntelliTrace -> Advanced" and copy the value of "Location of IntelliTrace Recordings".
Open Windows Explorer.
Paste the copied value into the Windows Explorer. Manually delete unwanted .iTrace files.
2.4.11 Architecture ToolsThis is a change from Visual Studio 2010 Beta 2. It affects code written against the modeling API.
Program code written for the Beta 2 version of the API will no longer compile. The following types no longer exist: IActivityDiagramContext, IClassDiagramContext, IComponentDiagramContext, ISequenceDiagramContext, IUsecaseDiagramContext.
To resolve this issue:
Where you have code like this:
[Import] public IClassDiagramContext ClassDiagramContext {get; set;}agramContext {get; set;}
// or ISequenceDiagramContext and so on
...
IClassDiagram classDiagram = ClassDiagramContext.CurrentDiagram;
Change it to:
[Import] public IDiagramContext DiagramContext { get; set; }
...
IDiagram diagram = DiagramContext.CurrentDiagram;
IClassDiagram classDiagram = diagram as IClassDiagram;
// or ISequenceDiagram and so on
For more information, see How to Define and Install.
Program code that uses the UML API ModelingProject.Load() will not compile.
This is used in code that reads a UML model from a file.
To resolve this issue:
Use ModelingProject.LoadReadOnly() to load a project. The type of the returned value is IModelingProjectReader.
Find code that resembles this:
IModelingProject project = ModelingProject.Load(projectFilename);
Replace it with this:
IModelingProjectReader reader = ModelingProject.LoadReadOnly(projectFilename);
Notice that the type returned by this method has also changed, from IModelingProject to IModelingProjectReader.
For more information, see How to Read a UML
The type IModelingProject still exists, and you can use it to access and update a modeling project that is open in Visual Studio. See How to Open a UML Model by using the Visual Studio API
Text templates fail to find assemblies referenced by the current project.
The current project's references are no longer used to find assemblies.
To resolve this issue:
In an assembly directive, state the location of the required assembly explicitly.
You can use Visual Studio macros such as $(ProjectDir) or Windows environment variables such as %ProgramFiles% as part of the assembly location.
Code that uses the text templating API and that worked in previous editions fails to compile.
To resolve this issue:
microsoft.visualstudio.texttemplating.vshost.dll
microsoft.visualstudio.texttemplating.dll
Microsoft.VisualStudio.TextTemplating.10.0
Microsoft.VisualStudio.TextTemplating.Interfaces.10.0
Microsoft.VisualStudio.TextTemplating.Interfaces
Replace it with:
Microsoft.VisualStudio.TexMicrosoft.VisualStudio.TextTemplating.VSHost as appropriate.
When you want to step through execution of a text template, a call to System.Diagnostics.Debugger.Break() does not result in entering a debugging instance of Visual Studio. Instead, a message appears that reports "User defined breakpoint - Windows is checking for a solution to the problem". This happens in Windows 7 an
To resolve this issue:
Additionally to the call to Break(), insert the following call at the point where you want to start stepping through execution:
System.Diagnostics.Debugger.Launch();
In Visual Studio 2008, you could specify a particular version of the template programming language. For example: <#@ template language="VBv3.5" #>.
In Visual Studio 2010, the valid values for the language parameter are "VB" and "C#" and the version 4 compiler will always be used. If you specify "VBv3.5" or "C#v3.5", you will get a warning message that the version 4 compiler will be used instead.
To resolve this issue:
In Visual Studio 2008, the default compiler for text templates is 2.0. If you want to use language features that are not available in 2.0, you must specify v3.5 explicitly.
If you want to use the same template in both versions of Visual Studio, then you can just ignore the warning message in Visual Studio 2010.
Users trying to type the name of line or arrow objects without a name in the designer surface of a UML Component Diagram or a Use Case Diagram, will fail to do so if they are using an IME to enter the name.
For instance, users cannot use an IME to type directly on the designer surface the name of a Dependency, Association, Generalization or Delegation, Part Assembly or Connector. The cause of the problem is that the addition of the label on the designer surface is triggered by an OnKeyDown event, and IMEs don't fire that event.
To resolve this issue:
Instead of typing the name of the abovementioned objects directly on the designer surface, type it as the value for the Name property, in the Properties window.
Coded UI Test Project structure has been changed between Beta 2 and RC. In addition, there have been significant changes in the API. All projects created by using Visual Studio 2010 Beta 2 must be upgraded to RC.
The list of changes are as follows:
1. UserControls.cs file has been removed. All specialized classes (HtmlButton, WinEdit, WpfCheckbox etc) are now part of the product.
2. 'Internet Explorer Server' control used to be part of the UI Control hierarchy for Html Controls. This has been removed to enable better support for extensibility.
3. For searching a Browser Window, exact name match will be used.
4. The names of properties (e.g: DisplayText of a HtmlButton) previously used to be in a separate class hierarchy (e.g: HtmlProperties.Button.DisplayText). This has now been modified to be part of the definition of each specialized class. Therefore, HtmlButton.PropertyNames.DisplayText will now give the name of the DisplayText property
5. Classes that did not have any additional property on them will now be treated as Custom classes. E.g., HtmlForm will now be treated as a HtmlCustom and its TagName property will be set to 'Form'. Windows Forms controls that do not have additional properties will be treated as a WinControl. WPF controls that do not have additional properties will be treated as a WPFControl.
To resolve this issue:
1. Start the Visual Studio Command Prompt window.
2. Run fUITestUpgrade.exe <name of folder(s) to upgrade>
- This upgrade tool will fix all the changes listed in the problem statement.
- All the folders under the specified folder(s) are searched recursively and all projects under are upgraded.
- Multiple folders may be specified, separated by comma.
- If a project is under source control, the upgrade tool will check it out of source control.
- A backup folder is created and all contents of the specified folder copied to it before making changes.
When you rename or add UI Test Files in a Coded UI Test Project, there are some caveats as listed below.
1. The Default UI Test file (UIMap.uitest) must not be renamed..
2. If an existing UI Test file is added to a Coded UI Test Project, the corresponding code files are not added automatically.
3. After a UI Test file is renamed and code generated from it, the references of the corresponding UI Map are not updated.
4. If a UI Test File that has the same name as an existing file in the Project is added, the existing file will be overwritten. For example, if you have AppToTest.cs in the Coded UI Test Project and you add AppToTest.uitest, AppToTest.cs will be overwritten.
To resolve this issue:
- After a UI Test File is renamed,
a. Open the UI Test file with Coded UI Test Builder.
b. Click on Generate code button in Coded UI Test Builder. This will update the code in the Designer.cs.
c. Open the corresponding .cs file and rename the class.
d. Search for all references to the new UI Map class and replace them.
- After adding an existing UI Test file to a Coded UI Test Project
a. Open the UI Test file by using Coded UI Test Builder.
b. Click Generate code in Coded UI Test Builder. This will add the Designer.cs and .cs files.
- Do not add a UI Test file that has the same name as an existing file in the Coded UI Test Project.
When you try to run tests from Visual Studio 2010 with test settings that run your tests on your local computer but collect data from remote computers, the tests do not run. The following steps describe this situation in detail:
1. Install Visual Studio 2010 Premium or higher.
2. Install on a second computer Test Controller and Test Agent.
3. Configure the agent to connect with the controller.
4. Open Visual Studio 2010 Premium or higher.
5. Create a C# Test Project.
6. Open the Local test settings.
7. Go to the Roles tab.
8. Select Local Execution with Remote Collection in the Test Execution Method box.
9. Type in the controller name.
10. Save and close.
11. Run the Tests.
To resolve this issue:
There is no workaround.
To upgrade from Visual Studio Lab Management 2010 Beta 2 to Visual Studio Lab Management 2010 RC, you must also upgrade Team Foundation Server, Visual Studio, all test controllers, all build controllers, and all agents (lab, test, and build) installed on the virtual machines.
To resolve this issue:
Before you upgrade to Visual Studio Lab Management 2010 RC, you must first upgrade Team Foundation Server. For the steps to upgrade, see the "Installation Guide for Team Foundation" on the Microsoft Web site http://go.microsoft.com/fwlink/?LinkId=127730om/fwlink/?LinkId=127730.
For the steps to upgrade Visual Studio Lab Management 2010 Beta 2 to Visual Studio Lab Management 2010 RC, see the instructions and checklist on the Microsoft Web site http://go.microsoft.com/fwlink/?LinkId=181530.
If Visual Studio 2010 RC is used to manage build definitions (by using LabDefaultTeamplate.xaml build process template) that were created by using Team Foundation Server 2010 Beta 2, the following issues might occur due to the change in the structure of the Lab Process Settings:
a. If a new build definition is created by selecting LabDefaultTemplate.xaml as Build Process Template and providing the appropriate values in Lab Process Settings, the build definition is created without any error or warning message. But when a build is queued from this build definition, the build fails because of null parameters.
b. If an existing build definition which was created by selecting LabDefaultTemplate.xaml as Build Process Template is edited and Lab Process Settings are changed, the build definition can be saved. But, when a build is queued, the build fails because of null parameters.
c. If Lab Process Settings are modified while queuing a build from a build definition that was created by selecting LabDefaultTemplate.xaml as Build Process Template, the modified Lab Process Settings do not take effect. The build executes by using the Lab Process Settings specified previously.
To resolve this issue:
If you perform any of the following operations on build definitions that use LabDefaultTemplate.xaml, make sure the version number of Team Foundation Server 2010 matches the version number of Visual Studio 2010:
- Creating a build definition
- Editing a build definition
- Modifying process parameters while queuing a build definition.
You can specify a service account in the Lab Management step when you create a Team Project Collection by using the 'Create Collection' wizard from the Team Foundation Administrator Console. This account is not granted appropriate permissions. Without these permissions the testing and workflow capabilities on all the virtual environments in this project collection cannot be enabled and will show a state of 'Failed'. For example, you will see the following error on the testing capability in a virtual environment: "Permission denied because this operation can only be performed by members of machine group 'TeamTestAgentService' on machine '<machine_name>' or by accounts having the 'create test run' permission on team project '<project_name>'."
This problem can occur only if you set the lab service account from the 'Create Collection' wizard. You will not encounter this problem if you set the service account from the 'Lab Management' tab for an existing project collection.
To resolve this issue:
1. Log on the computer on which Team Foundation Server Application Tier is installed. To reset the permissions for the lab service account, run the following command from the <TFS installation folder>\tools folder:
TFSLabConfig.exe SetServiceAccount /collection:<TeamProjectCollectionURI> /user:<serviceAccountName>
ex: TFSLabConfig.exe SetServiceAccount /collection: http://myTFS:8080/TFS/myCollectionFS:8 /user:"myDomain\svcUser"
2. To avoid running into this problem, you can skip the step to set a service account when you create a Team Project Collection from 'Create Collection' wizard. Once the collection is created, you can set the service account from the 'Lab Management' tab in the project collection properties from Team Foundation Administration Console.
There are no known issues.
For a list of known issues and other information about ASP.NET MVC 2 RC, see the readme file located at http://go.microsoft.com/fwlink/?LinkID=157072. Note: The ASP.NET MVC 2 RC release is included in Visual Studio 2010 RC.
© 2010 Microsoft Corporation. All rights reserved.