Visual Studio Code Name "Orcas" June 2007 Community Technology Preview (CTP) Readme

 

Table of Contents

1. System Requirements

Supported Architectures:

Supported Languages:

Supported Operating Systems:

Installation Requirements:

2. Known Issues

2.1. Installing

2.1.1. Setup does not resume on reboot when a user runs setup under Least-privilege User Account (LUA) on Windows Vista

When "Orcas" is installed on Windows Vista, if Setup is launched under LUA, then Setup does not resume on reboot. This happens because the user context of the process is modified when the process is elevated. When the user context is modified, the auto-launch registry keys are written to the wrong location.

To resolve this issue:

After the computer has rebooted, log in and run Setup again.


2.1.2. SQL Server Compact 3.5 .msi files should be manually removed before a later version of "Orcas" Beta or "Orcas" CTP is installed

SQL Server Compact 3.5 .msi files are not removed when you uninstall "Orcas" CTP. If SQL Server Compact 3.5 .msi files are not manually removed after "Orcas" CTP is uninstalled, then the latest version of the SQL Server Compact 3.5 .msi files will not be installed together with a later version of "Orcas".

To resolve this issue:

To manually remove SQL Server Compact 3.5 .msi files, open Add or Remove Programs in the Control Panel. The SQL Server Compact 3.5 .msi files are:


2.2. Uninstalling

2.2.1. On computers that have earlier versions of Visual Studio, SQL Server Compact 3.5 is uninstalled together with "Orcas" Beta. This may create problems when two or more "Orcas" SKUs are installed side-by-side on the same computer

If "Orcas" Beta is uninstalled, then all SQL Server Compact 3.5 MSIs are also uninstalled. This can create problems when two "Orcas" SKU's are installed side-by-side on the same computer, for example, "Orcas" Standard and "Orcas" C# Express. If one of the "Orcas" SKU is uninstalled, then the SQL Server Compact 3.5 MSIs will also be uninstalled, and the other "Orcas" SKU will not work correctly.

To resolve this issue:

Run the remaining "Orcas" SKU in repair mode to reinstall the SQL Server Compact Edition 3.5 MSIs.


2.2.2. On computers that do not have earlier versions of Visual Studio

There are no known issues.


2.3. Product Issues

2.3.1. General Visual Studio issues

2.3.1.1. A misleading error message is received when the "Visual Studio Add-in" template is used on Windows Vista

When a new project is created by using the "Visual Studio Add-in" template on Windows Vista, the following error message is displayed: "An error occurred, and the wizard could not generate the project. Verify that the programming language is properly installed." The reason for the error may be a file-access-denied condition in Windows Vista.

To resolve this issue:

Restart Visual Studio under administrative credentials and elevated permissions. To run Visual Studio with elevated permissions, right-click the Visual Studio icon in the Windows Start menu and then click "Run as administrator".


2.3.1.2. Adding an item to a project that targets .NET Framework 3.5 but is missing a reference to System.Core.dll will introduce a build error

An item that is added to a project that targets .NET Framework 3.5 will include a "using System.Linq;" directive. If your project does not contain a reference to System.Core.dll, then this will introduce a build error in your project. The scenarios in which this will occur are as follows:

To resolve this issue:

  1. Right-click your project and then click Add Reference.
  2. On the .NET tab, find the reference to System.Core.dll.
  3. Click OK.


2.3.1.3. Encryption of a SQL Server Compact 3.5 database .sdf file cannot be changed after the file is created

A SQL Server Compact 3.5 database .sdf  file can be encrypted only while it is being created. Also, a SQL Server 2005 Compact Edition or SQL Server 2005 Mobile Edition database .sdf file may be encrypted while is is being upgraded to SQL Server Compact 3.5. After a SQL Server Compact 3.5 .sdf file has been created or upgraded from an earlier version, the encryption mode (Platform Default, Engine Default, PPC2003 Compatibility) of an encrypted file cannot be changed, and an unencrypted file cannot be encrypted. The Encryption Mode token in SqlCeConnectionString will be ignored while an existing SQL Server Compact 3.5 database is being opened. The Encrypt token is not used in SqlCeConnectionString. The token is retained in SQL Server Compact 3.5 for backward compatibility. The token should not be used and it will be deprecated in the future

To resolve this issue:

You can change the encryption mode of an existing SQL Server Compact 3.5 database or encrypt an existing unencrypted SQL Server Compact 3.5 .sdf file by creating a new SQL Server Compact 3.5 database and then pasting the existing schema and data in the new database.


2.3.1.4. Upgrading a Visual Studio 2005-based SQL Server Compact 3.5 project to "Orcas" will not also upgrade the references

When you upgrade a Visual Studio 2005 project to "Orcas", you must manually upgrade the references to SQL Server Compact 3.5 and upgrade the database file to SQL Server Compact 3.5.

To resolve this issue:

To upgrade a reference in "Orcas", click View in Solution Explorer, and then expand the References node. Right-click the reference and then click Properties.

To upgrade the database file, access the Upgrade to SQL Server Compact 3.5 dialog box in "Orcas" by clicking Data, clicking Add New Data Source, and then clicking Add Connection. Note: If you open an earlier version of the database in "Orcas", then a message may appear. When you click OK in the message, the Upgrade to SQL Server Compact 3.5 dialog box will appear.


2.3.2. ADO.NET

2.3.2.1. Data is partially committed during timeout in transaction scope in SQL Server Compact 3.5

If the queries in a transaction scope take too long to finish and the transaction scope times out, the data is partially committed to the database. Any data committed to the database before the transaction scope timeout will be rolled back. The data committed to the database after the transaction scope timeout will be committed to the database.

To resolve this issue:

To avoid such a situation, increase the time-out value.


2.3.3. Languages (Visual C++, Visual C#, Visual Basic)

There are no known issues.


2.3.4. LINQ

There are no known issues.


2.3.5. Visual Studio Tools for Office

There are no known issues.


2.3.6. Web Development

There are no known issues.


2.3.7. Windows Communication Foundation (WCF) Tools

There are no known issues.


2.3.8. Windows Presentation Foundation (WPF) Designer for Visual Studio

There are no known issues.


2.3.9. Windows Workflow Foundation (WF) Tools

There are no known issues.


2.3.10. Windows SDK Integration

2.3.10.1. Some IA64 libraries are missing from \Program Files\Microsoft SDKs\Windows\v6.0a\Lib\IA64\

Windows development on IA64 is not supported in this release of "Orcas".

To resolve this issue:

There is no workaround for this issue.


2.3.10.2. The TAPI Browser (Tb3x.Exe) Has Been Deprecated and Removed from the Windows SDK

Tb3x.exe has been deprecated and removed from the Windows SDK.

To resolve this issue:

There is no workaround for this issue.


2.3.10.3. The Application Verifier Tool is Not Available in the Windows SDK

The Application Verifier tool is not available in the Windows SDK. It is included in the Windows Application Compatibility Toolkit.

To resolve this issue:

Download the Windows Application Compatibility Toolkit.


2.3.10.4. The Configuration Editor Tool (SvcConfigEditor.exe) Reloads the Config File When It Is Changed by Another Entity

If you are using SvcConfigEditor.exe to edit a config file and another process or editor accesses that file, then SvcConfigEditor.exe will automatically reload the file. For example, this can happen when anti-virus software scans the config file. The reload will cause the loss of any changes made to the config file since SvcConfigEditor.exe last saved it.

To resolve this issue:

Ensure that SvcConfigEditor.exe is the only process that accesses the file during a session.


2.3.10.5. Possible Application Exception after localIssuer Address is Removed By Using The Configuration Editor Tool (SvcConfigEditor.exe)

If you use SvcConfigEditor.exe to delete the address value in the localIssuer element of clientCredential in the WCF Endpoint Behavior, the tool will create an invalid configuration file and your application will throw an exception. This happens because SvcConfigEditor.exe does not remove localIssuer when the localIssuer value is an empty string (an unexpected value).

To resolve this issue:

Manually remove the localIssuer element by using some other editor, for example, Notepad.


2.3.10.6. The TraceViewer Tool (SvcTraceViewer.exe) Does Not Display Arabic Characters Correctly

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 then paste it into some other editor that can display the characters in the correct order.


2.3.10.7. Code Generation Language Support in Service Model Metadata Utility Tool (SvcUtil.exe)

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.

To resolve this issue:

There is no workaround for this issue.


2.3.10.8. Service Model Metadata Utility Tool (SvcUtil.exe) Can Throw InvalidChannelBindingException When It Imports WSDL from Certain Endpoints

Although Windows Communication Foundation (WCF) enables setting the ReliableSession's Binding Element InactivityTimeout or AcknowledgementInterval properties to TimeSpan.MaxValue, WCF will not consume WSDL that has been 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".


2.3.10.9. Managed C++ Code Generated By Using Service Model Metadata Utility Tool (SvcUtil.exe) Tool May Not Compile

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. These issues with the C++ code provider will be addressed in a future release of Visual Studio 2005.

To resolve this issue:

There is no workaround for this issue.


2.3.10.10. Code Generation Language Support in Service Model Metadata Utility Tool (SvcUtil.exe)

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.

To resolve this issue:

There is no workaround for this issue.


2.3.10.11. 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 /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:

There is no workaround for this issue.


2.3.10.12. Un-decoded Windows Communication Foundation (WCF) traces appear on Windows Vista

On Windows Vista, some ETW providers use manifests instead of MOF registrations. For such providers that do not have the trace schema in the WMI catalog, the current version of SvcTraceViewer.exe cannot decode the trace output.

To resolve this issue:

To decode Windows Vista-specific binary traces that do not have a CIM schema, use the command-line tool, TraceRpt.exe, which is included with Windows Vista.


2.4. Related Links

2.4.1. Visual Studio Code Name "Orcas" June 2007 CTP Readme

To view the latest version of the Visual Studio Code Name "Orcas" June 2007 CTP Readme, click here.

2.4.2. Visual Studio Code Name "Orcas" Express Editions June 2007 CTP Readme

To view the latest version of the Visual Studio Code Name "Orcas" Express Editions June 2007 CTP Readme, click here.

2.4.3. Microsoft .NET Framework 3.5 June 2007 CTP Readme

To view the latest version of the Microsoft .NET Framework 3.5 June 2007 CTP Readme, click here.

© 2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks | Privacy Statement