I just learned recently that MAS 500 tasks including any new .NET client tasks you create will not be able to take advantage of 64 bit processors. The problem is the MAS 500 framework is making interop calls to old 32 bit DLLs. Until MAS 500 is totally using .NET this going to be a fact for quite sometime. On the other hand, the database side of things can take full adavantage of the new 64 bit processors, so there is some good news on this front.

One thing you will need to do when creating .NET EXEs is to ensure you explicitly set that you will be using x86 CPUs. By default, Visual Studio 2005 is set to use 'Any CPU'. If you leave it as this setting you run the risk of having the application error out if it is installed on a 64 bit system. Setting it to the x86 setting will keep it running in a 32 bit mode even on a 64 bit machine.

I hope you find this information useful.


I need to add that the next version of MAS 500 will be able to take advantage of 64 bit processor servers. The current version is still using a 32 bit version of License.DLL which means even on a 64 bit SQL Systems, it would still be running in a 32 bit mode.

Louis Davis

Last edited Jan 31, 2007 at 3:54 PM by MAltadonna, version 1


No comments yet.