March 2007 Community Technology Preview

This document lists issues you might encounter while using this release of the Microsoft Visual Studio Code Name “Orcas” product.

Contents:

1. The uninstall wizard for Visual Studio codename "Orcas" will chain uninstall all non-RTM prerequisites and optional components that were installed during install time.

For example, during uninstall time prerequisites such as WinFX 3.5 and optional components such as device emulator will be uninstalled along with Visual Studio codename "Orcas". If more than one SKU is installed on a machine the chain uninstaller may uninstall prerequisites and/or optional components out from under the other SKU(s).

To resolve this issue

Repair the remaining SKU and the prerequisites and/or optional components will be reinstalled on the machine.

2. Microsoft Visual J# Redistributable Package is not installed.

Installation of Microsoft Visual J# Redistributable Package is not supported in the March CTP Release.

1. Support for J# IDE functionality and the JLCA tool will continue through 2015 via the Visual Studio 2005 product family. This means that J# language project types and the JLCA will not be included in the Visual Studio “Orcas” release or beyond.

2. To meet customer requests for 64 bit assemblies, there will be an upgrade to the J# 2.0 redistributable, called “Visual J# 2.0 Redistributable Second Edition” and the product name will be “Microsoft Visual J# 2.0 Redistributable Second Edition (x86/x64/IA64)”

3. The J# 2.0 Runtime Second Edition will be made available through a release to web (RTW) and include support for 64-bit versions of the .NET Framework and additional bug fixes.

4. Assemblies that are compiled with the J# 2.0 Runtime Second Edition will run on the .NET Framework 2.0, 3.0 and the future version of the .NET Framework to be released with Visual Studio “Orcas”

5. Support for the J# 2.0 second edition redistributable will be 10 years (5 mainstream and 5 extended) from the time of its release. This will be the final release of the J# redistributable.

For more information, go to: http://msdn.microsoft.com/vjsharp/default.aspx

To resolve this issue

No workaround is available for this issue.

3. Java Language Conversion Assistant is not installed.

Installation of the Java Language Conversion Assistant tool is not supported in this CTP release.

3. The J# 2.0 Runtime Second Edition will be made available through a release to web (RTW) and include support for 64-bit versions of the .NET Framework and additional bug fixes.

5. Support for the J# 2.0 second edition redistributable will be 10 years (5 mainstream and 5 extended) from the time of its release. This will be the final release of the J# redistributable.

For more information, go to: http://msdn.microsoft.com/vjsharp/default.aspx

4. Installing and Uninstalling SQL Server Compact Edition Runtime.

SQL Server Compact Edition can be deployed on mobile devices either by manually copying and installing the CAB files or through Visual Studio. The SSCEDeviceRuntime-ENU.msi file places the SSCE 3.5 CAB files for deploying SSCE on the mobile devices. The CAB files are placed under the folder %Program Files%\Microsoft SQL Server Compact Edition\v3.5\Devices.

To resolve this issue

To uninstall SQL Server Compact Edition 3.5 CTP from a mobile device

· Click Start, Settings, System, and then Remove Programs.

· From the list of installed programs, select Microsoft SQL Server Compact Edition 3.5 CTP.

· Click Remove.

Installing and Uninstalling SQL Server Compact Edition Runtime on Desktop and Tablet PC

SQL Server Compact Edition has a separate installer (SSCERuntime-ENU.msi) for desktop computers and Tablet PCs. Some of the important considerations when you install SQL Server Compact Edition on a desktop computer or Tablet PC are as follows:

· To install or uninstall SQL Server Compact Edition, you must be an administrator on the desktop computer or the Tablet PC.

· Unless you are using the OLEDB data provider, the Microsoft .NET Framework 2.0 or a later version is required before you install SQL Server Compact Edition. You can download the .NET Framework 2.0 from .NET Framework 2.0 Download Center.

· You do not need Visual Studio or SQL Server 2005 installed before you install SQL Server Compact Edition on a desktop computer or Tablet PC.

· To replicate data between SQL Server and SQL Server Compact Edition, you require a version of SQL Server Compact Edition 3.5 Server Tools.

· To develop applications, you can use OLEDB or ADO.NET. For richer support, you can install Visual Studio.

Note:

SQL Server Compact Edition should be installed on desktop computers and Tablet PCs by the SSCERuntime-ENU.msi only. Any other mode of installing SQL Server Compact Edition might lead to serviceability problems.

To uninstall SQL Server Compact Edition 3.5 CTP

· Double-click Add or Remove Programs in Control Panel.

· From the list of installed programs, select Microsoft SQL Server Compact Edition 3.5 CTP.

· Click Remove.

5. Installing and Uninstalling SQL Server Compact Edition 3.5 CTP Server Tools.

SQL Server Compact Edition 3.5 Server Tools can be downloaded from the Microsoft Download Center.

If you are installing SQL Server Compact Edition Server Tools on a computer that is running Windows XP SP2 that uses Windows Firewall, you must specifically enable the HTTP and/or HTTPS services.

For more information about how to install and configure a server environment for Remote Data Access or merge replication, see "Installing a Server Environment" and "Configuring and Securing Server Environment" in SQL Server Compact Edition Books Online.

To enable the HTTP or HTTPS service

Double-click Windows Firewall in Control Panel.
Click the Advanced tab.
In Network Connection Settings, select the connection, and then click Settings.
Select Web Server (HTTP) or Secure Web Server (HTTPS), make sure the server name or IP address is correct, and then click OK.

To uninstall SQL Server Compact Edition 3.5 Server Tools CTP

Double-click Add or Remove Programs in Control Panel.
From the list of installed programs, select Microsoft SQL Server Compact Edition 3.5 Server Tools CTP.
Click Remove.
After uninstalling, you should restart IIS or reboot the computer running IIS.

Supported Operating Systems and Platforms for SQL Server Compact Edition 3.5 CTP

This release of SQL Server Compact Edition supports the following operating systems:

· Desktop and Tablet PC

o Microsoft Windows 2000 Professional SP4

o Microsoft Windows 2000 Server SP4

o Microsoft Windows XP Professional SP2

o Microsoft Windows XP Home Edition SP2

o Microsoft Windows XP Media Center Edition 2002 SP2

o Microsoft Windows XP Media Center Edition 2004 SP2

o Microsoft Windows XP Media Center Edition 2005

o Microsoft Windows XP Tablet PC Edition SP2

o Microsoft Windows XP Embedded SP2

o Microsoft Windows Server 2003, Standard Edition SP1

o Microsoft Windows Server 2003, Enterprise Edition SP1

o Microsoft Windows Server 2003, Datacenter Edition SP1

o Microsoft Windows Server 2003 R2, Standard Edition

o Microsoft Windows Server 2003 R2, Enterprise Edition

o Microsoft Windows Server 2003 R2, Datacenter Edition

o Windows Vista Home Basic

o Windows Vista Home Premium

o Windows Vista Business

o Windows Vista Enterprise

o Windows Vista Ultimate

Mobile devices

· Microsoft Windows CE 5.0

· Microsoft Windows Embedded CE 6.0

· Windows Mobile 2003 Software for Pocket PC

· Windows Mobile 5.0

6. Deploying SQL Server Compact Edition 3.5 CTP Applications.

This section describes support for deploying SQL Server Compact Edition applications.

SQL Server Compact Edition Desktop Deployment Support in Visual Studio

You can deploy a SQL Server Compact Edition application to a desktop computer or a Tablet PC by using ClickOnce support in Visual Studio. DataDirectory substitution string also simplifies deploying an application. For more information about ClickOnce and DataDirectory, see the Installing a Development Environment and Installing SQL Server Compact Edition on a Desktop and a Tablet PC topics in SQL Server Compact Edition Books Online and Microsoft Knowledge Base article 920700.

SQL Server Compact Edition Mobile Devices Deployment Support in Visual Studio

You can use Visual Studio to deploy a SQL Server Compact Edition application to either an emulator or a device in the following ways.

A Pocket PC 2003 application can be deployed on:

· Pocket PC 2003 Device

· Pocket PC 2003 Emulator

· Pocket PC 2003 SE VGA Emulator

· A Windows CE 5.0 application can be deployed on:

· Windows Mobile Version 5.0 Pocket PC Device

· Windows Mobile Version 5.0 Pocket PC Emulator

· Windows Mobile Version 5.0 Pocket PC Phone Edition GSM (virtual radio) Emulator

· Windows Mobile Version 5.0 Pocket PC Phone Edition GSM VGA (virtual radio) Emulator

· Windows Mobile Version 5.0 Pocket PC VGA Emulator

· Windows Mobile Version 5.0 Smartphone Device

· Windows Mobile Version 5.0 Smartphone GSM (virtual radio) Emulator

· Windows Mobile Version 5.0 Smartphone GSM QVGA (virtual radio) Emulator

Windows CE 5.0 Devices

· A Windows Mobile Version 5.0 Pocket PC application can be deployed on:

· Windows Mobile Version 5.0 Pocket PC Device

· Windows Mobile Version 5.0 Pocket PC Emulator

· Windows Mobile Version 5.0 Pocket PC Phone Edition GSM (virtual radio) Emulator

· Windows Mobile Version 5.0 Pocket PC Phone Edition GSM VGA (virtual radio) Emulator

· Windows Mobile Version 5.0 Pocket PC VGA Emulator

· A Windows Mobile Version 5.0 Smartphone application can be deployed on:

· Windows Mobile Version 5.0 Smartphone Device

· Windows Mobile Version 5.0 Smartphone GSM (virtual radio) Emulator

· Windows Mobile Version 5.0 Smartphone GSM QVGA (virtual radio) Emulator

7. Uninstalling this CTP on a machine with VS 2005 installed will break the VS 2005 Publish Property Pages.

In VS 2005, create a brand new VB App and select the Project Properties, the “Publish” tab in the Project properties will not be there. In VS 2005, create a brand new VB App and select the Project Properties, the “Publish” tab in the Project properties will not be there.

To resolve this issue

Enter the following registry keys into the registry:

[HKEY_LOCAL_MACHINE\Software\Microsoft\VisualStudio\8.0\CLSID\{CC4014F5-B18D-439C-9352-F99D984CCA85}]

@="Microsoft.VisualStudio.Publish.Framework.PublishPropPageComClass"

"ThreadingModel"="Both"

"Class"="Microsoft.VisualStudio.Publish.Framework.PublishPropPageComClass"

"RuntimeVersion"="v2.0.30908"

"Assembly"="Microsoft.VisualStudio.Publish, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"

[HKEY_LOCAL_MACHINE\Software\Microsoft\VisualStudio\8.0\CLSID\{EFB9A924-3760-49AF-B363-5A82DF3A960C}]

@="Microsoft.VisualStudio.Publish.Framework.PublishProject"

"ThreadingModel"="Both"

"Class"="Microsoft.VisualStudio.Publish.Framework.PublishProject"

"RuntimeVersion"="v2.0.30908"

"Assembly"="Microsoft.VisualStudio.Publish, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"

8. Using Visual Studio Tools for Office with Microsoft Office.

To take advantage of Visual Studio Tools for Office (VSTO) in this release, you need to install either Microsoft Office 2003 or the RTM version of 2007 Microsoft Office System. This release does not work with pre-release versions of Office 2007. It is also not recommended to install both Office 2003 and Office 2007 on the same development machine.

If you do not have 2007 Microsoft Office RTM, you can download the trial version at: http://office.microsoft.com/en-us/help/HA101687261033.aspx.

When using Visual Studio 2007 with Visual Studio 2005 or Visual Studio Tools for Office 2005 SE installed on a single development machine, please consider the following issues:

· Side-by-side scenarios are not fully implemented for Office projects in this release and it is recommended that you do not install this release of VS 2007 on a machine with VS 2005 if you plan to work with Office projects.

· Use of Office 2003 is not supported when both VS 2005 and this release of VS 2007 are on the same machine.

· Upgrading existing VS 2005 Office projects does not work properly in this release. It is recommended that you do not attempt to upgrade projects with this release.

· Uninstalling this release of VS 2007 from a machine that also contains VS 2005 will require VS 2005 to be repaired. You can repair your VS 2005, VSTO 2005 SE and Office 2003 environment by doing the following:

o Uninstall this release of Visual Studio 2007 completely.

o Uninstall Visual Studio Tools for Office 2007 Runtime if still on the machine.

o Repair VSTOR.exe Note: a repair of VS 2005 or VSTO 2005 SE might be necessary for other Visual Studio 2005 features as well.

To resolve this issue

No workaround is available for this issue

9. Visual Studio Tools for Office SharePoint Workflow requires configuration to work properly in this release.

To use the SharePoint workflow tools in this release, you must install the following products and components in the specific order listed:

1. Windows 2003 Server (updated with .NET Framework 2.0), for information: http://www.microsoft.com/windowsserver2003/evaluation/features/comparefeatures.mspx

2. Internet Information Services (IIS), for information: http://technet2.microsoft.com/windowsserver/en/technologies/featured/iis/default.mspx

3. .NET Framework 3.0 with Windows Workflow runtime, for information: http://www.microsoft.com/downloads/details.aspx?FamilyId=10CC340B-F857-4A14-83F5-25634C3BF043&displaylang=en

4. Visual Studio Tools for Office Codename "Orcas"

5. Windows SDK (installs Windows Workflow design time components), for information: http://www.microsoft.com/downloads/details.aspx?FamilyId=C2B1E300-F358-4523-B479-F53D234CDCCF&displaylang=en

6. Optional: SMTP Service; Installing this service allows you to use SharePoint’s email-enabled features. Consult SharePoint product documentation to learn more about these capabilities. For information: http://technet2.microsoft.com/WindowsServer/f/?en/library/7cb16105-73d6-459e-b9f8-015b2f2ac00d1033.mspx

7. Install Microsoft Office SharePoint Server 2007, for information:: http://office.microsoft.com/en-us/sharepointserver/FX100492001033.aspx

To resolve this issue

No workaround is available for this issue.

10. Team Foundation Server Upgrade.

This release does not support an upgrade or data migration from Visual Studio 2005 Team Foundation Server.

II. Product Issues

1. WCF host program throws an exception when closing the host.

When ServiceHost.Close() is called, it throws the following exception:

System.BadImageFormatException was unhandled

Message="An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)"

Source="System.ServiceModel"

Note: this will affect the shutdown/closing of all WCF applications. For self hosted applications this will be hit on closing the Service Host. This will be fixed by Beta1.

To resolve this issue

Catch and handle that exception type when calling ServiceHost.Close().

2. WCF Net.Pipe services cannot be hosted in IIS.

Net.Pipe WCF services hosted in IIS cannot be activated, since incoming message will not be delivered to the WCF service. Net.pipe Listener Adapter,which receives activation requests over net.pipe protocol ,is not functional.

To resolve this issue

Run the WCF service in an EXE or Windows NT Service.

3. wcfSvchost.exe requires Administrator privileges.

The wcfSvcchost.exe tool requires administrator privileges to run. The WCF service library template in Visual Studio will not run correctly if wcfSvchost.exe is not available.

To resolve this issue

Run Visual Studio using an Administrator account when authoring services using wcfSvchost.exe.

4. Intellisense for WCF configuration is not available in this release.

To resolve this issue

No workaround is available for this issue.

5. WCF Service Configuration Editor doesn’t exist in VS tools menu.

The svcConfigEditor.exe is not available in the Tools menu of Visual Studio. The tool cannot be started from within Visual Studio.

To resolve this issue

Install the Windows SDK, which includes the editor. The svcConfigEditor.exe is located in the Windows Start menu.

6. WCF features are not disabled in .Net 2.0 projects or websites.

The WCF tools and templates are erroneously available in projects targeted at .Net 2.0. WCF requires .Net 3.0 or higher. Using WCF in a .Net 2.0 project is not possible.

To resolve this issue

When using WCF features the target framework version must be set to 3.0 or higher.

7. SQL Server Compact Edition: No support for server-generated keys and server-generated values.

When using 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 (if a default value has been specified as part of the column definition) when an entity is created or updated.

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.

For more information, see the SQL Server Compact Edition Forum.

8. SQL Server Compact Edition: Paging queries not supported.

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 may 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 paging queries.

For more information, see the SQL Server Compact Edition Forum.

9. SQL Server Compact Edition: Full outer joins not supported.

Entity SQL supports multiple joins including inner joins, left outer joins and full outer joins.

This release of SQL Server Compact Edition does not support Entity SQL queries with full outer joins that use the ADO.NET Entity Framework. As an example, the following query will not be supported:

SELECT c.Name, c.Id, o.Id

FROM NW.Customers AS c full

OUTER JOIN NW.Orders AS o ON c.Id = o.CustomerId

For more information, see the SQL Server Compact Edition Forum.

10. SQL Server Compact Edition: No support for COLLATE subclauses in the ORDER BY clause of an Entity SQL query.

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

For more information, see the SQL Server Compact Edition Forum.

11. SQL Server Compact Edition: No support for command time-outs.

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.

For more information, see the SQL Server Compact Edition Forum.

12. SQL Server Compact Edition: Supports only Unicode strings.

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 <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.

For more information, see the SQL Server Compact Edition Forum.

13. SQL Server Compact Edition: Limited support for Language Integrated Query.

The ADO.NET Entity Framework supports the Language Integrated Query. This release of SQL Server Compact Edition when it is used with the ADO.NET Entity Framework has limited support for Language Integrated Query. The release has been tested for the Entity SQL queries

For more information, see the SQL Server Compact Edition Forum.

14. SQL Server Compact Edition: Time-out in transaction scope.
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 SQL Server Compact Edition database.

To resolve this issue

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

For more information, see the SQL Server Compact Edition Forum.

15. Publish Tab in the Properties Page does not work for Office projects.

On the properties page, selecting the Publish tab will cause Visual Studio to fail.

To resolve this issue

Do not select the Publish tab from the Properties page. Instead, to publish a solution, right-click the project name in the Solution Explorer and select Publish.

16. Office Applications Load Only One Add-in or Customization.

Microsoft Office applications can run only one Visual Studio Tools for Office add-in or customization. After one is loaded, any additional add-in or customization will fail to load.

To resolve this issue

To work around this issue, open the Office project for the first add-in, click the Build menu, and then click Clean to unregister the add-in.

17. Orcas C# LINQ Samples.

The C# LINQ samples for this CTP are embedded in the help files. It is likely that some of these samples will need to be updated from time to time. To get the latest information on the samples, go to the Visual C# Developer Center on MSDN http://msdn2.microsoft.com/en-us/vcsharp/default.aspx and look at this page http://msdn2.microsoft.com/en-us/vcsharp/bb330936.aspx.

18. There is a known performance regression in product startup which may add up to 12 additional seconds to the startup time of Visual Studio, depending on system configuration.

This regression should be fixed in the next update.

19. Working with Project Designer (Project Properties) is unsupported when the CTP is installed on the same machine as VS 2005 or SQL Server 2005.

Project Designer is the feature responsible for configuring application settings, handling application events, managing settings, managing resources, and working with other properties of the project. This feature currently is not supported in the March CTP if the CTP is installed on the same machine (side-by-side) with VS 2005 or SQL Server 2005. This limitation is caused by a known issue in the setup authoring of this component.

To resolve this issue

It is recommended to either:

· Use the March CTP from a VPC image

· Install March CTP to a different machine without VS 2005 or SQL Server 2005

20. Working with Workflow Designer is unsupported when the CTP is installed on the same machine as VS 2005.

This feature currently is not supported in the March CTP if the CTP is installed on the same machine (side-by-side) with VS 2005.

To resolve this issue

It is recommended to either:

· Use the March CTP from a VPC image

· Install March CTP to a different machine without VS 2005

21. Visual J# Orcas Express Edition and Visual Web Developer Orcas Express Edition are not supported.

“ADO.NET vNext” only supports Visual Basic “Orcas” Express, Visual C# “Orcas” Express and Visual Studio “Orcas” Standard and higher SKUs.

22. Root namespace must be empty in Visual Basic Model Object library projects.

To resolve this issue

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.

23. ADO.NET Entity Framework: Model and Target must be in different namespaces.

To resolve this issue

The Namespace attribute in the Schema element of the Model (.csdl) file should be different from the one in the Target (.ssdl) file. "ADO.NET vNext" throws an exception at runtime if they are the same.

24. ADO.NET Entity Framework: 1:1 relationships are not supported.

1:1 relationships cannot be mapped into the conceptual models of the Entity Data Model.

To resolve this issue

If a 1:1 relationship is present in the database, it can be mapped to a single entity (using entity splitting) if the two tables share the same primary keys.

25. Support for ASP.NET projects.

Assemblies containing ADO.NET Entity Data Models must be compiled outside the ASP.NET website project. They can be used in ASP.NET projects by copying the assembly into the “bin” website directory or adding a reference to them. The CSDL, MSL and SSDL files should also be copied into “bin”. Please refer to the ADO.NET vNext Web sample for more information about how to deploy, locate and load the appropriate CSDL, MSL and SSDL files.

26. Entity Framework requires all tables to have primary keys.

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. The wizard will mark these places in the files with element names prefixed with the string "TODO". The wizard also adds warning messages to the Visual Studio task window.

27. LINQ to Entities sample: Working with the modified database.

The sample application should automatically mount the modified Northwind Database. If it is not successful or you have a different version you'd like to use, you can manually mount the database and change the connection string. To change the database that is used by the LINQ to Entities Samples, please change the connection string contained in the “Provider Connection String” setting of the Entity Framework connection string. If you attempt to use the App.Config for a connection string, please see the documentation.

28. LINQ to Entities sample: Adding or changing Entity Framework files.

If you add or change Entity Framework files (e.g., csdl, msl, etc), make sure to have the "Copy To Output" setting in Visual Studio set so that the files are included with any builds.

29. LINQ to SQL assembly is not yet enabled for partial trust.

In this CTP, LINQ to SQL cannot be used in ASP.NET medium trust scenarios.

To resolve this issue

Full trust is required in this CTP. We are working on enabling partial trust.

30. SQL Server Authentication in ADO.NET Entity Data Model wizard.

There is a known issue in the ADO.NET Entity Data Model wizard with using SQL Server authentication and choosing “Yes, include the sensitive data in the connection string”. The wizard disappears after you click “OK”.

To resolve this issue

Either use Windows Authentication or choose “No, exclude sensitive data from the connection string”. This issue is being targeted to be fixed for ORCAS Beta1.

31. Config changes needed to enable Workflow hosting in IIS.

The XOML build provider in web.config has an extra asterisk character that needs to removed.

To resolve this issue

· Go to C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG

· Open web.config

· Look for the following entry under <buildProviders>:

· Change it to

32. Smart Device Unit Testing - MSTest doesn’t work if project contains references to certain NetCF assemblies.

If your project contains references to .Net Compact Framework assemblies which are not present in the full desktop .Net framework (Eg: Microsoft.WindowsMobile.DirectX.dll), running smart device tests through MSTest throws an error.

To resolve this issue

Set ‘CopyLocal’ to true on these references.

33. Smart Device Unit Testing – ‘Create Unit Test’ dialog does not show methods from NetCF 3.5.

When you right click on a method in a smart device project and invoke the ‘Create Unit Test’ dialog, you will not find methods from NetCF 3.5 listed

To resolve this issue

There is no workaround currently. This issue will be fixed in a future release.

34. Smart Device Unit Testing – Generating unit tests for non-public members causes build failures.

Generating unit test code for non-public members throws build errors.

To resolve this issue

You need to write your own code using System.Reflection to access private/protected members. This will be fixed in a future release.

35. The Object Relational Designer (O/R Designer).

The file format for the DBML file generated by the O/R Designer is in the process of being changed. The current format that uses GUIDS will be replaced by a more comprehensible format. There is currently no plan to provide upgrade tools that migrate to subsequent file formats. Entity classes created with the March CTP release of the O/R Designer will not be supported in subsequent releases.

36. ASP.NET Applications fail to run in partial trust

Due to a product issue in this CTP release, attempts to run ASP.NET applications in a partially trusted AppDomain will cause requests to fail with the following exception:

[SecurityException: Request failed.]

System.ServiceModel.ServiceHostingEnvironment.EnsureInitialized() System.ServiceModel.Activation.HostedHttpModuleRequestAsyncResult.BeginRequest()

System.ServiceModel.Activation.HttpModule.StartBeginProcessRequest(Object sender, EventArgs e, AsyncCallback cb, Object extraData)

System.ServiceModel.Activation.HttpModule.ProcessRequestCore(Object sender, EventArgs e)

System.ServiceModel.Activation.ProcessRequestState.OnCallback(Object sender, EventArgs e)

System.ServiceModel.CallbackStateBase`3.OnCallback(Object o)

System.ServiceModel.PartialTrustHelpers.InvokeWithPerms(PermissionSet perms, WaitCallback callback, Object state)

System.ServiceModel.Activation.HttpModule.ProcessRequest(Object sender, EventArgs e)

System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()

System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

This issue is temporary and will be resolved in future “Orcas” CTP.

To resolve this issue

There are two possible resolutions to this issue:

Grant the ASP.NET application a Trust Level of “Full” (the default). For information about configuring the trust level granted to ASP.NET applications, see the following URL: http://msdn2.microsoft.com/en-us/library/tkscy493(VS.80).aspx

Alternatively, remove the WCF HTTP Module from the ASP.NET Pipeline by adding the following configuration to the application’s web.config file:

<system.web>
<httpModules>

             </httpModules>
          </system.web>

Workaround (2) will disable the use of WCF services from within the affected application.

37. Adding a WCF service to the ASP.NET AJAX Script Manager Control does not work in Debug mode.

In the Orcas release, it is possible to use the Windows Communication Foundation to write services that may be consumed from AJAX-enabled web 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 behaves differently in Release and Debug deployment modes. In this CTP release, WCF services are incompatible with the Debug mode. This issue will be addressed in future releases.

To resolve this issue

Set the ScriptMode property of the Script Manager control to “Release” if the control contains references to any AJAX-enabled WCF services.

38. The WebScriptServiceHostFactory class does not work with HTTP GET operations.

The WebScriptServiceHostFactory class is designed to allow Windows Communication Foundation services to be used to serve data to AJAX-enabled web pages without having to write WCF configuration settings. In this CTP release, the WebScriptServiceHostFactory class does not work with WCF operations that have been configured with the HttpTransferContractAttribute attribute to use the HTTP GET verb. You may get an error about an AddressFilter mismatch if you attempt to use it with such operations. This issue will be addressed in future releases.

To resolve this issue

One way to resolve the issue is to avoid using HTTP GET operations and use HTTP POST instead. If this is impossible, then instead of using the WebScriptServiceHostFactory you should create a WCF configuration section in web.config or another config file as appropriate and use it to enable an AJAX endpoint (taking into account the other release note about endpoint URLs that end directly with “.svc”)

39. WCF AJAX endpoints at URLs immediately ending with “.svc” do not work with HTTP GET operations.

In the Orcas release, it is possible to use the Windows Communication Foundation to write IIS-hosted services that may be consumed from AJAX-enabled web pages. These services may be hosted at endpoints with URLs 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 CTP 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. This issue will be addressed in future releases.

To resolve this issue

There are three ways to resolve this issue. One is to use URLs with suffixes (remember to include the suffix if using such a URL in the ASP.NET AJAX Script Manager control). Another is to avoid using HTTP GET operations and use HTTP POST instead. Finally, it is possible to use a URL without a suffix if a “dot” character is used as the relative address in the WCF service configuration. That is, instead of specifying the endpoint as <endpoint address=”” …>, specify it as <endpoint address=”.” …>

40. Add Web Reference to Projects that Target the .NET Framework 3.0/3.5.

Adding a Web reference to a project that targets the .NET Framework 3.0/3.5 is not possible from the 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’ in the Application tab. Once the project has been downgraded to .NET Framework 2.0, add a Web reference. Then upgrade the project to target the .NET Framework 3.0/3.5. From that point on, the Web reference menu items will be available on the Project and Web References folder in the Solution Explorer.

41. Add Web Reference to Web sites that Target the .NET Framework 3.0/3.5.

Adding a Web reference to a web site that targets the .NET Framework 3.0/3.5 is not possible from the Solution Explorer if a Web reference does not already exist.

To resolve this issue

In the Solution Explorer, right-click and add an ‘App’ ASP.NET Folder. The folder will have right-click menu items for adding and updating a Web reference.

42. Compilation fails when using WF Declarative Rule Conditions or Policy Activity.

When you use declarative rule conditions or the out-of-box policy activity in a workflow project, the project will not compile. This is due to an issue in the CTP’s workflow project templates where embedded resources (e.g. .rules file) do not get complied with the project. As a result, the compilation will fail since the activities will not be able to locate the declarative conditions and the rule set previously defined in the .rules file.

To workaround this issue

To workaround this issue, use code conditions instead of declarative rule conditions. A Policy From File Activity sample posted on http://go.microsoft.com/fwlink/?LinkId=83545 will show you how to use rule sets within your workflow application in an alternative way than the out-of-box policy activity.

43. Unable to open/create/execute Visual J# applications/projects/solutions.

The run-time and design-time features for the Visual J# language are not supported in the March CTP Release. For more information, go to: http://msdn.microsoft.com/vjsharp/default.aspx

To resolve this issue

No workaround is available for this issue.

44. Unable to use Object Test Bench.

The Object Test Bench feature for Visual C#, Visual Basic and Visual J# languages is not supported in the March CTP Release.

To resolve this issue

No workaround is available for this issue.

45. Visual Basic 101 Samples.

The Visual Basic 101 samples may not run immediately. To address the compilation errors you see:

1. Add the statements ‘Option Strict Off’ and ‘Option Infer On’ to the top of DLinQSamples.vb, LinQSamples.vb, XLinQSamples.vb, and XQueryUseCases.vb

2. In Northwind.vb, do a search and replace ‘DLinQ’, with ‘LinQ’

3. Rebuild the application

46. WPF Designer (“Cider”) limitations and issues.

The latest information on limitations and issues when using the WPF designer (“Cider”) in the March CTP can be found on the Cider wiki on Channel9.

47. Expression Blend^TM projects fail to migrate correctly when opened in Visual Studio.

Projects created using Microsoft Expression Blend™ are not migrated correctly when opened in Visual Studio. The project will still open in Microsoft Expression Blend™ and Visual Studio but will not build successfully in either product.

To resolve this issue

Edit the project file in Notepad and add “ToolsVersion=2.0” to the first line before opening the project in Visual Studio. For example:

This change will prevent project upgrade. Projects will open and build in both Blend and Visual Studio but will not be upgraded to VS Orcas projects. As a result some Orcas project features may not work correctly.

48. Expression Blend^TM cannot build Visual Studio Orcas solutions and projects.

Solutions and projects created using Visual Studio Orcas will not build in Microsoft Expression Blend™. Solutions and projects will open successfully in Microsoft Expression Blend™ but will not build.

To resolve this issue

Build the solution in Visual Studio.

49. Team Foundation Server Compatibility.

This release is not backward-compatible with Visual Studio 2005 Team Foundation Server. You cannot run Team Explorer (March 2007 CTP) against a server running Visual Studio 2005 Team Foundation Server. Similarly, you cannot run Visual Studio 2005 Team Explorer against a server running Team Foundation Server (March 2007 CTP).

50. The Team Foundation Server Readme and Known Issues documents found on the Team Foundation media are for Visual Studio 2005 Team Foundation Server and are out-of-date.

Some issues may be missing, incorrect, or fixed in the Team Foundation Server (March 2007 CTP).

51. Microsoft Synchronization Services for ADO.NET Books Online.

Customers can get updated documentation for Microsoft Synchronization Services for ADO.NET from http://go.microsoft.com/fwlink/?LinkId=80742.

52. VC Libraries

ATL Server has been moved to the Shared Source Project. It is planned to be released on CodePlex.com in March of 2007. For more information please visit http://www.msdn.com/visualc and search “ATL Server Shared Source”.

53. Supporting derived and associated CIM classes from WMI Provider Extension 2.0.

.NET developers looking to leverage existing CIM classes to create their own CIM application classes (created from the .NET attribution implemented by the WMI Provider Extension 2.0) won’t be able to achieve this in this current CTP release. This will be possible in a next version of Orcas. Currently, CIM classes created from the .NET attribution cannot be derived (they must be created directly from the Root of the CIM namespace)

54. Required .NET Framework Updates do not install on Vista

· Websites which use C#3.0/VB9.0 language constructs will fail at runtime.

· C# and VB projects will produce a compiler warning on every build.

This warning can safely be ignored – but indicates that a required component was not installed, and that a manifest to tell Vista UAC to treat the app as AsInvoker has not been inserted into the resulting assembly.