What we normally do is create the project with Visual Studio and do an
initial build of the project from within VS. Then add the studio
project folder to your repo with TortoiseSVN, and make sure to de-select
the bin and object directories, as well as the .user file. So far so
good. Then add an svn:ignore property to the project folder to ignore
'bin obj *.user'. Now commit in the parent/solution folder, as you will
need to ensure you get the project correctly added to the .sln file.
This way you get your base project committed to your repo and you ensure
that everyone gets the right ignore pattern. I rarely rely on people
updating the client side config file to correctly ignore things. Far
better to put it on the folder in question and ensure everyone gets it
without having to do anything.
From: Marcus Rohrmoser [mailto:email@example.com]
Sent: Monday, March 21, 2005 7:41 AM
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
Hope this helps,
oleksa borodie schrieb:
> 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
> 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
> but what if I will need add some files from bin folder?
> Could you give me advice please?
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Mon Mar 21 16:46:19 2005