CODEWITHSUNDEEP
c#.netvb.net32bit-64bitwindows-server
Derek
Derek

Reputation: 23

.NET application from network share with Any CPU

Our primary business application is written in a mixture of VB.NET and C# using VS2008. The back-end is SQL server Express 2005.

The application is NOT installed on client machines. It resides on a network share on (currently) a Windows Server 2003 machine which also hosts the database. Clients access the application through a shortcut, and there are additional server-side executables running as services which are accessed by the client application code. It's an entirely 32-bit environment at present.

We are moving to Server 2008 R2 and SQL Express 2008, and will be upgrading some of our 32-bit Win7 clients to 64-bit. I have set the Target CPU to "Any CPU" in the compile options of all .EXE and .DLL projects that comprise the application and have run PVerify on them all - they are entirely managed code.

Is this enough? Will both 32 and 64-bit clients be able to run the application seamlessly?

Thanks

Upvotes: 1

Views: 250

Answers (1)

chwarr
chwarr

Reputation: 7202

The client applications should work in this configuration, assuming they are pure managed code as you say. You haven't said whether you've tested this or not, but testing shouldn't be all that hard. :-)

Note that 64-bit versions of Windows have the WoW64 subsystem that can run 32-bit applications, so you probably didn't have to do anything in the first place.

The question What does the Visual Studio “Any CPU” target mean? may be worth reading, but it looks like that is already understood here. If you need to be able to produce both x86 and x64 outputs (for example, if you have unmanaged DLLs that need to be called into), the question Targeting both 32bit and 64bit with Visual Studio in same solution/project may be useful.

Upvotes: 2

Related Questions