MS Visual Studio 2008 Team Suite

Год выпуска: 2008
Разработчик: Microsoft
Платформа: x86, x64
Совместимость с Vista: полная
Системные требования:

Minimum: 1.6 GHz CPU, 384 MB RAM, 1024x768 display, 5400 RPM hard disk
Recommended: 2.2 GHz or higher CPU, 1024 MB or more RAM, 1280x1024 display, 7200 RPM or higher hard disk
On Windows Vista: 2.4 GHz CPU, 768 MB RAM

Язык интерфейса: только английский
Таблэтка: Не требуется
Описание:
Новая среда разработки на языках C++, C#, Basic и не только...
Для установки требуется Windows Installer 3.1.
Доп. информация: MSDN внутри Wink



===================================
Visual Studio 2008 Readme
Цитата:

To view the most up-to-date version of the Visual Studio 2008 Readme, click here. Table of Contents 1. System Requirements 1.1. Supported Architectures 1.2. Supported Operating Systems 1.3. Hardware Requirements 2. Known Issues 2.1. Installing 2.2. Uninstalling 2.2.1. On computers that have earlier versions of Visual Studio 2.2.2. On computers that do not have earlier versions of Visual Studio 2.3. Product Issues 2.3.1. General Issues 2.3.2. ADO.NET 2.3.3. Languages 2.3.4. LINQ 2.3.5. Visual Studio Tools for Office 2.3.6. Web Development 2.3.7. Windows Communication Foundation (WCF) Tools 2.3.8. Windows Presentation Foundation (WPF) Designer for Visual Studio 2.3.9. Windows Workflow Foundation (WF) Tools 2.3.10. Windows SDK Integration 3. Related Links 1. System Requirements 1.1. Supported Architectures x86 x64 (WOW) 1.2. Supported Operating Systems Microsoft Windows XP Microsoft Windows Server 2003 Windows Vista 1.3. Hardware Requirements Minimum: 1.6 GHz CPU, 384 MB RAM, 1024x768 display, 5400 RPM hard disk Recommended: 2.2 GHz or higher CPU, 1024 MB or more RAM, 1280x1024 display, 7200 RPM or higher hard disk On Windows Vista: 2.4 GHz CPU, 768 MB RAM 2. Known Issues 2.1. Installing 2.1.1. Visual Studio SharePoint workflow features have specific installation requirements. To use the SharePoint workflow development tools in Visual Studio Tools for Office, complete the following installation steps in the specified order. 1. Install Windows Server 2003. 2. Install Internet Information Services (IIS). In Control Panel, select Add/Remove Windows components, then Application Server, then Details, then Internet Information Services (IIS). 3. Install .NET Framework 2.0 and .NET Framework 3.0. 4. In IIS Manager, enable ASP.NET 2.0.5727. 5. Install Microsoft Office SharePoint Server 2007. Make sure to run the configuration wizard. 6. Install Visual Studio 2008. Use the default installation or make sure that Visual Studio Tools for Office is selected on the Custom installation page of the Setup wizard. 7. (Optional) SMTP Service. Installing this service lets you use SharePoint email-enabled features. Consult the SharePoint product documentation to learn more about these capabilities. To resolve this issue: No workaround is available. 2.1.2. Upgrading to the release version of SQL Server Compact 3.5 from SQL Server Compact 3.5 CTP or SQL Server Compact 3.5 Beta is not supported. Upgrading from the CTP and Beta versions of SQL Server Compact 3.5 to the release version is not supported. To resolve this issue: Before you install the release version of either SQL Server Compact 3.5 or Visual Studio 2008, uninstall all CTP and Beta versions of SQL Server Compact 3.5, SQL Server Compact 3.5 for Devices, and SQL Server Compact 3.5 Design Tools 2.1.3. Users get the error message, "A problem has been encountered while loading the setup components. Canceling setup". Users get the error 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. Users should install Windows Installer 3.1 and then retry Setup. To resolve this issue: 1. In Add or Remove Programs, look for Windows Installer 3.1 in the list of installed programs. 2. If Windows Installer 3.1 is not present, complete the following steps. a. Go to Windows Installer 3.1 Redistributable (v2) and then install Windows Installer 3.1. b. Retry Visual Studio 2008 Setup. 2.1.4. Setup stops and displays an 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". Setup stops and displays an 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 message indicates that a setup program other than Visual Studio 2008 Setup might already be running on the computer. After the other setup is finished, restart the computer and then run Visual Studio 2008 Setup. - This message might also indicate that Windows updates are being installed on the computer. After Windows Update is finished, restart the computer and then run Visual Studio 2008 Setup. - Look for msiexec.exe in Task Manager. If msiexec.exe is already running, wait for it to finish and then restart the computer and run Visual Studio 2008 Setup. - If none of these options apply to your problem, restart your computer and then run Visual Studio 2008 Setup. 2.1.5. Installing Visual Studio 2008 on a computer that has Visual Studio 2005 causes Visual Studio 2005 repair of .NET Framework 2.0 to fail. When Visual Studio 2008 is installed on the same computer as Visual Studio 2005, Visual Studio 2005 repair fails to repair the .NET Framework 2.0. To resolve this issue: Repair .NET Framework 2.0 separately by using Add or Remove Programs. 2.1.6. Visual Studio 2008 Setup may display a message that prompts you to close running applications. Visual Studio 2008 Setup may display a message that prompts you to close running applications. In the message, some of the applications may have a numeric process identifier and some may have an empty identifier. Names of applications are not shown. To resolve this issue: We recommend that you close the applications so that they do not affect the installation process. You can find the names of the applications by looking up their Process IDs in Task Manager. 1. Press CTRL+ALT+DEL and then click Task Manager. 2. On the View menu, click Select Columns. 3. Select PID (Process Identifier) and then click OK. 4. In Task Manager, click PID to sort entries by PID. 5. Look for the Process IDs that are shown in the message. You may also click Ignore in the message box and then continue with the installation. Doing this may require a reboot at the end of Setup. 2.2 Uninstalling 2.2.1. On computers that have earlier versions of Visual Studio 2.2.1.1. Uninstalling the Windows SDK can affect Visual Studio 2008. If you install either the Windows SDK for Windows Vista or the Windows SDK Update for Windows Vista together with Visual Studio 2008, and then uninstall the Windows SDK, the registry keys that Visual Studio requires to find Windows headers, libraries, and tools are removed. To resolve this issue: Do one of the following things: - Repair Visual Studio 2008 by using Add or Remove Programs (Windows Server 2003 and Windows XP) or by using Programs and Features (Windows Vista and Windows Server 2008). - Install the Windows SDK for Windows Server 2008 and .NET Framework 3.5. 2.2.1.2. Uninstalling Visual Studio 2005 clears the registry entries that are required by the Load Agent. If you install Visual Studio 2008 Team Test Load Agent on a computer that has Visual Studio 2005 Team System Edition for Testers or Visual Studio 2005 Team Suite Edition, and then uninstall Visual Studio 2005, the uninstallation will clear the following registry entries that are required for load generation. [HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpipParameters] "MaxUserPort"=dword:0000FFFE "TcpTimedWaitDelay"=dword:0000001e To resolve this issue: After you uninstall Visual Studio 2005, put these entries back in the registry. 2.2.2. On computers that do not have earlier versions of Visual Studio 2.2.2.1. After one version of Visual Studio is uninstalled in a side-by-side configuration, Workflow debugging is no longer available. If two versions of Visual Studio 2008 are installed on a computer (for example, the English and Japanese versions) and then one is uninstalled, you can no longer debug workflows in the remaining version. WDE.dll, which is part of the Workflow debugger, is uninstalled when either one of the installations is removed from the computer. To resolve this issue: In Visual Studio 2008 Setup, repair or reinstall the remaining Visual Studio version. 2.2.2.2. Visual Studio 2008 Setup may display a message that prompts you to close running applications. Visual Studio 2008 Setup may display a message that prompts you to close running applications. In the message, some of the applications may have a numeric process identifier and some may have an empty identifier. Names of applications are not shown. To resolve this issue: We recommend that you close the applications so that they do not affect the installation process. You can find the names of the applications by looking up their Process IDs in Task Manager. 1. Press CTRL+ALT+DEL and then click Task Manager. 2. On the View menu, click Select Columns. 3. Select PID (Process Identifier) and then click OK. 4. In Task Manager, click PID to sort entries by PID. 5. Look for the Process IDs that are shown in the message. You may also click Ignore in the message box and then continue with the installation. Doing this may require a reboot at the end of Setup. 2.3. Product Issues 2.3.1. General Issues 2.3.1.1. Running a custom installation of the Windows SDK may change file link paths to point to non-existent files. Running a custom installation of the Windows SDK may change file link paths to point to non-existent files. If Visual Studio 2008 is installed and then the Windows SDK is installed, an important registry key is changed. That key points to the SDK tools as well as the Windows headers and libraries. However, if you run a custom installation of the Windows SDK that does not include tools or headers and libraries, the link to those files is broken and some Visual Studio functionality will be broken. To resolve this issue: Either repair Visual Studio 2008 or use the Windows SDK Configuration Tool, which is installed with the Windows SDK for Windows Server 2008 and .NET Framework 3.5. 2.3.1.2. Windows Workflow debugging with T-SQL is not supported. If you debug your workflow with both the workflow debugging and T-SQL debugging enabled, unexpected results could occur. To resolve this issue: No workaround is available. 2.3.1.3. Locals window does not work on the 64-bit version of Windows Vista. The Locals window is not visible when Visual Studio is running on the 64-bit version of Windows Vista. To resolve this issue: No workaround is available. 2.3.1.4. Adding a new database unit test to a workflow project displays an error. Adding a new database unit test to a workflow project displays the following message. "An error occurred while loading the workflow. Please correct the following error and try reloading the document to view the workflow. The designer could not be shown for this file because none of the classes within it can be designed. The designer inspected the following classes in the file: DatabaseUnitTest1. The base clase DatabaseUnitTest1 for the class needs to be an Activity." This message is displayed incorrectly. The new database unit test is actually valid. You can dismiss the message, and it will not reappear. To resolve this issue: Close the error. It will not reappear. 2.3.1.5. Visual Basic Workflow designer requires Visual Web Developer to be installed. After Visual Studio 2008 is installed in Visual Basic-only mode, the Workflow Foundation designer does not work correctly. You cannot specify the required fields in Workflow projects, and that makes it impossible to build the solution. To resolve this issue: Install Visual Web Developer by using Visual Studio 2008 Setup. 2.3.1.6. Visual Studio 2008 projects cannot build in Expression Blend. Solutions and projects that are created in Visual Studio 2008 can be opened and edited in Expression Blend, but they cannot be built there. Also, when you open Expression Blend projects in Visual Studio 2008, they will be upgraded to the Visual Studio 2008 format. After the project is upgraded, it can no longer be built in Expression Blend; however, you can still open it and edit it in Expression Blend. To resolve this issue: For more information about availability and for installation instructions, visit here or the Microsoft Expression Web site. 2.3.1.7. Visual Studio 2008 does not recognize Windows Mobile 6 SDK when the SDK is already installed. If a user installs Visual Studio 2008 on a computer that already has Windows Mobile 6 SDK, Visual Studio 2008 will not recognize the SDK. Repairing Windows Mobile 6 SDK will not solve this. To resolve this issue: 1. Uninstall Windows Mobile 6 SDK. 2. Reinstall Windows Mobile 6 SDK. 2.3.1.8 SQL Server Compact 3.5 does not use the Encrypt property of the SqlCeConnection class. The Encrypt property in the SqlCeConnection class should not be used. The property is retained in SQL Server Compact 3.5 only for backward compatibility. To resolve this issue: Use the encryption mode property of the SqlCeConnection class to encrypt SQL Server Compact 3.5 database files. Uses of encryption mode, together with code samples, are as follows. 1. To create a new encrypted SQL Server Compact 3.5 database. SqlCeEngine engine = new SqlCeEngine("Data Source=Northwind.sdf;encryption mode=platform default;Password=passw0rd;"); engine.CreateDatabase(); 2. To upgrade a SQL Server 2005 Compact Edition (version 3.1) or SQL Server 2005 Mobile Edition (version 3.0) database to an encrypted SQL Server Compact 3.5 database. SqlCeEngine engine = new SqlCeEngine("Data Source=Northwind.sdf;Password=passw0rd;"); engine.Upgrade ("Data Source=Northwind.sdf;encryption mode=platform default;Password=passw0rd;"); 3. To change the encryption mode of an existing SQL Server Compact 3.5 database. SqlCeEngine engine = new SqlCeEngine("Data Source=Northwind.sdf;Password=passw0rd;"); engine.Compact("Data Source=Northwind.sdf;encryption mode=ppc2003 compatibility;Password=passw0rd;"); 4. To encrypt an unencrypted SQL Server Compact 3.5 database. SqlCeEngine engine = new SqlCeEngine("Data Source=Northwind.sdf"); engine.Compact("Data Source=Northwind.sdf;encryption mode=platform default;Password=passw0rd;"); 2.3.1.9. Design-time experience in Smart Device programs cannot be used when SSC 3.1 database is targeted. A Smart Device programmer is unable to use any of the designer features, such as Add Datasource, Add New Connection, Create Database, Generate Data Forms, and drag-and-drop datasource objects onto the form designer, when she is programming against a SQL Server Compact Edition 3.1 database. The Smart device designer features default to SQL Server Compact 3.5 database. To resolve this issue: Use Visual Studio 2005 Service Pack 1 to program against SQL Server Compact Edition 3.1 database for Smart Device programs. For more information about using Visual Studio 2008 with SQL Server Compact Edition 3.1 database, see http://go.microsoft.com/fwlink/?LinkID=101885. 2.3.1.10. During the upgrade of a Visual Studio 2005 project to Visual Studio 2008, the encrypted SQL Server Compact database is not upgraded, and ClickOnce applications must be re-published. Database files (*.sdf) that are created by earlier version of SQL Server Compact are not compatible with SQL Server Compact 3.5. Un-encrypted database files from earlier versions of SQL Server Compact are upgraded when a Visual Studio 2005 project is upgraded in Visual Studio 2008. Encrypted database files must be manually upgraded. If the Visual Studio 2005 project uses ClickOnce to publish applications, the application should be re-published after the project has been upgraded in Visual Studio 2008. To resolve this issue: Upgrade the encrypted database files by completing the following steps. 1. Click Data. 2. Click Add New Data Source. 3. Click Add Connection. If an earlier version of the database file is open, a message appears. If you click OK, the Upgrade to SQL Server Compact 3.5 Database dialog box appears. Alternatively the SqlCeEngine.Upgrade API can be used for programmatic scenarios, as shown in the following code example. SqlCeEngine engine = new SqlCeEngine("Data Source=Northwind.sdf;Password=passw0rd;"); engine.Upgrade ("Data Source=Northwind.sdf;encryption mode=platform default;Password=passw0rd;"); If the project uses ClickOnce to publish applications, the application should be re-published after it has been upgraded in Visual Studio 2008. When you re-publish the Click Once application in Visual Studio 2008, you may see a warning that SQL Server 2005 Compact Edition prerequisite cannot be found for bootstrapping. You can ignore the warning. 2.3.1.11. SQL Server Compact 3.5 data types for parameters such as SqlDbType or DbType should be explicitly set. If the data types for parameters such as SqlDbType or DbType are not explicitly set, an exception will be thrown. To resolve this issue: Explicitly set the data type for parameters such as SqlDbType or DbType. Doing this is critical in case of BLOB data types (image and ntext). A code example follows. SqlCeEngine engine = new SqlCeEngine(connString); engine.CreateDatabase(); engine.Dispose(); SqlCeConnection conn = new SqlCeConnection(connString); conn.Open(); SqlCeCommand cmd = conn.CreateCommand(); cmd.CommandText = "CREATE TABLE BlobTable(name nvarchar(128), blob ntext);"; cmd.ExecuteNonQuery(); cmd.CommandText = "INSERT INTO BlobTable(name, blob) VALUES (@name, @blob);"; SqlCeParameter paramName = cmd.Parameters.Add("name", SqlDbType.NVarChar, 128); SqlCeParameter paramBlob = cmd.Parameters.Add("blob", SqlDbType.NText); paramName.Value = "Name1"; paramBlob.Value = "Name1".PadLeft(4001); cmd.ExecuteNonQuery(); 2.3.2. ADO.NET 2.3.2.1. After Visual Studio 2008 is upgraded, a warning is displayed that a MDAC 2.8 prerequisite is missing or that a built application does not run on Windows 2000 after it is installed. You may encounter one of the following problems: - A Visual Studio 2005 project was upgraded to Visual Studio 2008, and now a build warning says that a prerequisite is missing. - A built application that depends on MDAC does not run on Windows 2000. - Windows 2000 users cannot run a ClickOnce application because MDAC is missing. To resolve this issue: - If you do not require MDAC and you are getting a build warning, open the Prerequisites dialog box and then clear the MDAC prerequisite. - If you are targeting Windows 2000 clients and require the MDAC prerequisite, get the Bootstrapper package from the Internet, as follows. 1. Open the Prerequisites dialog box and then click 'Check Microsoft Update for more redistributable components'. Doing this will open http://go.microsoft.com/fwlink/?linkid=40981. 2. On the Web page, download the MDAC Bootstrapper package and save it in a new folder in Program FilesMicrosoft SDKsWindowsv6.0ABootstrapperPackages. - Get the Bootstrapper package from Visual Studio 2005. 1. If Visual Studio 2005 is installed on the same computer, you can copy the MDAC28 folder in Program Files Microsoft Visual Studio 8SDKv2.0BootStrapperPackages and then paste it in Program FilesMicrosoft SDKsWindowsv6.0ABootstrapperPackages. 2.3.3. Languages There are no known issues. 2.3.4. LINQ 2.3.4.1. Object Relational (O/R) Designer displays the message, “There is no Unicode byte order mark. Cannot switch to Unicode”, when a .dbml file that was created by using Visual Studio 2008 Beta 2 is opened. In Visual Studio 2008 Beta 2, the O/R Designer created .dbml files as UTF-8 byte-order even if UTF-16 encoding was specified in the actual file. Opening .dbml files created by using Beta 2 could raise the “There is no Unicode byte order mark. Cannot switch to Unicode” error. To resolve this issue: Right-click the .dbml file in Solution Explorer, open by using the XML Editor, and then save the file. Doing this does not impact the actual content of the .dbml file and there is no data loss. 2.3.5. Visual Studio Tools for Office 2.3.5.1. Office 2007 Service Pack 1 is required to preview Office InfoPath 2007 form templates. Previewing Office InfoPath 2007 form templates in Visual Studio 2008 by pressing F5 or clicking the Preview button will fail and display an error, unless InfoPath 2007 Service Pack 1 or the QFE is installed. To resolve this issue: The QFE is available at http://go.microsoft.com/fwlink/?LinkId=102084. 2.3.5.2. Using Office SharePoint workflow templates on a 64-bit operating system is unsupported and causes an exception. Visual Studio 2008 throws two exceptions if you try to create a SharePoint workflow project (SharePoint 2007 Sequential Workflow or SharePoint 2007 State Machine Workflow) on a 64-bit computer. The first exception message is "Object reference not set to an instance of an object". The second message is "SharePoint site location entered is not valid. The SharePoint site at http:// could not be found. Verify that you have typed the URL correctly…" To resolve this issue: Do not use the Visual Studio SharePoint workflow templates on a computer that is running a 64-bit operating system. For more information, see the Help topic, "Troubleshooting SharePoint Workflow Solutions". 2.3.5.3. Migrating Visual Studio Tools for Office (VSTO) projects from Visual Studio 2008 Beta 2 to the final version of Visual Studio 2008 You may experience build and runtime errors when building and running Beta 2 Office projects in the final release version of Visual Studio. Changes have been made to a number of VSTO reference assemblies. To resolve this issue: Renamed Assemblies: If you receive an error for any of the following reference assemblies, delete the old reference assembly and add the corresponding new reference assembly to your project and then rebuild. Old Reference New Reference Microsoft.VisualStudio.Tools.Applications.ServerDocument.dll Microsoft.VisualStudio.Tools.Applications.ServerDocument.v9.0.dll Microsoft.VisualStudio.Tools.Office.dll Microsoft.Office.Tools.v9.0.dll Microsoft.VisualStudio.Tools.Office.Common.dll Microsoft.Office.Tools.Common.v9.0.dll Microsoft.VisualStudio.Tools.Office.Excel.dll Microsoft.Office.Tools.Excel.v9.0.dll Microsoft.VisualStudio.Tools.Office.Outlook.dll Microsoft.Office.Tools.Outlook.v9.0.dll Microsoft.VisualStudio.Tools.Office.Word.dll Microsoft.Office.Tools.Word.v9.0.dll 2.3.6. Web Development There are no known issues. 2.3.7. Windows Communication Foundation (WCF) Tools 2.3.7.1. WcfTestClient may throw an exception if Biztalk Service SDK is installed. The Biztalk Service SDK introduces a metadata exchange (MEX) endpoint in the section of the element in the machine.config file. This setting generates the following exception when the service is invoked in WcfTestClient: System.NullReferenceException: Object reference not set to an instance of an object To resolve this issue: When you run the WcfTestClient, modify the machine.config file (located in WINDOWSMicrosoft.NETFrameworkv2.0.50727CONFIG),by commenting out the section that is nested in the element. Re-enable the section when you use the Biztalk service SDK. 2.3.7.2. Setupvroot.bat setup script for WCF samples can fail on Windows Vista. On Windows Vista, if the NetMsmqActivator service is enabled and Message Queuing (MSMQ) is not installed, then the iisreset utility does not work and the WCF samples setup script Setupvroot.bat will not run. To resolve this issue: Make sure that MSMQ is installed, or disable the NetMsmqActivator service on Windows Vista before you run the WCF samples setup script, Setupvroot.bat. 2.3.7.3. WcfTestClient does not support some features of WCF. The following features of WCF are not supported by the WcfTestClient in this release: - Message contract and XML serialization, non-WCF Web services - Session/Context binding - Transaction - Duplex contract - Windows CardSpace, Certificate, User name/Password, Windows Authentication - Types: Stream, IDictionary collection, and DataSet To resolve this issue: No workaround is available. 2.3.7.4. Service Model Metadata Utility tool (SvcUtil.exe) cannot generate data contracts from a running service. An example at the end of the Svcutil.exe help output indicates that you can use the /dataContractOnly (/dconly) option to generate data contracts from a running service. svcutil.exe /dconly http://service/metadataEndpoint - Generate Data Contract types from a running service or online metadata documents. This usage does not work. You can only use the /dconly option to generate data contracts from local metadata files. To resolve this issue: 1. Download the metadata from the running service by running the following command. svcutil.exe /target:metadata http://service/metadataEndpoint 2. Run Svcutil.exe with the /dconly option on the downloaded metadata files, as follows. svcutil.exe /dconly *.wsdl *.xsd 2.3.7.5. Code generation language support in the Service Model Metadata Utility tool (Svcutil.exe). The Svcutil.exe tool can generate code for Web service clients and data types, from metadata in any language that has a managed code provider. Svcutil.exe has been tested with the C#, Visual Basic, and C++ managed code providers. Other code providers have not been tested and may generate code that does not compile or may be otherwise unusable. To resolve this issue: Use one of the supported managed code providers, or manually edit the generated code to resolve any compilation issues. 2.3.7.6. Managed C++ code that is generated by using the Service Model Metadata Utility tool (Svcutil.exe) may not compile. You can use the Svcutil.exe tool to generate code for Web service clients and data types, from metadata. However, there are known issues with the C++ code provider in Visual Studio 2008 that can cause Svcutil.exe to generate Managed C++ code that may not compile. To resolve this issue: Manually alter the generated code to resolve any compiler errors. 2.3.8. Windows Presentation Foundation (WPF) Designer for Visual Studio 2.3.8.1. Property browser displays values, such as dates and numbers, by using the U.S. format. The property browser in the WPF designer displays and edits values by using the U.S. format. This matches the XAML convention of using the en-US CultureInfo. For example, dates and numbers are always in U.S. format. Dates are always displayed mm/dd/yy. If you enter a date value in the property browser. it will be converted with the assumption that it is in mm/dd/yy format. To resolve this issue: No workaround is available. 2.3.8.2. Code Refactoring does not make changes to XAML files. If you use code refactor to make type or member modifications, the refactoring will not propagate to the XAML files. For example, given a UserControl named MyCustomControl, if you use refactor to change the name of that UserControl to FancyControl in the code file, that name change will only affect code files and any instances of MyCustomControl in XAML files will not be updated.Additionally, the build may incorrectly succeed without error until a rebuild or clean of the project or solution is performed. To resolve this issue: There is no direct resolution. You must make the modifications by using Find and Replace. 2.3.8.3. Making changes to XAML will not refactor code files. If you make changes to a type or member in a XAML file, those changes will not propagate to the code files. For example, if you change the name of Button that has event handlers associated with it by using the XAML editor, the code behind will not be updated. To resolve this issue: There is no direct resolution. You must make the modifications by using Find and Replace. 2.3.8.4. Renaming from Solution Explorer does not prompt rename refactoring in WPF projects. If you right-click a XAML file in Solution Explorer and then click Rename, the file name will be changed but there will not be any prompt to refactor the class name in XAML or code-behind. In particular, if you rename the XAML file that is referred to by the StartupUri property in the Application XAML file, for example, rename Window1.xaml to MainWindow.xaml, then you must manually change the StartupUri property. To resolve this issue: There is no direct resolution. You must make the modifications by using Find and Replace. 2.3.9. Windows Workflow Foundation (WF) Tools 2.3.9.1. Custom activities do not appear in the Visual Studio 2008 toolbox when you use Visual C++ Development settings. Custom activities do not appear in the Visual Studio 2008 toolbox when you use Visual C++ Development settings. To resolve this issue: Use different development settings, for example, Visual Basic or C#. 2.3.10. Windows SDK Integration There are no known issues. 3. Related Links 3.1. Visual Studio Team Foundation Server Readme: http://go.microsoft.com/fwlink/?LinkId=102510 3.2. Visual Studio Express Edition Readme: http://go.microsoft.com/fwlink/?LinkId=102509 3.3. .NET Framework Readme:http://go.microsoft.com/fwlink/?LinkId=1102511 3.4. MSDN Library for Visual Studio Readme: http://go.microsoft.com/fwlink/?LinkId=102512 3.5. Download SQL Server Compact 3.5 Books Online and Samples from http://go.microsoft.com/fwlink/?LinkID=96191 and Synchronization Services for ADO.NET v1.0 Books Online and Samples from http://go.microsoft.com/fwlink/?LinkId=80742. To add these to the Visual Studio Combined Help Collection, complete the following steps. 1. Click Start, point to All Programs, Microsoft Visual Studio 2008, and then click Microsoft Visual Studio 2008 Documentation. 2. In the Visual Studio Combined Help Collection, click Help and then click Index. 3. In the Look for box, enter collection manager, and then click the Help entry under collection manager in the Index. 4. In the Combined Help Collection Manager topic, select SQL Server Compact 3.5, and then click Update VSCC. 5. In the two dialog boxes that appear, read the requirements, and then click OK. 6. Close and then reopen the Visual Studio Combined Help Collection. SQL Server Compact Books Online is now available in the Table of Contents, Index, Search, and F1 Help. 3.6. For the latest information about issues with using the WPF designer in Visual Studio 2008, see the Cider wiki on Channel9, http://go.microsoft.com/fwlink/?LinkId=83541. 3.7. Visual J# MSDN developer center:http://go.microsoft.com/fwlink/?LinkId=102513 3.8. The XML to Schema tool can be downloaded from http://go.microsoft.com/fwlink/?LinkId=102514 The XML to Schema tool is a free project-item template that automates the creation of XML schema sets from any number of XML documents. If you are working with LINQ to XML in Visual Basic 2008, this utility may significantly improve your editing experience by adding XML schemas (.xsd files) to your project that then provide IntelliSense for XML properties. The tool can also be used to create an XML schema set from a set of existing XML documents. © 2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks | Privacy Statement