Adds extended capabilities to .NET web services. New features in WSE 2.0 include policy framework, enhanced security model, message-based programming model, support for multiple hosting environments.

1.0 sp1 provides enhanced security features such as digital signature and encryption, message routing capabilities, add message attachments that are not serialized into XML.

MS KB article here -
Programming with web service enhancements

San Diego .NET user group meeting about this, and here's a link to the MSDN info on it.

Visual Studio .NET and Office Development

Thanks to Chris Sells for the heads up on this one.
Windows Server 2003 and IIS 6 against the competition

Notes from MSDN TV session.

WinCV
<:VSDir>\SDK\v1.1\Bin

Excellent! Browse the system assemblies and QUICKLY shows you all the methods available. You just type the object and see the memberse. Much faster than MSDN help, etc.

You can configure which assemblies are loaded to search by WinCV by editing the wincv.exe.config file.

Sharing a File for Multiple Projects
Physical file in a directory, but want to "point" to it from multiple projects.
In the project where you want to link, choose Add, Existing Item...find the file, but instead of click Open, pulll the Open button down and choose Link
This is great for AssemblyInfo.cs type stuff where version and signing key info are kept. Maybe only want to have one of these per solution.

Launch Multiple Processes in Debugger
Normally when you do GO -- it will launch the debugger on the "Startup Project".
Solution Properties, select multiple startup projects. For each one, can change start with or without debugging. as well as the order in which they are started.

Start with a Blank Solution
Helpful when you have many projects one level below where you want the solution. Instead of having the solution file in the same directory as the FIRST project you created.

Task List
Use //TODO: dan, fix this!
Tools, Options, Task List, add your own stuff, like ShowStopper etc. with different priorities.

Pre / Post Build
C# only.
Build properties,
Pre - maybe clean the build folders, remove from GAC, etc.
Post - maybe install to the GAC. i.e. "gacutil -i $(TargetPath)" (use Macros to point to various file paths, etc)
Set condition (only if successful, etc)

Treat Warnings as Errors
Build Properties, set to True. Recommend should always do this with release builds
Always set warning level to 4. (get as much help from compiler as possible)

Navigate XML and Structured Documents
xml, aspx, etc.
View, other windows, document outline.

C# Event Accessors
Usually a delegate is a public member variable. This is sometimes bad design, since you may want to control how many subscriptions are allowed, or limit access to subscriptions during key times, etc.

Can setup delegates with accessors much like a property.

public event MyDelegate NumberChangedEvent

{

   add {  m_NumberChangedEvent += value; }

   remove { m_NumberChangedEvent -= value; }

}

Within the add/remove functions, you can do whatever you want. Didn't specify how to reject a subscription, etc. since there's no return value. Maybe you throw exceptions?

Clients still use the += and -= operators to setup subscriptions to your event.

Now that I've made the switch to Outlook for my address book, I have been working on the export functionality for my home-grown XML-based distributed address book. I've got the export part working, using the Outlook Object model, from C#/.NET, and now just plugging in the last piece - calling the "export" functionality from an .aspx page.

Bam - brick wall !!

Apparently there are all kinds of problems using automation to drive Outlook from a service, web page, IIS, etc.

I guess I should have seen this coming. Not only is it unstable per the above document, but there are "profile" issues, etc. When trying to hit this from IIS, the account opening the Outlook session is not interactive, so it's probably prompting to create a new profile, etc.

I'm rethinking this now, probably going to just fallback to a nightly export job that lays the xml somewhere, and then a simple ASP.NET page to dish out the xml. Hmmm...maybe this can help in the "difference" issue too -- the nightly job can run a diff against the previous, and potentially not update the data if it's the same! :) So then I could get back to the "only return the data if it's changed" model.

I am so lame that I never know how to convert from the .NET DateTime.Ticks in 100-nanosecond increments down to something more reasonable like milliseconds.

Once and for all, here it is:
- to milliseconds -- divide by 10,000

keywords: ticks tickcount