Deploying .Net Control Source (SVN) for 32-bit and 64-bit dev stations

Question

Here's the situation:
Our Dev development team has heterogeneous operating systems scattered between 32-bit and 64-bit. This is not ideal, we actually plan to homogenize our infrastructure, but at the same time we have to deal with it.

The problem is that when a 32-bit developer tests a 64-bit solution on SVN, he must manually manually change the target platforms to compile it (not to mention other problems)

My question:
What pure (albeit temporary) solution could be solved in such a situation, allowing each developer to save the project / platform default settings during verification and in SVN.

I assume that, at least for the first time the project / solution is checked, the developer still has to manually configure the parameter in order to compile it correctly. After that, according to the appropriate SVN filters, you can ignore some settings files (which ones, by the way?)

I am open to all smart and detailed offers.

Thank.

Answer 1

Are you checking .suo and .user files in source code? Because they should be specific to developers, not should . Pretty sure suo maintains project build status for each user.

- . , 4 script, autohotkey . msbuild , , .

.

, , .

Answer 2

, 32- 64-? : , DLL?

" ", .NET 64 32 , .

: , CPU , x86-32 x86-64, .

, AnyCPU, , , .

Answer 3

As long as you use only managed dotnet code (without your own 32/64-bit code), each body can only work with a 32-bit solution on 64-bit and 32-bit dev stations. On win7-64, visual studio is also a 32-bit application.