Deploying a .Net App Source Control (SVN) over 32-bit AND 64-bit dev stations

Posted by Mika Jacobi on Stack Overflow See other posts from Stack Overflow or by Mika Jacobi
Published on 2011-01-13T10:59:11Z Indexed on 2011/01/13 11:53 UTC
Read the original article Hit count: 237

Filed under:
|
|
|
|

Here is the situation :
Our Dev Team has heterogeneous OS systems, scattered between 32-bit and 64-bit. This is not ideal, we are actually planning to homogenize our infrastructure, but in the meantime we have to deal with it.

The issue is that when a 32-bit developer checks out a 64-bit solution on SVN, he has to manually change the target platforms all over again to get it compiled (not to mention other side problems)

My question is :
What clean (though temporary) solution could be addressed in such situation, permitting each developer to keep his default project/platform settings while checking out and in from SVN.

I guess that -at least for the first time a project/solution is checked out, a dev still has to tweak the setting manually to compile it properly. After that, according to relevant SVN filters, it is possible to ignore some settings files (which ones, by the way?)

I am open to all clever and detailed suggestions.

Thanks.

© Stack Overflow or respective owner

Related posts about c#

Related posts about .NET