If you have a question regarding Web Services Enhancments (WSE) there is a great place on the net to look for the answer…
WSE FAQ all the web logs, web sites and information about WSE.
While preparing for some VS2005 lectures I found this nice site which lets you see what was changed in framework 2.0 ….
Cs2themax .Net Inspector
Using the browser we can explore all the assemblies, namespaces, types, and members in version 1.1 and 2.0 of the Microsoft .NET Framework and quickly determine which items have been added, removed, or modified from previous version.
For anyone who missed the convention…. Or just want to see Roy again and again….
Here is the link to Microsoft Deep Dive videos…http://www.besttv.co.il/microsoft/
Enabling the use of Themes in .net apps may cause the following error:
‘System.Runtime.InteropServices.SEHException’ occurred in system.windows.forms.dll
Background information regarding this bug can be obtained at Code Project’s BugList
There are two solutions for this bug:
The first solution is to add Application.DoEvents() just after calling EnableVisualStyles() on the main form:
void Main()
{
Application.EnableVisualStyles();
Application.DoEvents();
Application.Run(new Form1());
}
The second solution is to create an application external manifest file:
Create a new xml file in the application directory with the name of the application and an extension of exe.manifest. For instance, if your application name is "MyApp", you will name the manifest file as MyApp.exe.manifest. Place the following content in this file.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity
version="1.0.0.0" This is the application version
processorArchitecture="X86"
name="Theme Test" This is the application name
type="win32" /> This is the application description
<description>Testing Windows XP Visual Styles.</description>
<dependency>
<dependentAssembly>
<assemblyIdentity
type="win32"
name="Microsoft.Windows.Common-Controls"
version="6.0.0.0"
processorArchitecture="X86"
publicKeyToken="6595b64144ccf1df"
language="*" />
</dependentAssembly>
</dependency>
</assembly>
Its possible to embed this file into the executable as John McTainsh explains in this article.
Some information about this bug can be found at Cool Client Stuff blog
WSE 2.0 simplifies the development and deployment of secure Web services by enabling developers using Visual Studio .NET and the .NET Framework to more easily apply security policy, establish long-running secure conversations, retrieve and validate security tokens and more. New features include a policy framework, enhanced security model, message-oriented programming model, and support for multiple hosting environments.
Service Pack 2 addresses customer issues and provides a new Kerberos token that enables support for constrained delegation and clustering scenarios.
Download Web Services Enhancements 2.0 Service Pack 2 
For a list of changes made in SP2 check here