Korenkiewicz, Mark schrieb:
> Marcus,
>
> When it comes to MS Visual Studio there are things like version numbers
> built into compiled DLLs, VS project files that have build options and
> stuff, all of which may be critical to building a specific version of an
> EXE or DLL. In many cases, all this stuff needs to be under SCM.
I think you should NEVER use a IDE as a build tool (as you wouldn't vice versa ;-)). I used nant to
build my VS projects based on a fresh svn co of the desired version (tag).
Still: Never saw a occasion where compiler output versioning made sense.
>
> Is there some limitation in Subversion that prevents this?
>
>
> Mark Korenkiewicz
> ITSC/Mitretek Systems
> College Park, MD
>
>
>
>>-----Original Message-----
>>From: Marcus Rohrmoser [mailto:mrohrmoser@gmx-gmbh.de]
>>Sent: Monday, March 21, 2005 7:41 AM
>>To: users@subversion.tigris.org
>>Subject: Re: Where is binary files should be placed?
>>
>>I think only things hard to create (e.g. source code that is
>>manually edited) should go into version control. Everything
>>else (compile/build output, generated docs etc.) shouldn't be
>>in the repository at all.
>>
>>Hope this helps,
>> M
>>
>>oleksa borodie schrieb:
>>
>>>Hello.
>>>
>>> Help me please I'm new with subversion. Where is binary
>>
>>files should
>>
>>>be placed? I mean where is build output directory should
>>
>>be? Is there
>>
>>>any common practice? I'm using MS Visual Studio.
>>>
>>> I could place it inside project directory project1/bin
>>
>>project1/obj
>>
>>>and ignore with global-ignores option inside configuration file. On
>>>the each developer computer this file should be edited -
>>
>>someone could
>>
>>>forget edit it.
>>> I could move it out of the project folder output/project1/
>>
>>project1/
>>
>>>but what if I will need add some files from bin folder?
>>>
>>> Could you give me advice please?
Received on Mon Mar 21 16:50:43 2005