Visual Studio Code Name “Orcas” Release Notes © 2006 Microsoft Corporation
October 2006 Community Technology Preview
This document lists issues you might encounter while using Microsoft Visual Studio Code Name “Orcas”.
Contents:
I. Visual Studio Code Name “Orcas” Known Issues
I. Visual Studio Code Name “Orcas” Known Issues
1. Visual Studio Tools for Office features require Microsoft Office 12
To use the Office projects in this CTP release of Visual Studio, you will need to install the Office Beta 2 Technical Refresh.
To resolve this issue
You can find the Office 12 Beta 2 Technical Refresh for
download at: http://www.microsoft.com/office/preview/default.mspx
or as a shortcut on the VPC desktop.
2. Samples
on the usage of the ADO.NET stack
To resolve
this issue
ADO.NET Samples can be downloaded
online. The samples provide simple examples of programming console, web and win
forms applications against tables in the Northwind
Database in both VB and C#. If the link does not work, copy and paste http://www.microsoft.com/downloads/details.aspx?FamilyId=C14C451D-7043-44F0-87D7-845F1C238D64&displaylang=en
into
the browser.
3. ADO.NET Entities in this current drop do not support
LINQ
To resolve
this issue
The private CTP of ADO.NET (ADO.NET
August CTP) does
offer a preview of LINQ integration but that functionality does not work with
the Orcas October CTP
4. No ADO.NET tools support
for the Orcas October 2006 CTP
To resolve
this issue
There is no tools support included in the Orcas October
2006 CTP . There is a publicly available ADO.NET
Tools CTP . Please
note these tools are for the ADO.NET
August CTP.
5. LINQ (Language Integrated Query) in Orcas October 2006 CTP
Although parts of the LINQ feature set are available as part of Orcas in the October CTP, the full set of LINQ features is still in development. If you want to try out LINQ, we recommend you continue to use the May LINQ CTP which installs on top of Visual Studio 2005, and which includes more fully featured prototype versions of the C# and VB compilers, as well as the LINQ APIs.
To resolve this issue
2)Use the static methods on System.Query.Sequence
to access the LINQ to Objects functionality
6. Project
Designer Missing Option Infer
Users can now control whether or not a variable’s type
is inferred by typing “Option Infer [On | Off]” at the top of any code
window. Just like the other options (Explicit, Strict etc…), Option Infer
can be set at the project level and also the file level. For this CTP,
the UI support for setting this at the project level is not in place.
To
resolve this issue
By default, Option Infer is turned on at the project
level for all non-upgraded projects. Although you can’t set it through the UI, you can still type “Option Infer On”
or “Option Infer Off” at the individual file level.