Visual Studio Code Name “Orcas” Release Notes © 2007 Microsoft Corporation
January 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.
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"
2.
Uninstalling this CTP on a machine with VS 2005 installed will break PreRequisites button on a Setup project
In VS 2005, create a brand new Setup
Project. Go to the Setup Project
properties and you will see a PreRequisites
button. Pressing the button willnot work.
To resolve
this issue
Enter the following keys in
the registry:
Modify the InprocServer32 to
the correct path to your windows installation first
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\CLSID\{A6383CAD-E8B2-422A-BEBF-44CBB7CE73AA}]
@="Microsoft.VisualStudio.Publish.Library.Bootstrapper.ComBootstrapperDialog"
"InprocServer32"="C:\\WINNT\\system32\\mscoree.dll"
"ThreadingModel"="Both"
"Class"="Microsoft.VisualStudio.Publish.Library.Bootstrapper.ComBootstrapperDialog"
"Assembly"="Microsoft.VisualStudio.Publish, Version=8.0.0.0,
Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\CLSID\{A6383CAD-E8B2-422A-BEBF-44CBB7CE73AA}\Implemented
Categories]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\CLSID\{A6383CAD-E8B2-422A-BEBF-44CBB7CE73AA}\Implemented
Categories\{62C8FE65-4EBB-45E7-B440-6E39B2CDBF29}]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\CLSID\{A6383CAD-E8B2-422A-BEBF-44CBB7CE73AA}\InprocServer32]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\CLSID\{A6383CAD-E8B2-422A-BEBF-44CBB7CE73AA}\InprocServer32\8.0.0.0]
"Class"="Microsoft.VisualStudio.Publish.Library.Bootstrapper.ComBootstrapperDialog"
"Assembly"="Microsoft.VisualStudio.Publish, Version=8.0.0.0,
Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\CLSID\{A6383CAD-E8B2-422A-BEBF-44CBB7CE73AA}\ProgId]
@="Microsoft.VisualStudio.Publish.Library.Bootstrapper.ComBootstrapperDialog"
3.
Uninstalling this CTP on a machine with VS 2005 installed will break
Application Verifier functionality
In VS 2005, create a new or
open an existing VC++ project, go to the Debug menu and click on "Start
With Application Verifier". The application is launched under the debugger
without enabling application verifier. There will not be any visible failure,
but the application will be run under a normal debug session as opposed to an
application verifier enabled debug session.
To resolve
this issue
Enter the following registry keys in to the registry or
Repair/ReInstall VS 2005:
In the below settings, please replace "D:\Program
Files\Microsoft Visual Studio 8" to where VS 2005 is installed on your
machine
On a
32 bit machine:
(You can copy the
following into a .reg file and double click on the
file to update the registry. Please replace "D:\Program Files\Microsoft
Visual Studi 8" to where VS 2005 is installed on
your machine)
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\CLSID\{80243527-713A-4A9B-A75D-039ECCE6E9D9}]
@="Application
Verifier Remote Debug Engine Helper"
[HKEY_CLASSES_ROOT\CLSID\{80243527-713A-4A9B-A75D-039ECCE6E9D9}\InProcServer32]
@="D:\\Program
Files\\Microsoft Visual Studio
8\\Common7\\Packages\\Debugger\\avvspkdh.dll"
"ThreadingModel"="Both"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{80243527-713A-4A9B-A75D-039ECCE6E9D9}]
@="Application
Verifier Remote Debug Engine Helper"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{80243527-713A-4A9B-A75D-039ECCE6E9D9}\InProcServer32]
@="D:\\Program
Files\\Microsoft Visual Studio 8\\Common7\\Packages\\Debugger\\avvspkdh.dll"
"ThreadingModel"="Both"
[HKEY_CLASSES_ROOT\CLSID\{B7572133-00C2-46FA-870E-984EF818B382}]
@="PSFactoryBuffer"
[HKEY_CLASSES_ROOT\CLSID\{B7572133-00C2-46FA-870E-984EF818B382}\InProcServer32]
@="D:\\Program
Files\\Microsoft Visual Studio 8\\Common7\\Packages\\Debugger\\avvspkdh.dll"
"ThreadingModel"="Both"
[HKEY_CLASSES_ROOT\Interface\{B7572133-00C2-46FA-870E-984EF818B382}]
@="IAvrfResourceEnum"
[HKEY_CLASSES_ROOT\Interface\{B7572133-00C2-46FA-870E-984EF818B382}\NumMethods]
@="7"
[HKEY_CLASSES_ROOT\Interface\{B7572133-00C2-46FA-870E-984EF818B382}\ProxyStubClsid32]
@="{B7572133-00C2-46FA-870E-984EF818B382}"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{B7572133-00C2-46FA-870E-984EF818B382}]
@="PSFactoryBuffer"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{B7572133-00C2-46FA-870E-984EF818B382}\InProcServer32]
@="D:\\Program
Files\\Microsoft Visual Studio
8\\Common7\\Packages\\Debugger\\avvspkdh.dll"
"ThreadingModel"="Both"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{B7572133-00C2-46FA-870E-984EF818B382}]
@="IAvrfResourceEnum"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{B7572133-00C2-46FA-870E-984EF818B382}\NumMethods]
@="7"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{B7572133-00C2-46FA-870E-984EF818B382}\ProxyStubClsid32]
@="{B7572133-00C2-46FA-870E-984EF818B382}"
[HKEY_CLASSES_ROOT\Interface\{36250171-9F91-403B-9312-3D285469C314}]
@="IAvrfResourceEnumCallback"
[HKEY_CLASSES_ROOT\Interface\{36250171-9F91-403B-9312-3D285469C314}\NumMethods]
@="4"
[HKEY_CLASSES_ROOT\Interface\{36250171-9F91-403B-9312-3D285469C314}\ProxyStubClsid32]
@="{B7572133-00C2-46FA-870E-984EF818B382}"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{36250171-9F91-403B-9312-3D285469C314}]
@="IAvrfResourceEnumCallback"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{36250171-9F91-403B-9312-3D285469C314}\NumMethods]
@="4"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{36250171-9F91-403B-9312-3D285469C314}\ProxyStubClsid32]
@="{B7572133-00C2-46FA-870E-984EF818B382}"
On a
64 bit machine:
(You can copy the following into a .reg
file and double click on the file to update the registry. Please replace
"D:\Program Files\Microsoft Visual Studio 8" to where VS 2005 is
installed on your machine
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\CLSID\{80243527-713A-4A9B-A75D-039ECCE6E9D9}]
@="Application
Verifier Remote Debug Engine Helper"
[HKEY_CLASSES_ROOT\CLSID\{80243527-713A-4A9B-A75D-039ECCE6E9D9}\InProcServer32]
@="D:\\Program
Files\\Microsoft Visual Studio 8\\Common7\\IDE\\Remote
Debugger\\x64\\AvVsPkDH.dll"
"ThreadingModel"="Both"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{80243527-713A-4A9B-A75D-039ECCE6E9D9}]
@="Application
Verifier Remote Debug Engine Helper"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{80243527-713A-4A9B-A75D-039ECCE6E9D9}\InProcServer32]
@="D:\\Program
Files\\Microsoft Visual Studio 8\\Common7\\IDE\\Remote
Debugger\\x64\\AvVsPkDH.dll"
"ThreadingModel"="Both"
[HKEY_CLASSES_ROOT\CLSID\{B7572133-00C2-46FA-870E-984EF818B382}]
@="PSFactoryBuffer"
[HKEY_CLASSES_ROOT\CLSID\{B7572133-00C2-46FA-870E-984EF818B382}\InProcServer32]
@="D:\\Program
Files\\Microsoft Visual Studio 8\\Common7\\IDE\\Remote
Debugger\\x64\\AvVsPkDH.dll"
"ThreadingModel"="Both"
[HKEY_CLASSES_ROOT\Interface\{B7572133-00C2-46FA-870E-984EF818B382}]
@="IAvrfResourceEnum"
[HKEY_CLASSES_ROOT\Interface\{B7572133-00C2-46FA-870E-984EF818B382}\NumMethods]
@="7"
[HKEY_CLASSES_ROOT\Interface\{B7572133-00C2-46FA-870E-984EF818B382}\ProxyStubClsid32]
@="{B7572133-00C2-46FA-870E-984EF818B382}"
[HKEY_CLASSES_ROOT\Wow6432Node\Interface\{B7572133-00C2-46FA-870E-984EF818B382}]
@="IAvrfResourceEnum"
[HKEY_CLASSES_ROOT\Wow6432Node\Interface\{B7572133-00C2-46FA-870E-984EF818B382}\NumMethods]
@="7"
[HKEY_CLASSES_ROOT\Wow6432Node\Interface\{B7572133-00C2-46FA-870E-984EF818B382}\ProxyStubClsid32]
@="{B7572133-00C2-46FA-870E-984EF818B382}"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{B7572133-00C2-46FA-870E-984EF818B382}]
@="PSFactoryBuffer"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{B7572133-00C2-46FA-870E-984EF818B382}\InProcServer32]
@="D:\\Program
Files\\Microsoft Visual Studio 8\\Common7\\IDE\\Remote
Debugger\\x64\\AvVsPkDH.dll"
"ThreadingModel"="Both"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{B7572133-00C2-46FA-870E-984EF818B382}]
@="IAvrfResourceEnum"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{B7572133-00C2-46FA-870E-984EF818B382}\NumMethods]
@="7"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{B7572133-00C2-46FA-870E-984EF818B382}\ProxyStubClsid32]
@="{B7572133-00C2-46FA-870E-984EF818B382}"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\Interface\{B7572133-00C2-46FA-870E-984EF818B382}]
@="IAvrfResourceEnum"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\Interface\{B7572133-00C2-46FA-870E-984EF818B382}\NumMethods]
@="7"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\Interface\{B7572133-00C2-46FA-870E-984EF818B382}\ProxyStubClsid32]
@="{B7572133-00C2-46FA-870E-984EF818B382}"
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\Interface\{B7572133-00C2-46FA-870E-984EF818B382}]
@="IAvrfResourceEnum"
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\Interface\{B7572133-00C2-46FA-870E-984EF818B382}\NumMethods]
@="7"
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\Interface\{B7572133-00C2-46FA-870E-984EF818B382}\ProxyStubClsid32]
@="{B7572133-00C2-46FA-870E-984EF818B382}"
[HKEY_CLASSES_ROOT\Interface\{36250171-9F91-403B-9312-3D285469C314}]
@="IAvrfResourceEnumCallback"
[HKEY_CLASSES_ROOT\Interface\{36250171-9F91-403B-9312-3D285469C314}\NumMethods]
@="4"
[HKEY_CLASSES_ROOT\Interface\{36250171-9F91-403B-9312-3D285469C314}\ProxyStubClsid32]
@="{B7572133-00C2-46FA-870E-984EF818B382}"
[HKEY_CLASSES_ROOT\Wow6432Node\Interface\{36250171-9F91-403B-9312-3D285469C314}]
@="IAvrfResourceEnumCallback"
[HKEY_CLASSES_ROOT\Wow6432Node\Interface\{36250171-9F91-403B-9312-3D285469C314}\NumMethods]
@="4"
[HKEY_CLASSES_ROOT\Wow6432Node\Interface\{36250171-9F91-403B-9312-3D285469C314}\ProxyStubClsid32]
@="{B7572133-00C2-46FA-870E-984EF818B382}"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{36250171-9F91-403B-9312-3D285469C314}]
@="IAvrfResourceEnumCallback"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{36250171-9F91-403B-9312-3D285469C314}\NumMethods]
@="4"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{36250171-9F91-403B-9312-3D285469C314}\ProxyStubClsid32]
@="{B7572133-00C2-46FA-870E-984EF818B382}"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\Interface\{36250171-9F91-403B-9312-3D285469C314}]
@="IAvrfResourceEnumCallback"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\Interface\{36250171-9F91-403B-9312-3D285469C314}\NumMethods]
@="4"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\Interface\{36250171-9F91-403B-9312-3D285469C314}\ProxyStubClsid32]
@="{B7572133-00C2-46FA-870E-984EF818B382}"
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\Interface\{36250171-9F91-403B-9312-3D285469C314}]
@="IAvrfResourceEnumCallback"
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\Interface\{36250171-9F91-403B-9312-3D285469C314}\NumMethods]
@="4"
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\Interface\{36250171-9F91-403B-9312-3D285469C314}\ProxyStubClsid32]
@="{B7572133-00C2-46FA-870E-984EF818B382}"
4. Microsoft
Visual J# Redistributable Package is not installed.
Installation of Microsoft Visual J# Redistributable Package is not supported in the January 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 upgrade 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 Upgrade 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.
5. Java Language Conversion
Assistant is not installed.
Installation of the Java Language Conversion Assistant tool is not supported in the January 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 upgrade 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 Upgrade 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
6. 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:
·
Uninstall
this release of Visual Studio 2007 completely.
·
Uninstall
Visual Studio Tools for Office 2007 Runtime if still on the machine.
·
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
1. 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.
2. Incorrect Documentation
For Query Variables in LINQ
In the MSDN documentation for LINQ, under
"Introduction to LINQ Queries" and elsewhere, it is stated that the
query variable receives and stores the query
results when the query is executed. This is incorrect and will be
corrected in future versions of the documentation. In fact, the concrete
sequences returned from a query invocation are accessed through the iteration
variable in the foreach loop. The query
variable itself does not store an actual sequence of
values unless it is explicitly converted (cast) to a List<T> (List
Of T in Visual Basic) or Array instance through a call to the ToList or ToArray extension
method. The separation of the query from the results is a fundamental
principle of the LINQ design. Among other benefits it enables queries to be
reused any number of times, and to be modified after they are initially
created, either prior to or after execution.
To resolve
this issue
The issue is
with the documentation, not with the product bits and will be corrected in
future releases of the documentation.
3. Visual Basic Upgrade Wizard
causes Unexpected Exception
Running the Visual Basic
Upgrade Wizard by opening a Visual Basic 6.0 project from the File / Open menu
causes 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: 80080005.
To resolve
this issue
At this time there is no
work around for this problem.
4. 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.
To resolve
this issue
ADO.NET Samples can be downloaded
online. The samples provide simple examples of programming console, web, and winforms 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=5C12FE07-E646-49C2-887F-8CC070B37247&displaylang=en
into the browser.
6. 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 January 2007 CTP.
7. No ADO.NET tools support for the
Orcas January 2007 CTP
To resolve
this issue
There is no tools support included in the Orcas January
2007 CTP. There is a publicly available ADO.NET
Tools CTP. Please note these tools work with the ADO.NET
August CTP and not the Orcas January 2007 CTP.
8. 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 January 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.
9. 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 January CTP Release.
To resolve
this issue
No workaround is available for this issue.
10. Can’t import Whidbey SDM Designer
files in Orcas.
There is a known bug that
blocks users from importing into the Orcas version of Visual Studio SDM
designer files that were created with the Whidbey version of Visual Studio.
Whidbey files should continue to work with Whidbey and Orcas files should
continue to work with Orcas.
SDM Designer files include
files with these extensions: *.sdm, *.ad, *.sd,
*.dd, and *.ldd.
To resolve
this issue
No workaround is available for this issue.
11. ETW features only work on Windows
All new ETW (Event Tracing for Windows) features can only
work on Microsoft Windows Vista (any SKU) and may not work on older versions of
Windows.
To resolve
this issue
Install Windows Vista.