Visual Studio 2008 and WSE 3.0

[Jason Young]

Check out this link for a solution to your problem: http://blogs.imeta.co.uk/jyoung/arch...08/29/345.aspx

[Weltchy]

On a slightly different note,

Have you guys run across a problem with WCF when you use add a service reference or use svcutil /n: and one of your operation contracts includes an XmlSerializerFormat attribute. For some reason, when it generates the code reference file, it seems to declare one of the enums that I created twice.

The first enum is tied in with System.Runtime.Serialization (DataContractSerializer, 3.0.0) whilst the second declaration of the same enum has a generated code attribute of "svcutil", "3.0.4506.648".

I can get round this problem by generating the code file manually and then removing one of the duplicates, but its a tad annoying.

[themistry]

this may help you

http://devlicio.us/blogs/ziemowit_sk...d-wse-3-0.aspx

TM

[themistry]

Anyways, sounds like you are just looking for an argument.

To reiterate, the features of VS 2005 to directly support WSE 3.0 no longer exist in VS 2008. They have been removed.

No big deal.

I am not looking for an argument, I am trying to help you.

But alas, nevermind.

Good luck
TM

[DimPrawn]

Maybe you could elaborate? You still seem to think of WCF as a technology.

WSE 3.0 is a set of standards, which one do you want to impliment or consume?

WCF does not stop you consuming exisiting WSE 3.0 compliant services, it makes it easier. If you want to expose a service, the same argument holds.

TM

I don't have time to go into details, but briefly, VS 2005 had design time support for WSE 3.0. You can take any project, and in the designer check WSE 3.0 and it will generate the necessary .config and changes and generate the required classes to make your web service WSE 3.0 compliant.

VS 2008 removes these design time features as you are expected to create projects that utilise WCF standards.

WSE 3.0 != WCF

http://devlicio.us/blogs/derik_whitt...2008-hack.aspx

http://www.jeremyjarrell.com/archive/2008/02/23/83.aspx

We use web services for communication between our client layer and our business layer. Not only does this help to enforce the thin client nature of our product but it also sets us up well in the future to consider alternative clients to our business logic. However, we use WSE 3.0 to provide enhanced security for our web services. Apparently, VS2008 and WSE 3.0 do not play well together at all. In fact, it would seem that Microsoft has no plans on them ever playing well in the future. Their reasoning is that WCF can do everything that WSE can and more and that all new development should be against WCF. Although I agree with this, it was a bit of a roadblock that we hit with no warning. Unfortunately, when you "convert" your project from VS2005 to VS2008 with the wizard, it will "helpfully" regenerate all of your project web references with no WSE support. However, this can simply be worked around by hand copying all of your generated Reference.cs files from your VS2005 web reference folders to your VS2008 web reference folders. It's a bit tedious (some of our projects have over 50 web references) but actually works quite seamlessly once its complete. Strangely, the conversion wizard will retain your assembly references to WSE 3.0 so the copied WSE classes build fine.

Anyways, sounds like you are just looking for an argument.

To reiterate, the features of VS 2005 to directly support WSE 3.0 no longer exist in VS 2008. They have been removed.

No big deal.

[themistry]

Yes I know, but they have also removed (direct) support from VS 2008 for WSE which was supported in VS 2005 and client has VS 2008 and wants to use WSE and doesn't want to migrate to WCF.

That's progress for you.

Maybe you could elaborate? You still seem to think of WCF as a technology.

WSE 3.0 is a set of standards, which one do you want to impliment or consume?

WCF does not stop you consuming exisiting WSE 3.0 compliant services, it makes it easier. If you want to expose a service, the same argument holds.

TM

[DiscoStu]

I have no clue what any of you are talking about. Ignorance is bliss!

[DimPrawn]

You will find that WSE 3.0 is just a set of standards... that low and behold... are generally all implimented under WCF...

WCF isn't a new technical solution by Microsoft, they have just made developing WS-* compliant services much easier.

TM

Yes I know, but they have also removed (direct) support from VS 2008 for WSE which was supported in VS 2005 and client has VS 2008 and wants to use WSE and doesn't want to migrate to WCF.

That's progress for you.

[DimPrawn]

Come on DP. Keep up. No wonder the banks are cutting peoples rates by 10%. tsch tsch

I think I should spend more time working (an learning) and less time posting.

HTH

[themistry]

Solved. There is no, and there never will be, support (directly) for WSE in VS.NET 2008.

There are hacks but the only real approach is migrate to WCF.

HTH

You will find that WSE 3.0 is just a set of standards... that low and behold... are generally all implimented under WCF...

WCF isn't a new technical solution by Microsoft, they have just made developing WS-* compliant services much easier.

TM

[Weltchy]

Come on DP. Keep up. No wonder the banks are cutting peoples rates by 10%. tsch tsch

[DimPrawn]

Solved. There is no, and there never will be, support (directly) for WSE in VS.NET 2008.

There are hacks but the only real approach is migrate to WCF.

HTH

[DimPrawn]

VS.NET 2005 had design time support for WSE 3.0

Can't seem to find similar support in 2008

Any hints or tips in implementing WSE 3.0 enabled web services using VS.NET 2008?