解决方案\参考管理 [英] solutions\references managment

问题描述

我想创建utils类库(例如，日志记录等)
我想在几个独立的应用程序中使用utils解决方案.

我当然正在使用源代码控制...

-这是否意味着我应该管理utils解决方案(持有utils类库)
并为每个应用程序提供单独的解决方案?

-使用ApllicationA解决方案的utils类库该怎么办?

-ApplicationA解决方案还可以包括utils解决方案(例如，去定义作品吗?)

-如果可能的话，是否意味着程序员A的任何更改都将通过ApplicationA解决方案应用于utils库，也将使用相同的utils类库影响ApplicationB解决方案

-修复utils解决方案中的错误时该怎么办?
-修补程序如何气泡到ApplicationA和B?

I would like to create utils class library (eg, logging, etc)
I want to use the utils solution in several independent applications.

I''m using source control of course...

- Does that mean I should manage utils solution (holding the utils class library)
and also separate solution for each application?

- What do I have to do to use the utils class library from ApllicationA solution?

- Can ApplicationA solution also include the utils solution (eg, go to definition works?)

- If that is possible, does that mean that any change programmerA apply to utils library via ApplicationA solution , also affects ApplicationB solution using the same utils class library

- What do we to do when we fix a bug in utils solution?
- How does the fix bubbles to ApplicationA and B?

推荐答案

您要做的就是构建库的发行版-我假设它是DLL? -并在其他项目中添加参考.然后，他们将访问发行版本.您可以继续开发控件的调试版本，并仅在准备就绪时重新构建发行版.

您不必将项目添加到任何其他解决方案或源代码中，只需将其添加为引用(如果需要，还可以添加using).

All you have to do is build the release version of your library - I assume it is a DLL? - and add a reference in the other projects. They will then access the release version. You can continue developing the debug version of the control and rebuild the release only when it is ready.

You do not have to add a project to any other solution, or the source code - just the reference (and obviously the using if you want that).

这篇关于解决方案\参考管理的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！