1.1 Supported Architectures
1.2 Supported Operating Systems
1.3 Hardware Requirements
2. Known Issues
During Visual Studio Setup on Vista there is a required reboot to apply an update to the OS. If the user is not logged in using the Administrator account, Visual Studio Setup will not resume automatically after the machine is restarted.
To resolve this issue:
After the machine restarts, log in and re-launch setup manually to resume Visual Studio Setup or run setup while logged in using the Administrator account.
This issue can be safely ignored. Setup will resume.
To resolve this issue:
No workaround is available.
Installing Visual Studio 2008 on a Windows Vista computer that has had earlier versions of the .NET Framework 3.5 may fail.
To resolve this issue:
Open Control Panel, click Programs & Features, and then click "View installed updates" in the Tasks pane. Select and uninstall the following Windows updates:
- Hotfix for Microsoft Windows (KB110806)
- Hotfix for Microsoft Windows (KB930264)
- Hotfix for Microsoft Windows (KB929300)
Installing Visual Studio 2008 may bring up a dialog box that prompts to close running applications. Some of the applications may have numeric identifiers and some may have an empty identifier. You may see the message box with Process IDs of applications that should be closed. You will not be able to see name of applications that should be closed.
To resolve this issue:
- We recommend that you close these applications so that they do not affect the installation process. You can find names of applications that should be closed by looking up the Process IDs in Task Manager, as follows.
1. Press CTRL+ALT+DEL and then click Task Manager.
2. On the View menu,click Select Columns.
3. Make sure PID (Process Identifier) is selected and then click OK.
4. In Task Manager, click PID to sort entries PID. 5. Look for Process IDs shown in the message box.
Or, you can click Ignore and continue with the installation. This may require a reboot at the end of setup.
When Visual Studio 2008 is installed on the same computer as Visual Studio 2005, Visual Studio 2005 repair will fail to repair the .NET Framework 2.0.
To resolve this issue:
Repair the .Net Framework 2.0 separately by using Add or Remove Programs.
Installing Visual Studio 2008 requires a reboot on all Windows Vista platforms. When the user is prompted, there may be 2 reboot dialog boxes, one from the Visual Studio 2008 Setup and one from Windows Vista. We recommend that the user only use the Visual Studio 2008 Setup prompt.
To resolve this issue:
No workaround is available.
When Visual Studio 2008 is installed on a Windows Vista SP1 Beta platform, the .NET Framework has mismatched versions. This causes random failures in the product.
To resolve this issue:
No workaround is available.
Installing Visual Studio 2008 on Windows Vista mayl randomly fail. This could happen if SMS or Windows Update are installing packages on the computer at the same time as Visual Studio 2008 Setup is running.
To resolve this issue:
Wait for SMS/Windows Update to finish. Re-boot the machine and then restart VS Orcas setup.
Setup finish pages has script error 887600de in SIT13948.tmp\install1.htm
Line: 159
Character: 5
Error: Could not complete operation due to error 887600de.
Code: 0
URL: file:///D:\Users\MSLAB2\AppData\Local\Temp\SIT13948.tmp\install1.htm
To resolve this issue:
Clicking Yes to both instances of the error message to enable Setup to finish.
A user might get the message "A problem has been encountered while loading the setup components. Canceling setup," and then Setup is cancelled. This only occurs on systems that do not have Windows Installer 3.1 installed.
To resolve this issue:
1. In Add or Remove programs and check if Windows Installer 3.1 is in the list of installed programs.
2. If Windows Installer 3.1 is not in installed programs list, please use following steps.
a. Go to Windows Installer 3.1 Redistributable (v2) and install Windows Installer 3.1
b. Retry Visual Studio 2008 installation
If you have installed an earlier version of Visual Studio 2008, such as a Community Technical Preview (CTP), then you must uninstall it in the following order. If you uninstall Visual Studio by using Add or Remove Programs, all pre-release components will be chain-uninstalled with the product. This lets the user uninstall an earlier release of Visual Studio 2008 and then install a newer release of Visual Studio 2008 without manually uninstalling the product.
1. Go to the Control Panel and open Add or Remove Programs.
2. Remove "Microsoft SQL Server Compact Edition 3.5".
3. Remove "Microsoft SQL Server Compact Edition 3.5 Design Tools".
4. Remove "Microsoft SQL Server Compact Edition 3.5 for Devices".
5. Remove "Microsoft Visual Studio Performance Collection Tools".
6. Remove "Windows Mobile 5.0 SDK R2 for Pocket PC".
7. Remove "Windows Mobile 5.0 SDK R2 for Smartphone".
8. Remove "Crystal Reports 2007".
9. Remove "Visual Studio Asset System".
10. Remove "Visual Web Developer Design Service Reminder Tools".
11. Remove "Microsoft Visual Studio 2005 Tools for the 2007 Microsoft Office System Runtime".
12. Remove "Microsoft Visual Studio 2005 Tools for the 2007 Microsoft Office System Runtime Language Pack". This step is not required if you have only the English edition.
13. Remove "Microsoft Visual Studio Tools for Office Runtime 3.0".
14. Remove "Microsoft Visual Studio Codename Orcas Professional" or other related Visual Studio IDE installations, such as Professional, Standard, Enterprise Architect, or Team Suite.
15. Remove "Microsoft Document Explorer".
16. Remove "Microsoft Document Explorer 2005 Language Pack". This step is not required if you have only the English edition.
17. Remove "Microsoft Device Emulator 3.0".
18. Remove "Microsoft .NET Compact Framework 2.0 SP1".
19. Remove ".NET Framework 2.0 SDK".
20. Remove "Microsoft Visual Studio Codename Orcas Remote Debugger".
21. Remove "Microsoft Visual Studio 64bit Prerequisites Beta". This step is required only if Visual Studio is installed on a 64-bit computer.
22. Remove "Microsoft .NET Framework 3.5".
Note: If two or more Visual Studio 2008 products are installed on the same computer and then one of them is uninstalled, the remaining products may be broken. The chained uninstall of any pre-release version of Visual Studio 2008 will chain uninstall applications that are shared by all the products. To fix any remaining product, run Repair on it so that the shared applications will be reinstalled.
To resolve this issue:
No workaround is available.
Setup stops with the error message, "Setup failed to stop Windows Installer service. You must stop all other applications running Windows Installer service or restart your computer before the installation"
To resolve this issue:
Try the following options.
- This error message indicates that a Setup other than Visual Studio 2008 Setup might already be running on your computer. After the other Setup has completed, restart your computer and then run Visual Studio 2008 Setup.
- This might also happen when Windows Update is installing updates on the computer. Wait for Windows Update to finish and then restart your computer and run Visual Studio 2008 Setup.
- Check for msiexec.exe in Task Manager. If msiexec.exe is already running, wait for it to finish, and then restart your computer and run Visual Studio 2008 Setup.
- If none of the above apply to your problem, restart your computer and run Visual Studio 2008 Setup.
There are no known issues.
There are no known issues.
There are no known issues.
2.1.5.1 Javascript intellisense, coloring and syntax validation may not work when Silverlight Tools or Team Explorer (Team Foundation Client) Beta 2 is installed
Uninstalling Silverlight Tools for Visual Studio 2008 Beta 1 or installing Team Explorer (Team Foundation Client) Beta 2 after installing Visual Web Developer 2008 Express Edition Beta 2 may lead to non availability of Javascript intellisense, coloring and syntax validation. This is due to a setup conflict for the Javascript authoring component.
To resolve this issue:
Repair the Visual Web Developer 2008 Express Edition Beta 2 installation by running the setup again. This will restore the Javascript functionality in Visual Web Developer 2008 Express Edition Beta 2.
If you install Visual Studio 2008 on the same computer as Visual Studio 2005 and then uninstall Visual Studio 2008, some Visual Studio 2005 features might stop working.
To resolve this issue:
Use Add or Remove Programs to repair Visual Studio 2005.
Uninstalling any Visual Studio 2008 product triggers an uninstallation of the .NET 3.5 Framework. This breaks any other installed Visual Studio 2008 product because all Visual Studio 2008 products depend on the .NET 3.5 Framework.
To resolve this issue:
Repair the installation by using Add or Remove Programs, or by downloading and running the Visual Studio 2008 product installer.
Visual Studio Express uninstall will prompt user to close existing applications which could affect uninstall process. User will see the message box with process ids of applications that should be closed. User will not be able to see name of applications that should be closed.
To resolve this issue:
User can find names of applications that should be closed by looking up process id in the task manager.
1. Press Ctrl-Alt-Del and select task manager.
2. Click on 'View' from top level menu
3. Click on 'Select Columns' menu item
4. Check the following checkbox if its unchecked 'PID (Process Identifier)' and Click 'Ok'
5. Click the 'show processes from all users' button
6. In task manager, click on 'PID' so that task manager entries are sorted by PID
7. User can search process id shown in the message box in this list.
SQL Server Compact 3.5 .msi files are not removed when you uninstall Visual Studio Code Name “Orcas” CTP. If SQL Server Compact 3.5 .msi files are not manually removed after Visual Studio Code Name “Orcas” CTP is uninstalled, the latest version of the SQL Server Compact 3.5 .msi files will not be installed with the later versions of Visual Studio.
To resolve this issue:
1. To manually remove SQL Server Compact 3.5 components, use Add or Remove Programs. The SQL Server Compact 3.5 components are the following:
SQL Server Compact 3.5
SQL Server Compact 3.5 for Devices
SQL Server Compact 3.5 Design Tools
2. Run Visual Studio 2008 Setup and install the SQL Server Compact components.
When Visual Studio 2008 Beta 2 is uninstalled, all SQL Server Compact 3.5 components are also uninstalled. This can create problems if two Visual Studio 2008 Beta 2 products (for example, Visual Studio 2008 Beta 2 Standard and Visual Studio 2008 Beta 2 C# Express) are installed on the same computer. If one of the Visual Studio 2008 Beta 2 products is uninstalled, then all the SQL Server Compact 3.5 components are also uninstalled and the other Visual Studio 2008 Beta 2 product will not function correctly.
To resolve this issue:
Run the Visual Studio 2008 Beta 2 product installation and select Repair to reinstall the SQL Server Compact 3.5 components.
There are no known issues.
There are no known issues.
There are no known issues.
There are no known issues.
If the full MSDN Library documentation is not installed, then when the local documentation is used and a link is clicked, the user receives an "Information Not Found" page even if an online version of the documentation exists. All links in the local documentation redirect to their local destination regardless of the user's online help settings.
To resolve this issue:
No workaround is available.
When a project is opened or created, XML IntelliSense in Visual Basic or Visual Web Developer may not be available. This happens because the XML editor package that XML IntelliSense depends on is not being loaded.
To resolve this issue:
Open or create an XML document in Visual Studio before you open or create the project.
The O/R Designer in Visual Studio 2008 maps database columns of Binary, Image, Timestamp and Varbinary types to System.Byte[] when a table that contains columns of these types are dragged to the Designer. Because System.Byte[] is not supported for identity members, setting these columns as a primary key may result in a runtime error. Note that SqlMetal.exe in Visual Studio 2008 maps columns of the above listed types to System.Data.Linq.Binary type, which can be used as primary key. Opening a SqlMetal.exe-generated .dbml file in the O/R Designer might corrupt the mapping for these types.
To resolve this issue:
If you must use tables with Binary, Image, Timestamp or Varbinary columns as the primary key, use SqlMetal.exe to create the .dbml file and generate the LINQ to SQL code.
"Using a Web site or Web application over a Remote Desktop as non-Admin automatically enables NTLM authentication. Therefore, when an ASMX or WCF service is consumed, the following error occurs: "The HTTP request is unauthorized with client authentication scheme 'Anonymous'. The authentication header received from the server was 'NTLM'."
To resolve this issue:
1. Open the property pages for the Websites
2. On the Start Options tab, clear NTLM Authentication
Note: This is only advised for Web sites that exclusively have WCF services. WCF services security is managed through the configuration in the web.config file. This makes NTLM Authentication unnecessary.
By default, a WCF proxy is generated in Visual Studio for Web Services for projects that target .NET Framework 3.0 or 3.5. If you attempt to call an ASMX WebService method that returns a typed datatype, an error will result.
To resolve this issue:
Add a Web Reference that generates an ASMX proxy instead of a Service Reference that generates a WCF proxy. To do this on new projects that target .NET Framework 3.0 or 3.5, use the Add Service Reference command, on the Project menu or on the project shortcut menu. In the Add Service Reference dialog box, click Advanced and then click Add Web Reference, and then add the Web Reference.
If the queries in a transaction scope take too long to finish and the transaction scope times out, the data is partially committed to the database. Any data committed to the database before the transaction scope timeout is rolled back, and the data committed to the database after the transaction scope timeout is committed to the database.
To resolve this issue:
To avoid such a situation, increase the time-out value.
SQL Server Compact 3.5 database files can only be encrypted while the database file is being created or while a SQL Server 2005 Compact Edition or SQL Server 2005 Mobile Edition database (.sdf) file is being upgraded to SQL Server Compact 3.5. After a SQL Server Compact 3.5 database file has been created, or upgraded from an earlier version, the encryption mode (Platform Default, Engine Default, PPC2003 Compatibility) cannot be changed, and an unencrypted database file cannot be encrypted. The Encryption Mode token in SqlCeConnectionString will be ignored when an existing SQL Server Compact 3.5 database is opened. The Encrypt token is not used in SqlCeConnectionString. The token is retained in SQL Server Compact 3.5 for backward compatibility. The token should not be used, and it will be deprecated in the future.
To resolve this issue:
To change the encryption mode of an existing SQL Server Compact 3.5 database or to encrypt an existing unencrypted SQL Server Compact 3.5 database, create a new SQL Server Compact 3.5 database and then copy the schema and data to the new database.
The Visual Basic, Visual C# and Visual C++ samples are available for download. To access them, on the Help menu, click Samples.
To resolve this issue:
None
There are no known issues.
2.3.3.1 Visual Studio crashes when C# IDE features are invoked on explicit interface members defined in referenced project
Visual Studio will crash when invoking C# IDE features such as IntelliSense or Quick Info tooltips on explicit interface members defined in a referenced project. A simple example is as follows:
1. Create a new Project named ProjectA
2. Inside ProjectA, add a new file with the following content:
public interface Interface {
void Method();
}
public class ImplClass : Interface {
void Interface.Method() { }
}
3. Create a second Project called ProjectB, that references ProjectA
4. Add a file with the following content:
class Program {
static void Repro() {
new ImplClass().Method();
}
}
5. Visual Studio will crash when you hover over the "Method" token in the file you just created.
To resolve this issue:
No workaround is available.
There are no known issues.
If you add a previously created .dbml file to a project by using the Add Existing Item dialog box and the connection string referenced in the .dbml file is not found in the Application Settings of the project, a warning is displayed and asks whether the connection string should be added to the Application Settings automatically. Answering "Yes" to this warning will update the .dbml file and the Application Settings accordingly. However, this leaves the generated code in an incomplete state with the DataContext's default constructor missing, and code will not be regenerated until a Save or Save All command is issued.
To resolve this issue:
After choosing Yes in the warning, click either Save or Save All to initiate code generation.
When a Web project is run on Windows Vista, it may fail to start and the following error may be shown: "Unable to start debugging on the web server. Strong name validation failed. Click Help for more information."
To resolve this issue:
Disable strong name validation for a Visual Studio file (iisresolver.dll) by doing the following:
1. Click on Start, All Programs,
Accessories, Command Prompt, and then select Run as administrator
2. You may see the screen grey and a 'User Account Control' dialog box appear. If
this happens, click Continue so that the command prompt starts.
3. Obtain a copy of sn.exe. Sn.exe
installed with Visual Studio 2005, and the .NET Framework 2.0 SDK, and therefore
it may already be on the computer. If it is not on the computer, then download .NET
Framework 2.0 SDK to obtain it. The x86 version of the Software development kit can be downloaded from
http://www.microsoft.com/downloads/details.aspx?FamilyID=FE6F2099-B7B4-4F47-A244-C96D69C35DEC. The x64 version of the SDK can be
downloaded from
http://www.microsoft.com/downloads/details.aspx?FamilyId=1AEF6FCE-6E06-4B66-AFE4-9AAD3C835D3D.
4. Run one of the following commands, as appropriate:
32-bit computer:
"<path_to_sn>\sn.exe" -Vr "%ProgramFiles%\Microsoft Visual Studio 9.0\Common7\IDE\iisresolver.dll"
64-bit computer:
"<path_to_sn>\sn.exe" -Vr "%ProgramFiles(x86)%\Microsoft Visual Studio 9.0\Common7\IDE\iisresolver.dll"
This assumes that Visual Studio was installed to the default location. If Visual Studio was installed to a custom location, then '%ProgramFiles%\Microsoft Visual Studio 9.0' should be replaced with the path where Visual Studio was installed.
© 2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks | Privacy Statement