Advice re use of WSE in a 64 bit app

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

andyks - 18 Jul 2005 20:02 GMT

What advice or guidance is there about using the shipped WSE 3.x assembly or
the WSE 2SP3 assembly in a 64bit .NET 2.0 beta 2 application?

Reply to this Message

Benjamin Mitchell - 20 Jul 2005 14:32 GMT

WSE 2 apps will never be supported on 64bit, WSE 3 apps will.

>From Mark Fussell's 'What's new in WSE 3.0' article [1]:

"There will be a supported release of WSE 2.0 on the .NET Framework 2.0
after it has released. Applications built with WSE 2.0 SP2 and SP3
applications will be supported on .NET Framework 2.0; however, WSE 3.0
is the preferred solution for the .NET Framework 2.0. There is no
design-time support for WSE 2.0 with Visual Studio 2005 and WSE 2.0 is
supported only on 32-bit and not 64-bit. WSE 2.0 SP3 does install with
Visual Studio 2005 Beta 2 and the .NET Framework 2.0, but is
unsupported."

Regards,

Benjamin Mitchell [RD/MVP]
1 -
http://msdn.microsoft.com/webservices/building/wse/default.aspx?pull=/library/en
-us/dnwse/html/newwse3.asp

Reply to this Message

andyks - 20 Jul 2005 15:42 GMT

Ben,

That's an awful lot of "supporteds"..

Lets put the question another way.

1) I have a pure managed assembly built with VS2003 targetting .NET 1.1.
This has been provided by a 3rd party and I do not have the source.

2) I am using VS2005 and I am writing a pure managed app. I wish to run
this as a 64 bit app targetting .NET 2.0.

3) I wish the 64 bit .NET app to use the assembly mentioned in 1) above.

Where can I find clear info about the mixing of 64 & 32 bit components
inside 64 bit .NET apps?

> WSE 2 apps will never be supported on 64bit, WSE 3 apps will.
>
[quoted text clipped - 14 lines]
> 1 -
> http://msdn.microsoft.com/webservices/building/wse/default.aspx?pull=/library/en
-us/dnwse/html/newwse3.asp

Reply to this Message

Benjamin Mitchell - 22 Jul 2005 01:07 GMT

Josh William's blog has a lot of the deep details on the interaction
between 32 and 64 bit applications with .NET 2.0. The latest post [1]
he has on this topic, from October last year, has this to say on the
situation you describe:

"If you make a .Net 2.0 executable and link against a v1.0/1.1 dll you
will be able to load it into your process as if it was a .Net 2.0 MSIL
assembly. If that v1.0/1.1 dll has code that isn't safe to run in
64-bit mode it may crash."

I'd suggest a Goolge query like this to find out about mixing of 64 and
32 bit compnents in a 64 bit .Net application:
http://google.com/search?q=running+32bit+%2ENET+apps+in+64bit+CLR

Regards,

Benjamin Mitchell [RD/MVP]
1 - http://blogs.msdn.com/joshwil/archive/2004/10.aspx

Reply to this Message

andyks - 24 Jul 2005 20:25 GMT

Pretty limited stuff...It's not as if using pinvoke can cause issues is a
stunning revelation in the transition from 32 to 64 bit...Does this count as
the best documentation you know of?

Besides which neither WSE 2 no WSE 3 have such troublesome dependencies.

I guess like the rest of us you simply don't know. I would advise that you
tighten up your usage of "supported": Could be "MS don't want you to do
this" or "It simply cannot work".

> Josh William's blog has a lot of the deep details on the interaction
> between 32 and 64 bit applications with .NET 2.0. The latest post [1]
[quoted text clipped - 14 lines]
> Benjamin Mitchell [RD/MVP]
> 1 - http://blogs.msdn.com/joshwil/archive/2004/10.aspx

Reply to this Message

Advice re use of WSE in a 64 bit app

Free Magazines