Yes use an assemblies folder off of the trunk. I like the name lib better then assemblies Yes the path is already relative. When you branch your projects will get the correct assemblies folder Depending on how many third party assemblies you are using you make also want to organize your assemblies folder so it is not one big mess of dlls.
Yes use an assemblies folder off of the trunk. I like the name lib better then assemblies. Yes the path is already relative.
When you branch your projects will get the correct assemblies folder. Depending on how many third party assemblies you are using you make also want to organize your assemblies folder so it is not one big mess of dlls.
Right we actually have the assemblies folder divided into tidy sub-directories. As long as these paths are relative then I guess it's a non-issue. Thanks for the help.
– Alex Ford Apr 20 at 16:59.
Now we have nuget you can use it for all supported oss packages and even create your own nuget packages for other 3rd party assemblies. It is worth mentioning openwrap as an alternative to nuget. Nuget stores packages at solution level so each branch (and trunk) would keep a version of these.
I'd suggest this is preferable behaviour. You would want to keep your assemblies version separate if upgrading a 3rd party for example. In the past I've used svn's externals command to build the specific version from the internally developed dependencies.
There's no reason you couldn't stick those in a repository and use externals (or you scm's equivalent) to get the right version. I've used build events to get the dlls into the right place too.
I usually create a common project that all the others reference. Inside that common project, I create a folder called deps (for dependencies). Each of the other projects then references the copy of the DLL in the common project's deps folder.
We have a SolutionItems folder in our solution for the 3rd party references. Every branch of the solution has it's own copy. When we add a reference we use the 'Browse' tab in the add reference dialog and select the assembly relative to our current project.
The Project file contains this: False ..\Solution Items\SomeAssembly.dll.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.