http://download.microsoft.com/download/1/b/3/1b3f749d-e215-482c-a004-5d9c26c75c92/6.0.6000.0.0.WindowsSDK_Vista_rtm.DVD.Rel.img 
文件大小：1.6G 做好心理准备
1.Framework3.0 开发最权威文档
2.各种调试分析工具

Issues Related to Visual Studio:

  1. On the SP1 release of Visual Studio 2005 a bug exists where performing a project clean will cause the first subsequent project build of your project to generate a compilation error stating InitializeComponents() is not defined. Repeating the project build will succeed. This issue will be fixed in the full release of Orcas.
  2. Users of Visual Studio 2005 on Vista will need to run the Visual Studio Application as an elevated user for some features to to work correctly. It is required that you upgrade to future service packs and other updates availabe through microsoft for Visual Studio 2005.

Issues Related to the Windows Presentation Foundation:

General:

  1. Breakpoints within XAML x:Code tags will first prompt you for the XAML file containing the breakpoint.  Navigate up to the directory where the XAML file resides using the "Find Source" dialog which will show an "Edit and Continue is disabled for this debugging session" dialog.  This can be ignored and breakpoints will work to some degree afterwards.  We are working to improve the breakpoint experience in XAML files for future releases.
  2. Publishing from within the Express products fails if a XAML file is open in the editor as the topmost window.
  3. You must close all generated files that are open in the Visual Studio editor with extensions .g.cs or .g.vb before building your project.  Failure to do so may result in these files not being updated in subsequent builds.
  4. The XAML editor will flicker open and then immediately close the snippet selection box when you choose Insert Snippet from the context menu or from the from the shortcut. To workaround this you need to 'Open With' your .XAML file and use the XML editor. This will allow you to see the available snippets.

XAML Browser Application Development Issues:

  1. Stopping the debugger for a XAML Browser application terminates PresentationHost.exe but orphans the IE window.
  2. Manifest signature validations are now enforced at deployment time for XAML Browser Applications.  Visual Studio has created a test certificate for this project.  If you have an existing certificate that you'd rather use, you may make changes via the Properties->Signing tab for your project.

C# or Visual Basic Editor:

  1. IntelliSense doesn't work for elements with a Name until you build once. The IntelliSense engine relies on the code in the markup-compiler generated code file to know what type the Name is.
  2. To look at the markup-compiler generated code files, press show all files in the Solution Explorer, and then look inside the obj directory.

Xml Editor:

  1. Breakpoints elsewhere in a XAML file won't do anything today. (You can’t breakpoint a <Button> element, for example.)

IntelliSense in XAML (inside the XML editor):

The Windows Presentation Foundation and XAML schemas provided with the .NET Framework 3.0 SDK are not flawless. Today, many things can compile that the schema may not approve of. We also have things that the schema will approve that will not compile.

  1. Referencing 3rd party types in XAML will always cause a validation failure even though the markup and xmlns may be correct. If you build a custom element such as a custom control then IntelliSense in the XML editor will not work unless you hand build an .xsd for that control and put that .xsd in %programfiles%\microsoft visual studio 8\xml\schemas\.
  2. The schema will complain about attribute values that are not properly cased. Although type converters are generally not case sensitive, XML schema has limitations. We've chosen to put the matching case with the object model in the schema.
    DockPanel.Dock="fill"
    will compile, but the schema would prefer this form:
    DockPanel.Dock="Fill"
  3. Some elements will complain with the "content model is empty" warning. Many times, however, the compiler will be able to handle it.
  4. Several valid attributes in the xmlns:x=“http://schemas.microsoft.com/winfx/2006/xaml” namespace will cause a warning such as x:Uid and x:Shared.

Known Problems with Project Templates:

  1. The WPF Designer no longer has a tab for viewing source code. In VB projects this can be confusing because the source code behind the .xaml files is a subnode and the Visual Basic project system hides subnodes from the user. To work around this you should use the "Show All Files" button the solution explorer to access the source files.

Xaml Runtime Parsing Exceptions:

  1. We still have a way to go before the design/compilation process for xaml files gets smoother. In our first version, we aren’t going to be able to do as much content model and attribute value checking during compilation as we would like to. For hand coding xaml, until you start using a visual designer, it will be painful. To make it better, the XamlPresentation2006.xsd file has been significantly enhanced to give you better xaml editing in the xml editor. You can also choose to turn on Debug/Exceptions/Break when an exception is thrown for exceptions that you get when loading your xaml page. This will prevent .g.cs/.g.vb files from being opened which cause bad side effects. We realize that we need to invest significantly in this area in the future.

Documentation (help) for this release is only provided on the local machine. To have a complete set of documentation available, it is required to install the MSDN content that came with Visual Studio 2005. To properly access the documentation, in Visual Studio 2005, go into Tools/Options..., navigate to the Environment/Help/Online page, and make sure either "Try local first, then online" or "Try local only, not online" are selected.

Setup Issues:

  1. A few users have seen a situation where when they try to create a .NET Framework 3.0 project, they get a package load failure for the WPFFlavor.  This appears to be due to having a machine that had earlier versions of Visual Studio, .NET Framework 3.0, and Visual Studio 2005 extensions for .NET Framework 3.0 (WCF & WPF), November 2006 CTP.  If you hit this problem, run "devenv /setup" from the command line and this package load failure should be resolved.
  2. If you want to develop Windows Workflow Foundation projects, you need to install the workflow additions to Visual Studio 2005 separately.
  3. The .NET Framework 3.0 visual designer feature is not supported on the Express SKUs.  We expect to have this working on the Express SKUs when the full Orcas product CTPs start.
  4. The Express SKUs require the Microsoft Windows Vista SDK installed in order to add Service References.
  5. If you want to use the Publish feature for .NET Framework 3.0 projects then you must first copy the .NET Framework 3.0 redistributable packages for both x86 (Dotnetfx3.exe) and x64 (Dotnetfx3_x64.exe) to the %ProgramFiles%\Microsoft Visual Studio 8\SDK\v2.0\BootStrapper\Packages\NETFX30 directory, and then specify .NET Framework 3.0 as an additional prerequisite from the Publish tab in the project properties and specify that a setup program should be created to install the prerequisite components.  Note that until a final release of the .NET Framework 3.0 runtime is available, publishing can only be used for internal testing.
  6. If your project's "Publish Language" targets a non-English locale then you must also copy the appropriate .NET Framework 3.0 redistributable language packs for both 86 and x64 to the directory that matches the project locale under "%ProgramFiles%\Microsoft Visual Studio 8\SDK\v2.0\BootStrapper\Packages\NETFX30" to publish successfully. For example, if your project "Publish Language" is "Japanese" then copy both DotNetFX3LangPackJp.exe and DotNetFX3LangPack_x64Jp.exe to "%ProgramFiles%\Microsoft Visual Studio 8\SDK\v2.0\BootStrapper\Packages\NETFX30\Jpn" before starting the Publish build task. Note that Project Publishing enables bootstrapping the following .NET Framework 3.0 language packs in this preview release: English, German (DE), and Japanese (JP)

Documentation Issues:

  1. Express-specific overview help content is removed for Express products during registration of the Windows SDK documentation into Visual Studio.  We do not plan to fix this until the release of Microsoft Visual Studio Code Name "Orcas", as it would require creating a new set of documentation.  If you need the Express-specific overview content, you will need to uninstall this package (Visual Studio 2005 extensions for .NET Framework 3.0 (WCF & WPF), November 2006 CTP).
  2. If you replace the MSDN Library for Visual Studio 2005 with an MSDN Quarterly Library, you will not have .NET Framework 3.0 documentation integrated into Visual Studio 2005.  If you need the .NET Framework 3.0 documentation, please do not install the MSDN quarterly updates until they include .NET Framework 3.0 documentation.