CODEWITHSUNDEEP
.netasp.netwindows-server-2008x86-64
nWorx
nWorx

Reputation: 2155

Precautions when developing ASP.NET application on x86 computers but target computer is 64 bit (Windows Server 2008)

We have to deploy our application on a Windows 2008 64 bit server. As the application is already running for over one year on a Windows 2003 server installation, we know everything is working fine. We are still developing on Windows XP.

But installing it on a Windows 2008 64 bit system make me feel a little bit uneasy.

So are there any points, where we have to watch out? Are there any traps or tricky things to do?

Upvotes: 2

Views: 375

Answers (4)

Colin
Colin

Reputation: 10638

There's probably no real things to worry about, except when using Third party dll's that have been compiled specfically for x86.

I do all my builds in ASP.NET 'Platform independent', so they run on x86 as well as x64 without problems.

Upvotes: 1

Darin Dimitrov
Darin Dimitrov

Reputation: 1038780

A point of attention is if you use PInvoke to call unmanaged libraries and the size of IntPtr structure.

Upvotes: 0

sharptooth
sharptooth

Reputation: 170499

If you consume an in-proc 32-bit COM server prepare to see it no longer working unless you create a COM+ application for that COM server.

Upvotes: 0

Thomas Levesque
Thomas Levesque

Reputation: 292425

If you compile it with "Platform target" = "Any CPU", there shouldn't be any issues... remember that .NET is not native code anyway, so it's not platform dependant.

I'm currently working on an ASP.NET application deployed on Windows Server 2008 64 bits, and my development machine is Win XP 32 bits. No issues so far...

Upvotes: 1

Related Questions