c# - What is the best way to make shared libraries available to multiple applications? -
Like most shops, we get a team of people working on various projects, all of whom have the same basic information and Access to the works that are related to our business, usually in C # We are currently copying normal sections from project to project, but everyone is starting to taste their own and we want to strengthen it.
We use Turtle SVN and we are not sure about a separate project, but it is the best way to deploy this common code for our various applications. We work for an internal IT store that can tell users all about access to applications, we are not concerned about releasing our products in the real world.
We have some ideas: I know that this is a common problem, and if you Or spend time using any other option, you always find people explaining the loss of each method (version, regression test, "DLL hell", "GAC waste" etc.). What works I do and why is there a favorite way? We have only one problem on my company. Currently, we just use .bat files Who go to our SVN trunk and most recent Dll pulls the reference and fill in a local reference folder for the project you are working on. However, we are currently working on switching the system upwards I do not believe 100% how it works, but it is definitely worth it. It seems that you can point it out in a shared code collection, and then using a plug-in in Visual Studio, it's just as simple and every time you click on 'Update' to get the latest code It's easy to do. / P>
Comments
Post a Comment