Unfortunately, I think this may be it.  We hit the same thing moving a VS2005 project to VS2008 about two months back (more info here: www.jeremyjarrell.com/.../83.aspx)

It sounds like from this forum thread that MS won't be supporting WSE3 at all on VS2008 so this will have to be the 'official work around': forums.microsoft.com/.../ShowPost.aspx

Jeremy

Pingback from  Dew Drop - April 4, 2008 | Alvin Ashcraft's Morning Dew

You can always use the commandline tool that comes with WSE3: WseWsdl3.exe to generate the proxy class for you.

Probably not as cumbersome as opening up VS2005 and VS2008, copying files over, etc.

Pingback from  Alles rund um Hack Angriffe  » Blog Archive   » RE: Verschl??sselung  -  Hack den BMW!

Thank you so much for posting these instructions, this really helped me out.  I have a Java CXF based web service with some operations that I wanted to use MTOM with, and one of our clients is written in .NET 2.0.  You really saved me a lot of frustration getting the client stood up and working!  

Thank You for this workaround, Ive been looking around, being August 08, I would assume by now there are no updates or anything to support WSE 3.0...  I thought I was just 'out of the loop' when coming back into from VS 2003 to VS 2008, lots of differences.  I would assume the commandline tool will be the best option as I dont have VS 2005 at all. =o  Thank you again for your help, and if anyone finds an update or anything please post!

Thank You for your help!

Pingback from  wse

You can use WSE -> Configuration Tool to enable the security instead of having to open from VS 2005 and then copy paste in VS 2008.

It's probably wiser to just upgrade to WCF.

It's the future after all, and supersedes all of WSE 3.0.

I'm doing it right now, and it seems pretty straightforward, actually.

Check out this link: blogs.imeta.co.uk/.../345.aspx

Derik:

WCF can be used to consume a WSE web service with amazing ease. In VS 2008, it's as easy as creating a Service Reference rather than a Web Reference.

Caveat: By easy, I mean for most basic scenarios. It's quite possible that you'll end up having to monkey with the WCF configuration a bit. There's a learning curve there, and it frequently drives me nuts. Once you finally understand it things makes a *lot* of sense, but before then, ouch.

Still, I agree with Tor: it's wiser to upgrade to WCF if you can.

I cannot use the commandline tool on my computer...tells me to reinstall the .NET v2.0 SDK.  Was working before I upgrated to VS 2008.

I ended up using a virtual computer that still have VS2005 to generate the proxies I needed.

Jack

How would you convert this WSE code to WCF?

       UsernameToken token;

           userS.RequestSoapContext.Security.Tokens.Add(new UsernameToken(sUser, sPassword, PasswordOption.SendPlainText));

How would you convert this WSE code to WCF?

UsernameToken token;

userS.RequestSoapContext.Security.Tokens.Add(new UsernameToken(sUser, sPassword, PasswordOption.SendPlainText));

Pingback from  401 While Accessing Web Service | keyongtech