SOAP is a protocol based on XML; it cannot be 32- or 64-bit in principle. The protocol is totally agnostic to this detail. Moreover, if your application is for .NET, it itself can be agnostic to the
instruction-set architecture. You can compile you assembly to the "Platform" called "Any CPU" (see the project properties). You can always do it, unless you reference some compiled to different target architecture, or if you load native (unmanaged) DLL which is compiled to incompatible target architecture.
This "Any CPU" target is possible, because .NET executable files are compiled into CIL, which is also platform-agnostic, and .NET operation is based on JIT: the
machine code is generated during runtime; normally in happens on method by method basis, when a method is about to be called for the first time.
That said, there is nothing you need to do, to use SOAP on a 64-bit system. Only if you are using some 3rd party modules compiled to incompatible platform, you may have problem. If this is the case, please explain what do you have.
Please see:
http://en.wikipedia.org/wiki/SOAP[
^],
http://en.wikipedia.org/wiki/XML_Information_Set[
^],
http://en.wikipedia.org/wiki/Just-in-time_compilation[
^],
http://en.wikipedia.org/wiki/Machine_code[
^].
—SA