如何将输出(.dll)从一个项目拉到另一个? [英] How to pull output (.dll) from one project to another?

查看:203
本文介绍了如何将输出(.dll)从一个项目拉到另一个?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

作为一个更大的解决方案的一部分,我有两个项目。



一个是c ++库作为DLL打包,其他是.NET包装器。 / p>

什么是向Visual Studio指示输出第一个项目的DLL将被拉入第二个项目的目标文件夹的更好的方式,以及更多:对于使用的项目包装,他们会从第一个拿起DLL。



我可以使用后期制作步骤,但我后来更复杂一些。这是可能的吗?



编辑:我们还可以问:如何添加非托管参考?



< img src =https://i.stack.imgur.com/s08OZ.pngalt =solution image>

解决方案

我想我找到一个可能令人满意的解决方案。



步骤:




  • 在包装项目中,我将添加一个现在出现在LIBRARY的输出目录中的DLL。任何配置都可以。

  • 包装器项目的预构建步骤应该将当前配置为内置到源目录中的库的COPY输出直接

  • 文件的
  • 选项将在版本控制中为'不要构建'和'复制到输出目录(如果有更新'

  • ),该文件将被版本控制(我使用svn ,希望在其他人也是可能的。)


As the part of a bigger solution, I have two projects.

One is c++ library packed as a DLL, and other is .NET wrapper for it.

What would be the best way to indicate to Visual Studio that output DLL from first project is to be pulled into the destination folder of second project, and more: for projects that use wrapper, will they pick up also the DLL from the first one.

I could do it with post-build steps, but I'm after something more sophisticated. Is that possible?

EDIT: we could also ask: "How to add unmanaged reference?"

解决方案

I guess I found a solution, that might be satisfying...

Steps:

  • in wrapper project, I'll add a DLL that is now present in the output directory of the LIBRARY. Any configuration will do.
  • Pre-build step for the wrapper project should COPY output of the library that is currently configured to be built into the source directory directly
  • option for the file will be 'do not build' and 'copy to output directory if newer'
  • in version control, that file will be IGNORED by version control (I use svn, hope it's possible in others as well).

这篇关于如何将输出(.dll)从一个项目拉到另一个?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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