Should i upgrade a working WSE2 app to WSE3



I want to upgrade to WSE3 but need to convince my frightened bosses.

I am only using SecurityTokens UsernameTokens - dont use SAML or
certificates (SSL aside).

Are there any fundemental reasons [to | not to] upgrade - considering my app
is working perfectly ?

Will i also have to upgrade to .Net 2 ?

Are there any performance benefits ?

Are there any notable api changes in these areas of the WSE sdk ?

Thx for any comments/insights



.



Relevant Pages

  • Re: [Lit.] Buffer overruns
    ... http://www.garlic.com/~lynn/2001e.html#39 Can I create my own SSL key? ... http://www.garlic.com/~lynn/2001g.html#19 Root certificates ...
    (sci.crypt)
  • Re: SSL certificate modification
    ... > That's only one reason for the existance of SSL server ... > that certificates contains certified public keys which are used during ... implication then the domain name infrastructure is a trusted server ...
    (comp.security.misc)
  • Re: Web service Security
    ... Direct Authentication thru SSL ... X.509 certificates ... we need to secure the soap header as well as message itself. ... Is there any effective & secure solution which doesnt use SSL ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Setting up Push Mail in SBS 2003
    ... there are problems with the SSL certificates. ... Generally the first hits you'll get in Google will be SSL cert related. ... Outlook Mobile access on SBS 2003. ...
    (microsoft.public.windows.server.sbs)
  • Re: Development Environment w/ssl
    ... > sensitive, private user data. ... > would like to use ssl for the pages that display/edit this data. ... > machines - all the code is stored in a single Visual Source Safe server. ... If you need to issue certificates for the dev machines, ...
    (microsoft.public.dotnet.security)