Thursday, September 20, 2012 9:50 PM
I have a question about using projects and bringing them into Visual Studio from a Subversion repository.
We have a WPF application that has 1 WPF project and uses 3 custom built in house libraries. The 3 libraries are all projects in their own Subversion repositories.
These 3 libraries are used by this WPF application as well as other applications in our group.
Currently we don't bring in the built .dll files in our WPF project solution, we check out the dll projects in our WPF solution and build it before the WPF application. We do this because we know we will be making changes to the libraries often in the WPF application solution.
My question - is it better to use the library projects or the .dll file in the Visual Studio application?
remember we are using these libraries across other applications as well.
no we are moving to TFS and I'm lost. I don't know if these 3 libraries should be in their own TFS projects or should all be contained in one TFS project. Can anyone help with this?
Friday, September 21, 2012 6:34 AMModerator
Thanks for your post.
According your description that you will be making changes to the libraries often in the WPF application solution, and libraries across other applications. I suggest you create the own projects for that 3 libraries under the Team Project.
John Qiao [MSFT]
MSDN Community Support | Feedback to us
- Marked As Answer by John QiaoMicrosoft Contingent Staff, Moderator Wednesday, September 26, 2012 9:03 AM
Sunday, September 23, 2012 6:47 AM
If I understand this correctly, your company has 3 custom libraries that is stored in Subversion, but you using TFS and Visual Studio in your daily work, but you are the one developer making most changes to these 3 custom libraries. Correct?
If this is true, you should do what John is purposing, copy the latest version of the source to to the TFS server, and maintain it there. The version of the 3 custom libraries on the subversion should be made read-only and you should be creating "releases" and deploy this to a commin location so other developers canretrieve the latest version of your library.
The release might be done in a simple way be putting xcopy command in the post-build events of the solution.
- Marked As Answer by John QiaoMicrosoft Contingent Staff, Moderator Wednesday, September 26, 2012 9:04 AM