<?xml version="1.0" encoding="utf-8" ?>

<CodeSnippets xmlns="http://schemas.microsoft.com/VisualStudio/2005/CodeSnippet">

<CodeSnippet Format="1.0.0">

<Header>

<Title>sourcesafe header</Title>

<Shortcut>header</Shortcut>

<Description>Code snippet for sourcesafe header.</Description>

<Author>Paul van Brenk</Author>

<SnippetTypes>

<SnippetType>Expansion</SnippetType>

</SnippetTypes>

</Header>

<Snippet>

<Declarations>

<Literal />

</Declarations>

<Code Language="csharp" Kind="file" Delimiter="*">

<![CDATA[#region SourceSafe header

*end*]]>

</Code>

</Snippet>

</CodeSnippet>

</CodeSnippets>

File Attachment: sourcesafe_header.zip (550 bytes)

Off course it was released the day after I built a new virtual machine for running the September CTP. Anyway, this release does support Visual Studio 2005 RTM, including the express editions.

Download here:

WinFX Runtime Components November CTP

SDK for WinFX Runtime Components November CTP

Visual Studio 2005 Extensions for WinFX

Visual Studio 2005 Extensions for Windows WorkFlow Foundation

Remember to remove all the old versions of WinFX, VS 2005 and .Net 2.0. Or start with a clean virtual machine.

The installation order is:

• WinFx CTP
• Visual Studio
• Windows WinFX SDK
• VS Extensions for WinFx
• VS Extension for Windows Workflow Foundation

From Rob Relyea’s install guide for the September CTP.

Apparently the allignment bug I encountered in vs2005 can be resolved by changing a number of options in the Formating options:

This is by design. The "Indent Case Contents" option under Tools | Options | Text Editor | C# | Formatting | Indentation indents everything from the opening brace to the closing brace. Our preview window is somewhat misleading since it only shows you the effects of the current formatting option.

In order to set your settings to the way you'd like, you'll need to uncheck both
"Indent Open and Close brace" and
"Indent Case Contents."

You'll also need to have "Place open brace on new line for control blocks" checked under Tools | Options | Text Editor | C# | Formatting | New Lines.

Thanks Karen Liu for helping me solve this.

In Visual Studio 2005 there appears to be an allignment bug in switch/case statements as you can clearly see in this picture:

[bug details in MSDN Product Feedback Center]

If you are as confused as I was, or even more since there is YA-CTP, Kent Sharkey posted a great guide on MSDN [0], which describes what is in each version and how stable each is.

[0] Download Visual Studio 2005 Prerelease Software

Changes have been announced to both the naming of "special" directories (i.e. resources, data, bin ... ) and the compilation model of Asp.net in beta 2 of vs 2005. [0]

Personally I would have preferred a single root for the 'special'-directories, which has been considered, but rejected.

The single root approach was rejected because it did not enable us to support directories located in arbitrary locations in the application tree, such as the local resources directory. 

The default compilation model is changed to keep the markup outside of the compiled binaries. I'm not sure what to think if it, but certainly during development it's a lot easier to work with.

[0] changes in vs 2005 beta 2 for asp.net

Yet Another Community Technology Preview

Yesterday Microsoft released another CTP on MSDN Subscriber Downloads, this one specifically targets the associated SQL 2005 CTP.

This makes the 4th version of VS 2005 available for download:

• Visual Studio 2005 Enterprise Architect Beta 1
• Visual Studio 2005 Community Technology Preview May 2004
• Visual Studio 2005 Beta 1 Refresh with Visual Studio 2005 Team System
• Visual Studio 2005 for the SQL Server 2005 CTP

The version that no longer seems to be available is the PDC 2004 version which worked with that version on Windows Longhorn.

While I like the interval with which these CTPs are released, I really hope that by the time of the next beta, or CTP, it will be more clear which works with what, e.g. can I use the team system stuff with the current CTP of VS and SQL 2005.

I do think this version of VS2005 does support E&C for C#, but I'm not sure, so please correct me if I'm wrong.

The MSDN Library, that came with the May community preview, wouldn't show any of the topics. The solution was to change the binding "dexplore.exe" from the v2.0.40507 to v2.0.40426 in the "dexplore.exe.config"-file in the install directory, since that version of the framework is installed.

[update: I just noticed this is descriped in the readme, in point 18.2.]