This document lists known issues with the installation, uninstallation, and features of Visual Studio Codename "Orcas" Beta 1 (referred to as "Orcas" in this readme).
System Requirements
Supported Languages: Visual Studio codename “Orcas” is available in the following languages: English (United States) and Japanese
Supported Operating Systems: Microsoft Windows XP Professional x64 Edition (WOW), Microsoft Windows XP Professional SP2, Microsoft Windows XP Home Edition SP2, Microsoft Windows XP Media Center Edition 2002 SP2, Microsoft Windows XP Media Center Edition 2004 SP2, Microsoft Windows XP Media Center Edition 2005, Microsoft Windows XP Tablet PC Edition SP2, Microsoft Windows Server 2003, Standard Edition SP1, Microsoft Windows Server 2003, Enterprise Edition SP1, Microsoft Windows Server 2003, Datacenter Edition SP1, Microsoft Windows Server 2003, Web Edition SP1, Microsoft Windows Server 2003, Standard x64 Edition SP1 (WOW), Microsoft Windows Server 2003, Enterprise x64 Edition SP1 (WOW), Microsoft Windows Server 2003, Datacenter x64 Edition SP1 (WOW), Microsoft Windows Server 2003 R2, Standard Edition, Microsoft Windows Server 2003 R2, Standard x64 Edition (WOW), Microsoft Windows Server 2003 R2, Enterprise Edition, Microsoft Windows Server 2003 R2, Enterprise x64 Edition (WOW), Microsoft Windows Server 2003 R2, Datacenter Edition Microsoft Windows Server 2003 R2, Datacenter x64 Edition (WOW), Microsoft Windows Vista
Note: IA64 is not supported.
Installation Requirements:
Minimum: 1.6+ GHz CPU, 384+ MB RAM, 1024x768 Display, 5400 RPM HD. Recommended: 2.2+ GHZ CPU, 1024+ MB RAM, 1280x1024 Display, 7200 RPM HD.
For Vista: 2.4 GHz CPU, 768 MB RAM
If you have installed an earlier version of Orcas, such as a Community Technical Preview (CTP), then you must uninstall it in the following order:
If you uninstall Visual Studio from Add or Remove programs, all prerelease components will be chain uninstalled with the product. This allows the user to uninstall an older release of Orcas then install a newer release of Orcas without manually uninstalling the product.
Note: If two or more Orcas products are installed on the same computer and one of them is uninstalled, this will break the remaining products. The chained uninstall of any pre-release version of Orcas will chain uninstall applications that are shared across the products. To fix any remaining product, run repair on it and the chain uninstalled applications will be reinstalled.
When installing VS Orcas as a non-administrator on a Vista box, setup shows an error box stating that "Setup discovered the following problem: You must have administrative privileges to run Visual Studio Codename Orcas. Please contact your system administrator."
To resolve this issue:
To fix this issue, right click setup.exe and select "Run as administrator". This will prompt the user for the appropriate credentials and continue.
1.1.3. Visual Studio Setup will not resume after a reboot on Vista
During Visual Studio Setup on Vista there is a required reboot to apply an update to the OS. 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.
The installation of Orcas JPN on an English version of Windows XP will fail if East Asian Fonts have not been installed. This happens because the Visual Web Tools have a dependency on matching language fonts. If fonts are not found, the Visual Web Tools component will fail to install.
To resolve this issue:
You must install the East Asian Language Support before you install Orcas JPN on an English version of Windows XP. To install East Asian Language support, open the Regional and Language Options dialog box in the Control Panel. Click the Languages Tab, and then select "Install files for East Asian languages". Click OK to install and close the dialog box.
If Orcas is installed on a computer that has Visual Studio 2005, Windows Mobile 5.0/6, and Windows CE SDKs installed, Orcas will not automatically recognize the SDKs until they are repaired.
To resolve this issue:
Use Add or Remove Programs to repair the SDKs.
If Orcas is uninstalled, then all SSCE MSIs will be also uninstalled. This can create problems if two Orcas products are installed side-by-side on the same computer (for example, Orcas Standard and Orcas C# Express). If one of the Orcas products is uninstalled, it will uninstall all the SQL Server Compact Edition 3.5 MSIs and the other Orcas product will not function properly.
To resolve this issue:
To reinstall the SQL Server Compact Edition 3.5 MSIs, run the Orcas product installation in repair mode.
To use the SharePoint Workflow Tools in this release, you must install the following products and components in the order listed as follows:
During setup of VSTS, when the installation of SQL Server Express is finished, your are prompted to reboot. If you select Restart Later, the installation stops and nothing happens on reboot. The expected behavior is for setup to resume on reboot.
To resolve this issue:
If you selected Restart Now, the installation will continue after the computer reboots.
Orcas Beta 1 JPN cannot be installed on Windows Vista unless the Windows Vista JPN Langpack is installed first.
To resolve this issue:
Make sure that Windows Vista JPN Langpack is installed before you install Orcas Beta 1 JPN on Windows Vista.
1.1.10. Uninstalling Orcas CTP does not uninstall SQL Server Compact Edition 3.5
The SQL Server Compact Edition 3.5 MSIs are not uninstalled during the uninstallation of the Orcas CTP. The MSIs are SQL Server Compact Edition 3.5 Design Tools, SQL Server Compact Edition 3.5 For Devices, and SQL Server Compact Edition 3.5. If Orcas is installed at a later time on the same computer, the installation of the SQL Server Compact Edition 3.5 MSIs will be skipped.
To resolve this issue:
Uninstall the SQL Server Compact Edition 3.5 MSIs by using Add or Remove Programs.
1.1.11. OpenMP policy error
The OpenMP policy of Orcas Beta 1 points to an incorrect version.
To resolve this issue:
In the OpenMP policy file, remove the redirection or change the redirection value to something that exists on the computer. Use the following steps to change values:
1.1.12. Orcas Setup Will Fail if a pre-RTM Version of Office 2007 is Installed
When installing Orcas, if a user has a pre-RTM version of Office 2007 installed, setup will fail while installing the Viwual Web Tools component.
To resolve this issue:
Uninstall the pre-RTM version of Office 2007 and setup will work.
1.1.13. Installing Orcas on a Vista machine that has had previous versions of Orcas may fail
When installing Orcas on a Vista machine that has had previous versions of Orcas, setup fails during the installation of the .NET Framework 3.5 component.
To resolve this issue:
Open the Control Panel, select Programs & Features, click on the “View installed updates” located on 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)
1.1.14. Initial Orcas setup dialog on a Vista machine may temporarily appear to be “Not Responding”
This issue can be safely ignored and setup will resume shortly.
1.1.15. Orcas install on Vista machine may bring up a dialog that prompts to close running applications
Installing Orcas on Vista may prompt to close running applications such as Machine Debug Manager.
To resolve this issue:
Select the Ignore button and continue with the installation. This may require a reboot at the end of setup.
1.1.16. Visual Studio Tools for Office (VSTO): Office 2007 PIAs installed by the Office 2007 PIA redistributable package are not recognized by this release
If you install Office 2007 before you install the .NET Framework, the required Office 2007 PIAs are not installed. If you try to create a VSTO project when the PIAs are not installed, you will get an error asking you to install the required Office 2007 PIAs. If you then install the Office 2007 PIAs by running the Office 2007 PIA redistributable package, the PIAs are installed but are not recognized by the VSTO projects and you will get an error saying the PIAs are missing, even though they are really installed.
To resolve this issue:
Restart Office2007 setup and then choose Add or Remove features. Select Custom installation and then add the .NET programmability support feature for all Office applications.
If you install Orcas on the same computer as Visual Studio 2005 and then uninstall Orcas, some Visual Studio 2005 features might stop working.
To resolve this issue:
Use Add or Remove Programs to repair Visual Studio 2005. For more information, click here.
An error appears if you install Orcas on the same computer as Visual Studio 2005, uninstall Orcas, and then try to create a database project. The error states that the SqlServer.targets file cannot be found and that the project could not be created.
To resolve this issue:
Use Add or Remove Programs to repair Visual Studio 2005.
If you install Orcas on a computer that has Visual Studio 2005 and then uninstall Orcas, .NET Compact Framework v2.0 and Device Emulator will also be uninstalled.
To resolve this issue:
Reinstall .NET Compact Framework v2.0 and Device Emulator.
Uninstalling Orcas on a computer that has Visual Studio 2005 installed will cause
C# refactoring and code generation features (for example, Implement Interface, Auto-event hookup, Generate Method Stub) to fail in Visual Studio 2005. The problem occurs
because the .NET 2.0 SDK is uninstalled and the following registry keys are removed:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\Setup\VS]
"VS7CommonBinDir"="D:\\Program Files\\Microsoft Visual Studio 8\\Common7\\Tools\\"
"ProductDir"="D:\\Program Files\\Microsoft Visual Studio 8\\"
To resolve this issue:
To restore refactoring and code generation features in Visual Studio 2005:
A repair of Visual Studio 2005 will also resolve this issue.
The .NET 3.5 Framework is removed on uninstallation of any Orcas product. This breaks any other installed Orcas product because all Orcas 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 Orcas product installer.
When Orcas is uninstalled on a computer that has both Visual Studio 2005 and Orcas, all scenarios that involve desktop-to-device connectivity will be broken. Examples include connect to device, native/managed project deployment, and debugging.
To resolve this issue:
After you uninstall Orcas, do the following:
The Inherited Form and Inherited User Control C# item templates are missing in the Add New Item dialog box.
To resolve this issue:
To create your own Inherited Form:
To create your own Inherited User Control:
ClickOnce requires that the manifest files for an Office 2007 add-in are signed at build time. When you create an Office 2007 add-in project, a temporary certificate is created, added to the project, and installed into your personal certificate store. When you attempt to build the project, if the project’s certificate cannot be found in the certificate store, the project cannot be built and you will receive build errors. This can happen if you remove the certificate from the store or if the project is copied to another development computer.
To resolve this issue:
Either reinstall the certificate in the personal certificate store or create a new certificate. For more information, see How to: Sign Application and Deployment Manifests.
Generating unit test code for non-public members and methods that have non-public parameters is not supported in this release of Orcas. This will be fixed in a later release.
To resolve this issue:
Use the PrivateType/PrivateObject classes in the Smart Device Unit Test Framework to access non-public members.
On some computers, when you try to start the profiler monitor by using vsperfcmd, it will fail with no indication of the problem.
To resolve this issue:
Open a profiling target in the Performance Explorer and then click Yes when asked to elevate your credentials.
Upgrade of an existing Visual Studio 2005 project that is based on NETCF2.0 and SQL Server 2005 Mobile Edition or SQL Server 2005 Compact Edition will not upgrade the SQL Server 2005 Mobile Edition /SQL Server 2005 Compact Edition version to SQL Server Compact Edition 3.5. The project will not compile if either SQL Server 2005 Mobile Edition or SQL Server 2005 Compact Edition is not already installed.
To resolve this issue:
Install SQL Server 2005 Mobile Edition /SQL Server 2005 Compact Edition or replace SQL Server 2005 Mobile Edition /SQL Server 2005 Compact Edition references in the project with SQL Server Compact Edition 3.5 references.
Visual Studio 2005 Smart Device Native IDE will show the Windows Mobile 5.0 PPC/SP platform name as "Windows Mobile 5.0 Pocket PC SDK 2" when Orcas, Visual Studio 2005, and Windows Mobile 5.0 PPC/SP SDK are installed on the same computer. An incorrect platform name can affect you in one of the following ways:
To resolve this issue:
When you use the ADO.NET Entity Framework, an entity's keys may be marked as server generated. This enables the database to generate a value for the key on an insert (entity creation). Additionally, zero or more properties of an entity may be marked as server generated values. A SQL Server Compact Edition database may generate default values for null-valued properties when an entity is created or updated, if a default value has been specified as part of the column definition.
This release of SQL Server Compact Edition, when it is used with the ADO.NET Entity Framework, does not support entities with server-generated keys or values, even though such entity types might be defined in the Model (.csdl) or Target (.ssdl) files.
LIMIT and TOP expressions are supported in Paging queries. Paging queries are intended to support stateless paging (scrolling or windowing) through the results of a query. Paging queries in the ADO.NET Entity Framework can be specified by using the LINQ Skip and Take operators. For example:
customers.OrderBy(c => c.Name).Skip(100).Take(20)
Paging queries can also be expressed by using the SKIP, LIMIT, and TOP constructs of Entity SQL. For example:
SELECT value c
FROM NW.Customers AS c
ORDER BY c.Name skip 100 limit 20;
This release of SQL Server Compact Edition, when it is used with the ADO.NET Entity Framework, does not support SKIP expressions in the paging queries. The LIMIT and TOP expressions are supported.
Entity SQL enables a COLLATE subclause to be specified as part of each key in an ORDER BY clause. The COLLATE subclause is applicable only for string-valued expressions, and determines the comparison semantics to use for that expression.
This release of SQL Server Compact Edition, when it is used with the ADO.NET Entity Framework, does not support the use of a COLLATE subclause in the ORDER BY clause of an Entity SQL query. The following query will not be supported:
SELECT value c
FROM NW.Customers AS c
ORDER BY c.Name COLLATE Traditional_Spanish_ci_ai
The ADO.NET Entity Framework enables time-outs for commands to be specified by using the ObjectContext.QueryTimeout property or the EntityCommand.CommandTimeout property.
This release of SQL Server Compact Edition, when it is used with the ADO.NET Entity Framework, does not support time-outs. That is, the command time-out must not be set to a value other than zero. If a connection time-out property is set, a NotSupportedException("CommandTimeout") exception is raised by the SQL Server Compact Edition database.
The ADO.NET Entity Framework provides support for both Unicode and non-Unicode strings. This release of SQL Server Compact Edition supports only Unicode strings. Literal of type "String" is not supported by the current provider. The 'near constant literal’ exception is raised by SQL Server Compact Edition in non-Unicode strings.
If the queries in a transaction scope take too long to finish and the transaction scope times out, the data might get committed to the database. To resolve this issue: To avoid data getting committed to the database, increase the time-out value.
SQL Server Compact Edition stops responding when an index is created on the column specified in the WHERE clause and NULL is used in the ESCAPE clause.
To resolve this issue:
Remove the index on the column specified in the WHERE clause.
SQL Server Compact Edition 3.5 is supported side-by-side on desktop computers and devices that run SQL Server 2005 Compact Edition. The behavior of side-by-side execution differs for desktop computers and devices.
To resolve this issue:
SQL Server 2005 Compact Edition should be installed side-by-side with SQL Server Compact Edition 3.5 on mobile devices. On desktops, the same process should not load both the SQL Server 2005 Compact Edition and SQL Server Compact Edition 3.5 library.
The Add Web Reference menu item is missing for following types of Smart Device projects:
To resolve this issue:
The following workaround will enable Add Web Reference menu item for Smart Device Projects based on .NET Compact Framework version 3.5:
If you install Visual Studio 2005 on the same computer as Orcas and then uninstall Orcas, the database diagrams in Visual Studio 2005 might not function correctly.
To resolve this issue:
Use Add or Remove Programs to repair Visual Studio 2005.
An error appears if you install Orcas on the same computer as Visual Studio 2005, uninstall Orcas, and then try to create a database project. The error states that the SqlServer.targets file cannot be found and that the project could not be created.
To resolve this issue:
Use Add or Remove Programs to repair Visual Studio 2005.
The Object Test Bench feature for Visual C#, Visual Basic, and Visual J# languages is not included in Orcas Beta 1.
To resolve this issue:
No workaround is available for this issue.
This problem occurs in the following scenario:
To resolve this issue:
There is no workaround.
Code Analysis in Orcas is currently unable to distinguish between all attributes that made a member different from other members. Attributes such as custom modifiers, generic arity, and calling convention are not used to distinguish between targets. This causes the following legal declarations to be seen as the same method:
class Foo
{
void Bar()
{
}
void Bar() // Overloaded based on generic arity
{
}
void Bar(__arglist) // Overloaded based on calling convention
{
}
}
Because the above members are seen as the same method, global suppressions applied against any are seen as applying to all. This limits the ability to find the correct location of the desired target and causes in-source suppression to be either placed against the incorrect member, or prevents in-source suppression altogether.
To resolve this issue:
There are no workarounds for this issue.
After you create a data source, you should be able to select it from the Data Sources window and drag and drop it onto the Form Region designer. This cannot be done as expected, and instead the "not-allowed" icon is displayed when the data source is being dragged.
To resolve this issue:
After you create the data source, instead of dragging it to the Form Region designer directly, drag the corresponding control from the toolbox (for example, the DataGridView) to the designer and then set the data source from the "Choose Data Source" drop-down list associated with the control.
Like the UserControl, you then must call the DataAdapter.Fill() function to fill the control with data. Add this in the FormRegionShowing event handler as in the following example:
C#:
private void myFormRegion1_FormRegionShowing(object sender, EventArgs e)
{
this.categoriesTableAdapter.Fill(this.northwindDataSet.Categories);
}
Visual Basic:
Private Sub FormRegion1_FormRegionClosed(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.FormRegionClosed
Me.categoriesTableAdapter.Fill(Me.northwindDataSet.Categories)
End Sub
The C# compiler and editor may not perform well when code that contains deeply nested lambdas or queries is used. Slowdown may be observed at five to ten levels of nesting, but other aspects of the code may also have an affect. At deeper levels of nesting, the C# compiler and editor may appear to hang.
To resolve this issue:
Reduce the nesting of lambdas and queries in the source code.
LINQ samples and some other C# and VB samples for Orcas are online. To get the latest information about the samples, go to Orcas Samples Page.
These samples are not included in the documentation that is installed with Orcas. However, the documentation does include a link to the samples.
An IndexOutofRange error dialog box might appear when the Settings and Constraints Editor or Web Service Details window is visible. This error might prevent you from using Orcas.
To resolve this issue:
Typed datasets include a new feature called hierarchical update that processes changed data in related data tables and sends those changes back to the database in the correct order. For the hierarchical update feature to function correctly, all relations (DataRelations) between data tables are set to Both Relation and Foreign Key Constraint by default.
When Foreign Key Constraint is enabled, Update Rule and Delete Rule are set to Cascade regardless of the setting in the database. Update Rule and Delete Rule will match the rules specified in the database.
To resolve this issue:
Use the Dataset Designer to change Update Rule and Delete Rule to match the constraint rules in the database. Double-click a relation line on the Dataset Designer to bring up the Relation dialog box, where you can modify the constraint rules in the dataset.
The file format for the DBML file generated by the O/R Designer is being changed. The current format that uses GUIDs will be replaced by a more readable format. There is currently no plan to provide upgrade tools that migrate to subsequent file formats. Entity classes created with the Orcas of the O/R Designer will not be supported in subsequent releases.
Adding a Web reference to a project that targets .NET Framework 3.0 or .NET Framework 3.5 is not possible from Solution Explorer if a Web reference does not already exist.
To resolve this issue:
To add a Web reference, downgrade the project to target the .NET Framework 2.0. This can be done in the Property pages for the project by changing the Target Framework to ".NET Framework 2.0" on the Application tab. Once the project has been downgraded to .NET Framework 2.0, add a Web reference. Then upgrade the project to target .NET Framework 3.0 or .NET Framework 3.5. From that point on, the Web reference menu items will be available on the Project and Web References folder in Solution Explorer.
The ASMX Web service supports two protocols, Soap and Soap 1.2. By default, Web references select Soap. Service references do not select a default protocol to use. Therefore, you must select the endpoint (and hence protocol) to consume an ASMX Web service.
To resolve this issue:
You can provide the endpoint name when you instantiate the proxy class. The example below shows the Soap12 endpoint being used:
(C#)
ServiceReference.ServiceSoapClient proxy = new ServiceReference.ServiceSoapClient("ServiceSoap12");
(Visual Basic)
Dim proxy As New ServiceReference.ServiceSoapClient("ServiceSoap12")
The wcfSvcchost.exe tool requires administrator permissions to run. The Windows Communication Foundation service library template in Orcas will not run correctly if wcfSvchost.exe is not available.
To resolve this issue:
Run Orcas under an Administrator account when you author services by using wcfSvchost.exe.
The svcConfigEditor.exe is not available on the Tools menu of Orcas. The tool cannot be started from the IDE.
To resolve this issue:
Install the Windows SDK, which includes the editor. The svcConfigEditor.exe is located on the Windows Start menu.
When you use a Web site or application over a Remote Desktop as non-Admin, NTLM authentication is automatically enabled. 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:
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, which makes NTLM Authentication unnecessary.
This problem occurs in the following scenario:
To resolve this issue:
There is no workaround for this issue.
Solutions and projects created in Orcas can be opened and edited in Microsoft Expression Blend, but solutions and projects will not build.
To resolve this issue for pre-release (Beta and RC) versions of Microsoft Expression Blend:
Upgrade to the final release of Microsoft Expression Blend (when available) or build solutions and projects in Orcas.
To resolve this issue for the final release Microsoft Expression Blend:
See Issue 1.3.34 for a resolution to this problem.
When you open Microsoft Expression Blend projects in Orcas they will be upgraded to the Orcas format. Once this upgrade is complete the project will no longer build in Microsoft Expression Blend. You can still open and edit the project in Microsoft Expression Blend, but the project will not build in Microsoft Expression Blend.
To resolve this issue for pre-release (Beta and RC) versions of Microsoft Expression Blend:
Upgrade to the final release of Microsoft Expression Blend (when available) or build solutions and projects in Orcas.
To resolve this issue for the final release of Microsoft Expression Blend:
Apply the following (one-time only) workaround. This workaround applies only if Orcas is installed.
<?xml version ="1.0"?>
<configuration>
<startup>
<supportedRuntime version="v2.0.50727" safemode="true"/>
<requiredRuntime version="v2.0.50727" safemode="true"/>
</startup>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="Microsoft.Build.Framework" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
<bindingRedirect oldVersion="0.0.0.0-99.9.9.9"
newVersion="3.5.0.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="Microsoft.Build.Engine" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
<bindingRedirect oldVersion="0.0.0.0-99.9.9.9"
newVersion="3.5.0.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>
</configuration>
Note: If you uninstall Orcas and .Net Framework 3.5, you should also delete Blend.exe.config.
When you open a Windows Presentation Foundation (WPF) project that was created in an earlier version of Visual Studio or in Microsoft Expression Blend, the Orcas upgrade wizard will upgrade the project. As part of this process, you can choose to back up the project before migration. This migration process does not back up .XAML files.
To resolve this issue:
Back up the project manually before you open the project in Orcas.
The latest information about limitations and issues with the use of the Windows Presentation Foundation (WPF) Designer ("Cider") in Orcas can be found here.
If you attempt to import Code Snippets on Windows Vista, the attempt will fail with the following message: "The snippet files chosen were not valid."
To resolve this issue:
Manually add the snippets to the existing snippets folder.
If you edit very large XAML files in the WPF Designer ("Cider"), the designer will use large amounts of memory and CPU time. Our recommendation is to avoid editing very large XAML files in the WPF Designer in this release. "Very large" means files larger than 150KB or files with over 1000 elements; for example, a XAML file of a vector drawing that contains large numbers of Path elements.
When you add an element (for example a Button with Name="btnSave") to your XAML file, that named element will only appear in C# or Visual Basic IntelliSense in the code-behind file after you have saved the XAML file.
To resolve this issue:
Save the XAML file before you code against objects that are declared in the XAML file.
MDAC SDK is not installed with Orcas. As a result, ATL and MFC projects for OLE DB applications fail to build.
To resolve this issue:
Visual Studio 2005 projects upgraded to Orcas as well as new projects created in Orcas fail to build due to missing Windows SDK files.
To resolve this issue:
The following solution options are available:
A. From the IDE:
On the Tools menu, click Options, and then navigate to Projects & Solutions, VC++ Directories.
In each case add to end of list
Platform:Win32
B. From the Command Line:
The registry key that references the Windows SDK include path is not populated in the WOW registry hive. This prevents projects from being built.
To resolve this issue:
The following solution options are available:
Change:
:GetWinSDKFolder
@call :GetWinSDKFolderHelper HKLM > nul 2>&1
@if errorlevel 1 call :GetWinSDKFolderHelper HKCU > nul 2>&1
@if errorlevel 1 set WinSDKFolder=%VCINSTALLDIR%\PlatformSDK\
@exit /B 0
To:
:GetWinSDKFolder
@call :GetWinSDKFolderHelper HKLM > nul 2>&1
@if errorlevel 1 call :GetWinSDKFolderHelper HKCU > nul 2>&1
@if errorlevel 1 set WinSDKFolder=%systemdrive%\Program Files\Microsoft SDKs\Windows\v6.0\
@exit /B 0
This will cause vcvars32.bat to give the correct values each time it is run.
Replace $(WindowsSDKDir) with "%systemdrive%\Program Files\Microsoft SDKs\Windows\v6.0\"
(For example, replace $(WindowsSdkDir)\bin with C:\Program Files\Microsoft SDKs\Windows\v6.0\)
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SDKs
"%systemdrive%\Program files\Microsoft SDKs\windows\v6.0\"
Projects that reference winable.h and oleacc.idl will fail to build because files are missing. Winable.h has been deprecated in Orcas. Oleacc.idl is not available in Orcas Beta 1.
To resolve this issue:
Reference winuser.h instead of winable.h.
ADO.NET Entities does not support ASP.NET for Orcas and none of the item templates that support the ADO.NET Entity Data Model will appear in Visual Web Developer Express.
The messaging CABs provide all error strings and are required to quickly solve runtime issues because they include descriptions of the exceptions. These CABs may not be deployed because entries are missing in the microsoft.netcf.3.5.xsl file.
To resolve this issue:
The Orcas Content Installer may not install certain 2.0 content types correctly. Furthermore, installation of Code Snippets will not work since the "My Code Snippets" folder will not appear when importing code snippets.
To resolve this issue:
Manually unzip the content file and copy the contents to the appropriate folders based on their type. For example, add-ins can be copied to "\My Documents\Visual Studio Codename Orcas\Addins".
When you open a Windows Presentation Foundation (WPF) project created in an earlier version of Orcas or in Microsoft Expression Blend, the Orcas upgrade wizard will upgrade the project. However, this process does not correctly set the "custom tool" option on XAML files. This means that IntelliSense for named elements will only appear in C# or Visual Basic IntelliSense in the code-behind file after you have built the project.
To resolve this issue:
Build the project or set the Custom Tool in the file properties to Custom Tool = "MSBuild:Compile".
The use of C# Refactoring features (for example, Rename, Extract Method, Reorder/Remove Parameter) is not yet supported for C# 3.0 language constructs. The following examples illustrate some unsupported scenarios:
To resolve this issue:
There is no workaround. Refactoring will still work as expected when it is used with language constructs from previous versions of C#.
When you use the Crystal Reports .NET 3.5 project template "Crystal Reports Application" to create a Visual Basic Windows application, the project will not build successfully and the Form1.vb design view displays the following errors:
Could not find type 'CrystalReportsApplication1.CrystalReport1'
The variable 'CrystalReport11' is either undeclared or was never assigned.
To resolve this issue:
LINQ relies on a new feature called Local Variable Type Inference to implicitly infer strongly-typed local variables based on the value of the right-hand side of an assignment. This feature is controlled by a compiler setting, Option Infer, which by default is on for most new projects. In WCF projects and in MSBuild compilations, the setting for Option Infer is not propagated.
To resolve this issue:
Put "Option Infer On" at the top of all source files that use LINQ.
Step-into and highlighting of breakpoints does not work correctly when you are debugging workflows.
To resolve this issue:
Disable the advanced thread debugging features of Orcas when you are debugging workflows. On the Tools menu, click Options, and then navigate to Debugging, Enable advanced debugging features. Disable the feature.
While you are debugging a workflow, it is not possible to step into the activity code from a breakpoint set on the activity.
To resolve this issue:
Set a breakpoint in the code handler for the activity.
When run under the debugger, WPF Browser applications can crash on Windows Vista. This displays an error message instead of stopping the debugger. When this happens, Orcas must be closed and restarted.
To resolve this issue:
The registry must be modified to disable the Func-Eval Quick Abort feature. This feature fixes a problem that typically occurs during the debugging of multi-threaded WinForm applications. Therefore, you must restore the registry keys and restart Orcas before you debug a multi-threaded WinForm application.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\AD7Metrics\Engine\{449EC4CC-30D2-4032-9256-EE18EB41B62B}]
"EnableFuncEvalQuickAbort"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\AD7Metrics\Engine\{92EF0900-2251-11D2-B72E-0000F87572EF}]
"EnableFuncEvalQuickAbort"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VBExpress\9.0\AD7Metrics\Engine\{449EC4CC-30D2-4032-9256-EE18EB41B62B}]
"EnableFuncEvalQuickAbort"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VCSExpress\9.0\AD7Metrics\Engine\{449EC4CC-30D2-4032-9256-EE18EB41B62B}]
"EnableFuncEvalQuickAbort"=dword:00000000
The problem is caused by a recent design change to the common language runtime (CLR) components for the .NET Framework 2.0 that are installed with this release of Orcas. This change causes compatibility issues for the design-time engine of Microsoft Visual Studio for Applications as described in KB article 938209. Visual Studio 2005 uses the design-time engine of Visual Studio for Applications for macro capabilities. These compatibility issues may prevent the macro script from being compiled successfully or from being loaded successfully. Therefore, the macro does not run.
To resolve this issue:
Install Microsoft Visual Studio 2005 Team Suite Service Pack 1 here.
The compilation of Workflow projects that contain SReceive or Send activities fails even when they are configured correctly.
To resolve this issue:
Delete the SMDiagnostics.dll file from the References section for the Workflow project.
When you load a Microsoft Office SharePoint Server workflow project in Visual Studio Tools for Office, you should see the SharePoint activities added to the toolbox in a separate tab. Currently, only the Windows Workflow activities appear in the toolbox. In this release, you must add the activities manually.
To resolve this issue:
To add a tab and items to the Orcas toolbox, see Managing Tabs and Items in the Toolbox.
The SharePoint activities that you must add to the toolbox are located in the Microsoft.SharePoint.WorkflowActions namespace. When you follow the directions in the Managing Tabs and Items in the Toolbox help topic, you will see the Choose Toolbox Items dialog box when you add items to the toolbox. To display only the SharePoint workflow activities that you want to add, type the Microsoft.SharePoint.WorkflowActions namespace in the dialog's Filter textbox.
When you view the workflow design, you can set breakpoints both on lines of code and on activities or workflow states. However, when you set a breakpoint on an object
in the workflow designer, you will see the following error when you press F5 to begin
debugging your project:
Error loading workflow. An error occurred while loading the
workflow. Please correct the following error and try reloading the document to view
the workflow. Could not deserialize object. The type "CustomWorkflow.Workflow1"
could not be resolved.
To resolve this issue:
To avoid this error, remove any breakpoints on activities or states in the workflow designer. Use breakpoints in code procedures instead.
When you press F1 for help on language elements or UI while you are using local Help, you may receive the incorrect topic or a topic-not-found message. Dynamic Help may also display incorrect topics.
To resolve this issue:
Use Online Help as the primary source for Help. This is the default setting. To change the primary source to Online Help, do the following:
Triggering IntelliSense in the script block of an HTML file may be slow when there are many script blocks in the HTML file. A similar performance degradation is also observed when a JScript file references an HTML file that contains many script blocks. The slowdown can be observed when there are more than 10 script blocks. When there are even more script blocks, triggering IntelliSense may appear to hang the system.
To resolve this issue:
Combine script blocks or otherwise decrease the number of script blocks in the HTML file.
In this release, there are known issues when you use breakpoints in the debugger with some Office 2003 projects. If you complete the debugging process when you have breakpoints, then the Office application may not close correctly and you may receive an Office error. When you debug without using breakpoints, this is not an issue.
If you stop the debugging process before it completes, Orcas may crash.
To resolve this issue:
There is no workaround at this time. To avoid receiving the Orcas error, do not stop the debugging process until it has completed.
In this release, if you close an Excel 2003 project while the Excel designer is still open, then Excel cannot close correctly and you will receive an error. Nevertheless, the project will be saved correctly.
To resolve this issue:
Before you close an Excel 2003 project, manually close the designer window.
System.DirectoryServices.AccountManagement.dll does not appear on the .Net tab of the Add Reference dialog box.
To resolve this issue:
To add a reference to System.DirectoryServices.AccountManagement.dll, use the Browse tab of the Add Reference dialog box to locate the System.DirectoryServices.AccountManagement.dll in %windir%\Microsoft.NET\Framework\v3.5\.
When you are developing Outlook form regions, the only FormRegionMessageClass attribute that will be generated is for a Mail Message (IPM.Note) whether multiple standard message classes are checked, custom message classes are entered, or both.
To resolve this issue:
Manually add a FormRegionMessageClass attribute for each message class that you want the form region to be associated with.
When the Upgrade Wizard is run on the Professional version, it will cause the following
exception to occur:
Unexpected exception occurred during upgrade engine operation:
Retrieving the COM class factory for component with CLSID {EB29F2BC-A843-4C09-9355-03E58D51EC29}
failed due to the following error: 800736b1.
To resolve this issue:
There is no workaround for this issue.
Source code can be generated but it cannot be compiled because it will contain an invalid reference to a Private Accessor assembly.
To resolve this issue:
There is no workaround for this issue.
Using a Receive activity in the Workflow Foundation designer results in an error in Orcas because the shell cannot find a dependency.
To resolve this issue:
Copy SMDiagnostics.dll in the C:\Windows\Microsoft.NET\Framework\v3.0\Windows CommunicationFoundation\ folder. Paste it in the location required by the compiler (for example, C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.0). Doing this should solve the problem.
Changes made to some settings in the Sharepoint Workflow Wizard are not persisted. As a result, the project is created by using the default values instead of the changed values.
To resolve this issue:
Specify any properties you want to change on the first and second pages of the wizard, but do not click Finish on the second page. Instead, click Next to continue to the final page of the wizard. After you click Finish on the final page and the wizard finishes, the changes that you made are respected, except for any that you made on the final page. If you want to change any settings that appeared on the final page, you can do so by manually changing them in the Properties window.
In the Create Unit Tests dialog box for a Web application project, the tree cannot be expanded. Therefore, you cannot select the methods for which you want to generate unit tests.
To resolve this issue:
In the Create Unit Tests dialog box, click the Add Assembly button and then add the appropriate Web Application Project Assembly. Doing this will open the Create Unit Tests dialog box so that you can select the methods for which you want to generate tests. After you select the methods you want and generate the tests, you must add the proper attributes to the test method so that the test will execute correctly. The required attributes include Host Type (set to ASP.NET), AspNetDevelopmentServerHost (set to the path to the web site), and UrlToTest (set to the URL to test) .
Orcas may not be able to generate unit tests when device projects and desktop projects exist in the same solution.
To resolve this issue:
Do not add both types of projects to the same solution.
Orcas currently does not show a progress bar when tests are being generated.
To resolve this issue:
There is no workaround for this issue
Inheritance of test classes is not supported when inheritance spans classes that are defined outside the active test project.
To resolve this issue:
Put all the classes that will use inheritance into the same test class.
Although Orcas supports the inheritance of test classes, inheritance of test class attributes ([ClassInitialize], [ClassCleanup]) has been disabled in Beta 1.
To resolve this issue:
Copy the initializations in external classes so that inheritance is not required.
After you set the Access Modifier drop-down in the resource editor for a .resx file or for the Resources project properties page, you receive one of the following warnings in the task list:
To resolve this issue:
ASP.NET unit tests fail to run against ASP.NET Development Server, and the following error message is generated: "Could not find WebDev.Webserver.exe".
To resolve this issue:
If you receive the error "Could not find WebDev.Webserver.exe," then do the following:
If you want to add event handlers to WPF controls, you cannot do so by using the WPF Designer (for example double-clicking on the control).
To resolve this issue:
You must use the code editor features to add event handlers to WPF controls. In Visual Basic you can use the event drop-down lists in the code editor. In Visual C# you can use statement completion in the code editor.
The CSS Property Grid in Orcas Beta 1 is missing a file. Therefore, it is disabled.
To resolve this issue:
Copy the CSS schema file C:\Program Files\Common Files\Microsoft Shared\OFFICE12\SCHEMAS\CSS\css21.xml, and then paste it in C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\.
The Orcas Beta 1 ARM compiler supports native code generation of Vector Floating Point (VFP) instructions if the -QRfpe- switch is used. However, the compiler’s use of VFP registers is not compatible with Exception Handling (SEH and C++ EH). If a function that uses VFP throws an exception, catches an exception, or is on the callstack between the functions where an exception is thrown and caught, stack corruption may result. This situation could lead to unpredictable behavior or process termination.
To resolve this issue:
Mixing EH and VFP is not recommended. Either use __try/__except or try/catch to stop an exception from propagating, or do not compile by using the -QRfpe- switch when you are using exception handling.
IntelliSense in the Immediate window has been disabled for Beta 1 in C# projects. This is because support for C# 3.0 language features is not yet supported in IntelliSense in the Immediate window.
To resolve this issue:
There is no workaround. The Immediate window can still be used for evaluation.
If you run an Office 2007 application add-in created with this release on a 64-bit environment, you will receive a runtime error. This includes both running the add-in from the IDE, and installing and using the add-in outside of the IDE. This is because the cache for the add-in is not created correctly in this release.
To resolve this issue:
Before you run an Office 2007 add-in project, or install an Office 2007 add-in, create and publish a Windows Forms application. Then install that application on the computer on which you want to run the Office 2007 add-in. Running a Windows Form application creates the cache that Office 2007 add-ins can use.
Device Test Project execution may fail with error message "attempted to read or write protected memory" if the test project contains any combination of Unit Tests and Ordered Tests.
To resolve this issue:
On the PocketPC platform, FindText method of CEditView class will fail to locate a string if the text on the edit control is set by using SetWindowText.
To resolve this issue:
Type some text in the Edit Control or send message WM_CHAR before you invoke FindText method. For normal UI-based operations, no workaround is required.
The most common cause of this is when the code under test or the assembly under test raises a ThreadAbortException. This can also be seen in any situation when a test run receives a ThreadAbortException. For example, the following Test causes the test that is running on device to hang:
[TestMethod()]
public void abortTest()
{
System.Threading.Thread.CurrentThread.Abort();
}
To resolve this issue:
There is no known workaround. If possible, remove the Thread.Abort from the code under test or the assembly under test, and then restart the run.
The run-time and design-time features for the Visual J# language are not supported in Orcas. For more information, click here.
To resolve this issue:
No workaround is available.
By default, the debugging of WCF Services is not enabled in Orcas because that would break some important non-debugging scenarios, including partial trust HTTP hosting of services and Workflow-first authored services.
As a result, the following debugging scenarios are not enabled out of the box:
To resolve this issue:
Orcas provides a tool to enable and disable the debugging of WCF client-service applications.
To enable WCF debugging:
To disable WCF debugging:
To determine whether WCF debugging is enabled:
In order to return the form region manifest to Outlook during startup, an instance of FormRegionControl is created and cached for the lifetime of the add-in. This instance is not associated with any specific Outlook form region or item, and it will cause controls or other objects to be instantiated one more time than the number of current Outlook form regions.
To resolve this issue:
If there are any controls, components, or objects that will cause visual, memory, or performance issues if an extra instance is created, make sure to instantiate these in the FormRegionShowing event.
On x64 Windows Vista systems, a change in the architecture of the Windows Mobile Device Center (WMDC) application requires customers to patch their SerDMAASPlugin.dll to its x64 version. If this patch is not applied, users will not be able to cradle the device emulator to the desktop. Cradling is fundamental to Device Emulator application scenarios and is dependent on users having SerDMAASPlugin.dll.
To resolve this issue:
Install the 64-bit version of SerDMAASPlugin.dll here.
The next version of ADO.NET only supports Visual Basic Codename "Orcas" Beta 1 Express, Visual C# Codename "Orcas" Beta 1 Express and Visual Studio Codename "Orcas" Beta 1 Standard Edition, Professional Edition, and Team System Editions.
1.4.11. Orcas may not function properly following an OS upgrade such as Windows XP to Windows Vista
The .Net Framework 2.0 and 3.0 updates are not migrated as part of the OS upgrade leaving Orcas in a partially functional state.
To resolve this issue:
Uninstall the .Net Framework 3.5 and repair Orcas.
See .NET Framework 3.0 Release Notes.
If IIS is installed after .NET FX 3.5 or is reinstalled to repair the IIS configuration files (machine.config, web.config and applicationhost.config), CFXInstaller.exe has to be run manually from a command prompt.
To resolve this issue:
.NET Framework 2.0 and .NET Framework 3.0 langpacks must be manually uninstalled before .NET Framework 3.5 langpacks can be installed.
To resolve this issue:
Uninstall .NET Framework 2.0 and .NET Framework 3.0 langpacks
There are no known uninstalling issues.
There is a known issue in the ADO.NET Entity Data Model wizard. When you use SQL Server authentication and choose "Yes, include the sensitive data in the connection string" and click OK, the wizard disappears.
To resolve this issue:
Either use Windows Authentication or choose "No, exclude sensitive data from the connection string".
This is a known issue and will be fixed in a subsequent release.
To resolve this issue:
Choose a valid connection and ensure that the entity connection text box contains a valid connection name.
The following WCF samples will not work on Orcas:
To resolve this issue:
To run these samples, use .NET Framework 3.0.
After we released the BigInteger type in earlier CTPs, we received some constructive feedback from customers and partners who are interested in extended numerical types. We have learned that we must make some improvements so that this type better serves their needs. We decided to remove BigInteger from Orcas so that we can address these issues and concerns. Please let us know how this affects you and what would you expect in a BigInteger class. You can e-mail us at bclpub@microsoft.com.
The code snippets included in the documentation for Beta 1 were finalized before the Beta 1 bits, and therefore did not reflect the change of the type's name from TimeZone2 to TimeZoneInfo. As a result, if you copy the code from the documentation and paste it into Visual Studio, your attempts to compile it will produce "type or namespace not found" compiler errors.
To resolve this issue:
Rename all occurrences of TimeZone2 to TimeZoneInfo after you paste the code into an Orcas project.
The root namespace must be set to an empty string for Visual Basic projects that have ADO.NET Models. The ADO.NET Entity Data Model wizard will automatically set the root namespace to empty for Visual Basic projects.
The Namespace attribute in the Schema element of the Model (.csdl) file must be different from the one in the Target (.ssdl) file. The next version of ADO.NET throws an exception at runtime if they are the same.
One-to-one relationships cannot be mapped in the conceptual models of the Entity Data Model.
To resolve this issue:
If a one-to-one relationship is present in the database, it can be mapped to a single entity (by using entity splitting) if the two tables share the same primary keys.
Assemblies that contain ADO.NET Entity Data Models must be compiled outside the ASP.NET Web site project. They can be used in ASP.NET projects by copying the assembly into the "bin" Web site directory or by adding a reference to them. The CSDL, MSL and SSDL files should also be copied into "bin".
To resolve this issue:
Please refer to the next version of the ADO.NET Web sample for more information about how to deploy, locate, and load the appropriate CSDL, MSL, and SSDL files.
The Entity Data Model requires all entities to have keys. When the ADO.NET Entity Data Model Wizard generates files from a database table without a primary key, the project will not compile until a key is specified in the model files.
To resolve this issue:
The wizard will mark the places in the files with element names prefixed with the string "TODO". The wizard also adds warning messages to the Orcas task window.
The sample application should automatically mount the modified Northwind Database. If it is not successful or if you want to use a different version, you can manually mount the database and change the connection string.
To resolve this issue:
To change the database that is used by the LINQ to Entities Samples, change the connection string that is contained in the "Provider Connection String" setting of the Entity Framework connection string. If you use the App.config for a connection string, please see the documentation.
If you add or change Entity Framework files (for example, .csdl or .msl), make sure that you have set the "Copy To Output" setting so that the files are included with any builds.
Customers can get updated documentation for Microsoft Synchronization Services for ADO.NET here.
If you are calling managed code exposed as a COM object and this throws an exception followed by abnormal thread termination, then a spurious Managed Debug Assistant may fire and warn about managed code being run under the operating system’s loader lock. Such a warning during thread termination can be safely ignored.
To resolve this issue:
Turn off the loader lock Managed Debug Assistant.
The iisreset utility does not work unless MSMQ is installed or the NetMsmqActivator service is disabled. The WCF Samples setup script Setupvroot.bat will not run unless MSMQ is installed or the NetMsmqActivator service is disabled.
To resolve this issue:
Make sure MSMQ is installed or disable the NetMsmqActivator service on Windows Vista before you run the WCF Samples setup script Setupvroot.bat.
The WebScriptServiceHostFactory class is designed to enable Windows Communication Foundation services to be used to serve data to AJAX-enabled Web pages without having to write WCF configuration settings. In this Orcas release, the WebScriptServiceHostFactory class does not work with WCF operations that have been configured so that the HttpTransferContractAttribute attribute uses the HTTP GET verb. You may get an error about an AddressFilter mismatch if you attempt to use it with such operations.
To resolve this issue:
Avoid using HTTP GET operations and use HTTP POST instead. If this is impossible, then instead of using the WebScriptServiceHostFactory, create a WCF configuration section in web.config or another configuration file as appropriate and then use it to enable an AJAX endpoint. (Also see note 2.4.15 about endpoint URLs that end directly with ".svc".)
There is no way to implement classes as singleton in the existing WMI Provider Extension 2.0.
In this release, it is possible to use the Windows Communication Foundation to write IIS-hosted services that can be consumed from AJAX-enabled Web pages. These services can be hosted at endpoints with URLs that end directly with ".svc" (for example, "http://example.com/myService.svc") or at endpoints with URLs that end with an additional suffix (for example, "http://example.com/myService.svc/myEndpoint"). In this release, the URLs without a suffix do not work with WCF operations that have been configured with the HttpTransferContractAttribute attribute to use the HTTP GET verb, unless a workaround is applied. You may get an error about an AddressFilter mismatch if you try to use such URLs with GET operations.
To resolve this issue:
There are three ways to resolve this issue.
In this release, it is possible to use the Windows Communication Foundation to write services that can be consumed from AJAX-enabled pages. To work with the ASP.NET AJAX framework, references to such WCF services must be added to the Script Manager control. The Script Manager control enables you to inline service references by setting the InlineScript property to "true" on a particular service reference in the Services collection. In this release, WCF services are incompatible with the InlineScript="true" mode. You may get an InvalidCastException if you attempt to use this mode.
To resolve this issue:
Set the InlineScript property for all WCF services in the Script Manager control to "false".
To support native 64bit applications that use WF or WCF, manual modifications to the configuration are required.
To resolve this issue:
For selfhosted applications, the following modification to machine.config is required:
For applications hosted within IIS, there are two possible workarounds:
A. Configure IIS to run in WOW mode:
cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1
Windows XP, Windows 2003
Windows Vista
B. Update %windir%\Microsoft.NET\Framework64\v2.0.50727\CONFIG\web.config by adding the following:
InstallUtil is used to execute the installers in each given assembly. Some information is written during schema generation on the computer that is running InstallUtil even if the mof file is generated, and as a result, Mofcomp is not called. This causes the class to be created but not the registration. The result is a "Not Found" error on enumeration and a WMIInfraException when you try to register the class.
The iisreset utility does not work unless MSMQ is installed or the NetMsmqActivator service is disabled. The WCF Samples setup script Setupvroot.bat will not run unless MSMQ is installed or the NetMsmqActivator service is disabled.
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.
If IIS 6 Metabase Compatibility is enabled when Orcas is installed, additional configuration steps are required to webhost .xoml services in Integrated Mode (default) because not all the necessary HTTP Handlers will be installed.
To resolve this issue:
To install the necessary handlers, do the following:
The offline WCF and WF samples that are included with Orcas Beta 1 do not compile or run.
To resolve this issue:
Download the online versions of the Orcas Beta 1 samples for .NET Framework 3.5.
When you serialize objects returned from the database by LINQ to SQL, all related objects will also be serialized. Because of this, all the related objects will be defer-loaded from the database into memory. The serializer triggers this deferred loading automatically by accessing members that are defer-loadable relationship properties.
To resolve this issue:
Use DataShape.LoadWith() to pre-load the data you want, and turn off deffered loading by setting DeferredLoadingEnabled = "False" on your DataContext.
The documentation and tools provided in the Windows SDK support the application programming interfaces (APIs) available in the Windows Vista, Windows XP Service Pack 2 (SP2), and Microsoft Windows Server 2003 Service Pack 1 (SP1) versions of Windows. Not all APIs are supported on all platforms. See the specific API documentation to determine which platform the API supports.
This release of the Windows SDK for Orcas includes headers and libraries for Win32 development on x86 and x64 platforms only. IA64 Win32 development is not supported.
The Orcas release of the Windows SDK installs Windows Vista RTM headers and libraries as well as Windows Server 2003 SP1 headers and libraries. By default, Orcas uses Windows Vista headers and libraries.
When Orcas is uninstalled, the .Net Framework SDK 2.0 will also be removed. This may break other Visual Studio installations. To work around this issue, repair the other Visual Studio installations, or re-install .Net Framework SDK 2.0.
The registry key that references the Windows SDK include path [$(WindowsSDKDir)] is incorrectly set. This prevents projects from being built.
To resolve this issue:
Set the $(WindowsSDKDir) path correctly:
MDAC SDK is not installed with Orcas. As a result, ATL and MFC projects for OLE DB applications fail to build.
To resolve this issue:
Visual Studio 2005 projects upgraded to Orcas as well as new projects created in Orcas fail to build due to missing Windows SDK files.
To resolve this issue:
The following solution options are available:
A. From the IDE:
On the Tools menu, click Options, and then navigate to Projects & Solutions, VC++ Directories.
In each case add to end of list
Platform:Win32
B. From the Command Line:
Projects that reference winable.h and oleacc.idl will fail to build because files are missing. Winable.h has been deprecated in Orcas. Oleacc.idl is not available in Orcas Beta 1.
To resolve this issue:
Reference winuser.h instead of winable.h.
The registry key that references the Windows SDK include path is not populated in the WOW registry hive. This prevents projects from being built.
To resolve this issue:
The following solution options are available:
Change:
:GetWinSDKFolder
@call :GetWinSDKFolderHelper HKLM > nul 2>&1
@if errorlevel 1 call :GetWinSDKFolderHelper HKCU > nul 2>&1
@if errorlevel 1 set WinSDKFolder=%VCINSTALLDIR%\PlatformSDK\
@exit /B 0
To:
:GetWinSDKFolder
@call :GetWinSDKFolderHelper HKLM > nul 2>&1
@if errorlevel 1 call :GetWinSDKFolderHelper HKCU > nul 2>&1
@if errorlevel 1 set WinSDKFolder=%systemdrive%\Program Files\Microsoft SDKs\Windows\v6.0\
@exit /B 0
This will cause vcvars32.bat to give the correct values each time it is run.
Make sure the x64 tools are being used, and not the x86 tools. The x64 tools are located in "Program Files" directory and the x86 tools are located in the "Program Files (x86)" directory.
Windows PowerShell was available to customers and partners as a part of the Windows SDK. This is no longer the case. Now, Windows PowerShell can be downloaded directly.
Tb3x.exe has been deprecated and removed from the Windows SDK.
To resolve this issue:
There is no workaround for this issue.
The Application Verifier tool is not available in the Windows SDK. It ships as part of the Windows Application Compatibility Toolkit.
To resolve this issue:
Download the Windows Application Compatibility Toolkit.
To resolve this issue:
Make sure SvcConfigEditor.exe is the only process that accesses the file during a session.
If you use SvcConfigEditor.exe to delete the address value in the localIssuer element of clientCredential in the Windows Communication Foundation Endpoint Behavior, the tool will create an invalid configuration file and your application will throw an exception. This is because SvcConfigEditor.exe does not remove localIssuer when the localIssuer value is an empty string, which is an unexpected value.
To resolve this issue:
Remove the localIssuer element by using some other editor, such as Notepad.
In traces that contain Arabic characters, the XML view in SvcTraceViewer.exe may render the characters in reverse order.
To resolve this issue:
Use the Formatted View, which displays the traces in the correct character order. You can also copy the text from the XML view and paste it into some other editor that displays the characters in the correct order.
SvcUtil.exe can generate code for Web service proxies 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.
Although Windows Communication Foundation (WCF) allows the setting of the ReliableSession Binding Element InactivityTimeout or AcknowledgementInterval properties to TimeSpan.MaxValue, WCF will not consume WSDL generated by an endpoint with such settings. Instead, the import will fail and SvcUtil.exe will throw an InvalidChannelBindingException.
To resolve this issue:
After you download the WSDL, manually change the TimeSpan.MaxValue to 2147483647 (Int32.MaxValue). Then, in the generated configuration file, change the inactivityTimeout or acknowledgementInterval attribute from "24.20:31:23.6470000" to "Infinite".
You can use the SvcUtil.exe tool to generate code for Web service proxies and data types from metadata. However, there are known issues with the C++ code provider in Visual Studio 2005 and the .NET Framework 2.0 SDK that can cause the tool to generate Managed C++ code that may not compile.
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 /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.
If Orcas is installed, MSBuild is hard-coded to use the tools installed with Orcas. These may not be the latest versions. To ensure that you are using the latest tools installed by the Windows SDK, use the tools located in the Bin directory of the Windows SDK install directory. By default, this is "C:\Program Files\Microsoft SDKs\Windows\v6.0 ".
On Windows Vista, some ETW providers use manifests instead of MOF registrations. For such providers without the trace schema in the WMI catalog, the current version of SvcTraceViewer.exe cannot decode the trace output.
To decode Windows Vista-specific binary traces with no CIM schema, use the command-line tool TraceRpt.exe, which ships with Windows Vista.
IntelliSense for .NET Framework 3.5 is missing.
To resolve this issue