Hi Chris,
As for WSE2 SP3, it is built upon .net framework 1.1 and VS 2003 is the
dedicated IDE for developing WSE 2.0 equiped application. VS 2005 only
support developing .net framework 2.0 appliations, therefore, WSE 3.0 is
the expected one used in VS 2005.
For your scenario, since your server-side service remains ASP.NET
1.1(secured through WSE 2.0) and you need to use WSE 2.0 client proxy, I
think you can consider the following means:
1. Still use VS 2003 IDE add webreference or the WSE2.0'S wsewsdl2.exe to
generate the WSE2 client proxy and put it in a separate class library
project and build it.
2. Reference that class library assembly in your VS 2005(.NET 2.0)
application.
Thus, the wse2 proxy remain built upon .net framework 1.1 and your main
application can be developed through vs 2005/.net 2.0 and call the WSE 2.0
proxy through a class library assembly.
How do you think? If you have any further questions or concerns here,
please feel free to let me know.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
chrisexentra@newsgroups.nospam - 22 Mar 2007 12:15 GMT
Thanks Steven, this sounds like a good way forward.
I think it is unfortunate that VS2005 does not support WSE2 - for us and I
think plenty of other organisations who have 'legacy' WSE2 webservices there
is no easy migration path from 2 to 3. VS2005 appears to be trying to
'force' adoption of 3 - but may actually be causing organisations to resist
moving to VS2005/.NET 2 because of the migration issues?
Chris
> Hi Chris,
>
[quoted text clipped - 49 lines]
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
Steven Cheng[MSFT] - 23 Mar 2007 08:29 GMT
Thanks for your reply Chris,
For Visual Studio 2005, it is dedicated to .net framework 2.0 based
programming. And WSE 3.0 is .net framework 2.0 based and is completely
different from WSE 2.0 not only from framework version, but also the
supported WS-* protocol version. WSE 3.0 implement the latest WS-*
security specification, and WSE 3.0 secured interopable service can also be
compatible with WCF secured webservice. IMO, it is quite recommended to
upgrade service from WSE 2.0 to WSE 3.0 (if .net framework 2.0 has been
applied in the application).
Here are some reference about upgrading webservice from WSE 2.0 to WSE 3.0:
#Migrating Applications from WSE 2.0 to 3.0
http://msdn2.microsoft.com/en-us/library/aa529361.aspx
Hope this also helps some.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.