CODEWITHSUNDEEP
.net64-bit32bit-64bitgac32-bit
Mithir
Mithir

Reputation: 2425

Developing on a 64bit machine when the production is 32bit

I have a 64 bit machine for the last year or so and I develop to a production which runs 32bit.

So far I had no problems.

I've been told that I need to replace my workstation so it will run 32 bit. one of his reasons was that there might be some issues so that some dlls which are taken from the GAC are designed for 64bit and may work on my computer but when released to production errors may occur.

Is it correct about the GAC?

Should I replace the workstation? are there other reasons why it should be replaced?

Upvotes: 3

Views: 164

Answers (2)

Jim Jeffries
Jim Jeffries

Reputation: 10081

This is what continuous integration is built for. Get a 32-bit CI environment setup to test your changes after every commit. This way you will know your changes work on your production environment.

By moving your build process to a dedicated machine that has a similar setup to your production machine you can build and test more reliably. It is good for getting rid of the "works for me" issues as if it doesn't build on the CI server, then something has gone wrong.

See here and here for more information.

Upvotes: 4

wilx
wilx

Reputation: 18228

IMHO, you should keep your beast of a machine and do development there. You can either get a Windows VM or another machine to do all of your testing, verification and debugging there.

Upvotes: 2

Related Questions