CODEWITHSUNDEEP
c#visual-studiosvnversion-controlsmartsvn
Mytheral
Mytheral

Reputation: 3959

Any limitations with svn and c# / visual studio?

In other languages such as objective c there are certain files that you can't (or shouldn't) put under version control such as the story board and user data.

Does C# and Visual Studio suffer with any of these limitations?

edit: We are using Smart SVN.

edit2: from your comments it sounds like these would be the optimal global ignores: *.suo *.user *.ncb *.aps bin obj Debug Release temp debug release

Upvotes: 4

Views: 235

Answers (3)

jussij
jussij

Reputation: 10560

If you use a MS-SCCI Subversion plug-in like Agent SVN then the Visual Studio IDE itself will control what files get added to the repository.

Upvotes: 3

Skalli
Skalli

Reputation: 2817

At our company we're working with VS2010 and Subversion too. So far we never had any problems. We're using AnkhSVN and TortoiseSVN as clients.
We only added some files to the ignore list, mainly *.user and *.suo. Those files save local paths which are only interesting for local users. No need to have them in the repository. It's no problem if you commit them, it's just not necessary (at least from my personal experience, it might save some trouble not adding them to version control).

Edit to your edit: Yes, those files/folders can be ignored. Basically anything that is created at the client side when it is needed. Also this way users can have their own settings and work environment without colliding with other users path layout, for example.

Upvotes: 2

amaters
amaters

Reputation: 2316

We have been using visual studio in combination with Visual SVN (commercial use) for over a year now and the only issue we had was that some files from the project templates had multiple line endings which caused the commit to fail. Only after we fixed the line endings we could commit those files.

Another limitation in the current version we use is that committing a solution with externals in it does not go as smooth as it should. Externals not being committed and/or marked as no changes (while they in fact where changed).

A workaround is using TortoiseSVN which is being used in Windows explorer and not in Visual Studio itself. Never had any problems using this program

Upvotes: 2

Related Questions