建立一个DLL的另一个Visual Studio解决方案 [英] building a dll for another Visual Studio solution

查看:193
本文介绍了建立一个DLL的另一个Visual Studio解决方案的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我想要做的是有从一个Visual Studio解决方案更新一个类库,并把它提供给其他的解决方案以自动化的方式的能力。

What I want to do is have the ability to update a class library from one Visual Studio solution and have it available for other solutions in an automated way.

我不知道任何构建脚本工具(即恶性),我不知道,我需要在为了做到这一点。作为一个的NuGet用户我那种知道你可以发布一些方法但不知道如何做到这一点。

I don't know any build scripting tools (ie, nant) and I'm not sure that I need to in order to do this. As a Nuget user I kind of know you can publish something that way but not how to do so.

我肯定希望最小化花费在任何工具的时间和努力,即使它可能是有用的知识。有人可以给我一些切实可行的建议,做到这一点?

I sure would like to minimize the time and effort spent on any tools, even though it is likely to be useful knowledge. Can someone give me some practical suggestions to do this?

干杯,
Berryl

Cheers,
Berryl

推荐答案

您可以在同一个项目添加到多个VS解决方案。如果您保存该项目于一体的解决方案,并切换到另一种解决方案,它引用它,Visual Studio中应提示您该项目已被修改,你想重新装入。

You can add the same project to multiple VS solutions. If you save the project in one solution and switch to another solution which references it, Visual Studio should prompt you that the project has been modified and would you like to reload it.

如果您不希望包括在多个解决方案的项目(可能是明智的,如果解决方案>〜2号),然后重建就足够了。例如,如果你有两个解决方案:

If you don't want to include the project in multiple solutions (probably wise if number of solutions > ~2) then a rebuild will suffice. For example, if you have two solutions:

  • 包含共享类库
  • 引用的共享类库以同样的方式你引用任何其他外部组件(如log4net的)

然后传播从解决方案A 只是建立解决方案A 控制 + <大骨节病>移更改共享库+ <大骨节病> B )。现在,当你切换到溶液B 的修改应该得到自动拾取(智能感知知道新的特性等。)

Then to propagate changes to the shared library from Solution A simply build Solution A (Ctrl+Shift+B). Now when you switch to Solution B the changes should get automatically picked up (IntelliSense knows about new properties etc.)

这篇关于建立一个DLL的另一个Visual Studio解决方案的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
相关文章
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆