Subversion and ASP.NET.

Question

We are in the middle of moving from VSS to Subversion, and we have a website project in our Subversion Repo. We deleted the Bin folder because it causes all kinds of conflicts of chaotic trees, because our development solution contains some of the Class Library projects that the website project depends on (configured as links to projects in our solution). We also have several third-party DLLs in the website folder.

The next phase of our project involves a designer changing topics on our website. I would like for him to simply open the website project in VS 2005, change the CSS files that he needs on his working copy and check his files on his localhost. To do this, he needs the most modern DLL files.

Do we need to add Bin DLLs to subversion and configure TortoiseSVN or subversion so that we can transfer our latest DLLs (project dependencies in the developer decision files), but ignore them when updating (per client, I think)? It would also be useful to have third-party dependencies on Subversion.

Answer 1

It would be impossible to structure it as follows:

Trunk/
  WebApp/ 
  ClassLibrary1/
  ClassLibrary2/
  ClassLibrary3/
  3rdPartyDlls/
  build.bat

- - , DLL WebApp Bin ( ). TortoiseSvn build.bat . IIS , WebApp.

, svn externals, .

Answer 2

bin. , , bin . , .

, , "3rdPartyAssemblies". , bin, .

Answer 3

, "3rdParty", .

svn: externals, , "3rdParty", , , .

Answer 4

, , , , , (, ) DLL sourcecontrol "", C:\ . -.

Thi C:\Dependencies, -wiser =)

Answer 5

bin, , . 3- separete, , .

"copy local = true" bin .

-, .

This approach can also be done for your internal dll libraries, so that your designer can simply compile his visual-studio solution, so any corresponding DLL files will be placed in his bin folder and, therefore, create a functional site locally on his machine.