Failing that, you could try using Corflags to set the assembly to be 64-bit
compatible: http://msdn.microsoft.com/en-us/library/ms164699.aspx

This has a number of caveats though, most notably the fact that you won't be
able to do this if the 3rd party assembly is strong-named.


On Thu, Jun 9, 2011 at 3:01 PM, Peter Maddin <petermad...@iinet.net.au>wrote:

> Thanks
>
>
>
> I am referencing a third party logging assembly. I suspect that it is 32
> bit and that is my problem.
>
> I have asked the vendor if they can provide a 64 bit release.
>
>
>
> Regards Peter
>
>
>
> *From:* ozdotnet-boun...@ozdotnet.com [mailto:
> ozdotnet-boun...@ozdotnet.com] *On Behalf Of *Stephen Liedig
> *Sent:* Thursday, 9 June 2011 12:28 PM
> *To:* ozDotNet
> *Subject:* Re: 64 bit wcf service library
>
>
>
> Hi Peter,
>
>
>
> Typically, any cpu will run apps on the platform onto which they are
> deployed, so that should be fine. does your service have another references
> (third party) which may not be installed on the server? If so make sure they
> are also installed or they are compatible with x64.
>
>
>
> HTH,
>
>
>
> Steve
>
> On 9 June 2011 11:15, Peter Maddin <petermad...@iinet.net.au> wrote:
>
> I have written a fairly simple wcf service library.
>
>
>
> This will be hosted in a virtual instance of windows server 2008 r2,
> presumably running IIS 7.5 or better.
>
> The server will have 6 cores and 36 GB of memory.
>
> It will run 3 virtual web servers each will be bound to 2 cores and have
> 1/3 of the memory allocated.
>
>
>
> The system administrator has requested that the web service be 64 bit.
>
>
>
> The WCF service library is set with a Platform Target of ‘Any CPU.’
>
> If I set this to x64, did  clean and rebuild, it does this ok.
>
>
>
> The IIS web site chucks a fit however and gives me this error
>
>
>
> Error      2              Could not load file or assembly
> 'PathWestDirectServiceLibrary' or one of its dependencies. An attempt was
> made to load a program with an incorrect format.
>
>
>
> I removed the web site and created it anew and added my wcf service library
> but it still does not like an assembly that targets x64.
>
> If I change it back to AnyCPU its happy with the format.
>
> Looks like I am stuck with it being set to AnyCPU.
>
>
>
> I am developing on Windows 7 64 bit.
>
>
>
> Is what I am doing just not possible. Any reason why?
>
>
>
> *Regards Peter Maddin*
> *Applications Development Officer*
> *Path**West Laboratory Medicine WA*
> *Phone : +618 6396 4285
> Mobile: 0414 240 307*
> *E-Mail : petermad...@iinet.net.au; peter.mad...@health.wa.gov.au*
> *The contents of this e-mail transmission outside of the WAGHS network are
> intended solely for the named recipient's), may be confidential, and may be
> privileged or otherwise protected from disclosure in the public interest.
> The use, reproduction, disclosure or distribution of the contents of this
> e-mail transmission by any person other than the named recipient(s) is
> prohibited. If you are not a named recipient please notify the sender
> immediately**.*
>
>
>
>
>
>
>

Reply via email to