At a recent MSDN event we were told that WSE 3.0 will be compatible with the
Framework 2.0 that comes in Studio 2005. WSE 2.0 SP3 is not compatible with
Studio 2005 and WSE 3.0 is not compatible with Framework 1.1 in Studio 2003.

If this information is incorrect please let us know.

I am in the same situation you are in terms of starting a new project so I
am very interested in any replies this thread generates....

Mike

I have successfully converted a project that uses WSE 2.0 into .NET
2.0.00510 February CTP.

However, there are several gotchas...

1) This is a preview version, not the final release. Things might/will
change and these changes could affect WSE 2.0 "interoperability" with .NET
2.0 (bad word in this context I guess).
2) The VS Add-in does not work, and probably never will. This means that you
must edit your config and policy files yourself.
3) I don't use ASMX, and my HttpModule classes are not in the web service
project. The reason for this is that in the web.config you must be able to
know what the assembly name will be. AFAIK, this is not possible in ASP.NET
2.0 because of the new compiler model. By putting the HttpModule classes (my
service interface classes that inherit from SoapService) in a separate
project (and therefore in a separate assembly), I know which assembly name,
version, etc. to refer to in the web.config file.
4) I have only tried running the converted project on a machine that had
both .NET 1.1 and .NET 2.0 framework installed. Not sure what will happen on
a computer with only 2.0 installed.

There are problaby more, but I can't think of any at this time...

This post confers no rights and implies no guarantee or warranty.