如何（以及何时）将 TFS 与也可由 NuGet/NuPack 提供服务的私有 DLL 结合使用？
我们有几个私有的“企业服务”DLL，在我们所有的网站中用于身份验证、日志记录等。由于它们是私有的，我们还控制这些 DLL 的版本和源。创建 File | 之后我们的历史性（容易出错）步骤新项目包括
- 添加“企业服务”项目
- 添加对上面的引用
- 编辑web.config部分，例如身份验证，HttpHandlers等...
NuGet将自动执行上述过程
我刚刚来跨 NuGet （捆绑在 MVC3 中），它允许我从私有托管服务器下载并安装 VS2010 包，并自动化以前手动进行的配置设置。
问题：
- 将我的 dll 发布到私有 NuGet 服务器是否有意义？
- 如果需要的话，我是否会失去调试和单步执行该 dll 的能力？
- 如果我的项目的其余部分基于 TFS，我还应该考虑哪些其他事项？
We have a couple of private "Enterprise Services" DLLS that are used in all our Websites for authentication, logging, etc. Since they are private, we also control the versioning and source of these DLLs. Our historic (error prone) steps after creating File | New Project include
- Add the "Enterprise Services" project
- Add a reference to above
- Edit web.config sections such as Authentication, HttpHandlers, etc...
NuGet will automate the above process
I just came across NuGet (bundled in MVC3) which allows me to download and install VS2010 packages from a privately hosted server, and automate the config settings that previously would have made manually.
Question:
- Does it make sense to publish my dll into a private NuGet server?
- Will I lose the ability to debug and step into this dll if I need to?
- What other things should I consider if the rest of my project is based in TFS?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我同意 marcind 的观点：拥有私人提要是有意义的。
我的 2 美分是，您不需要配置专用服务器：将 VS 配置为以共享文件夹为目标就足以分发包，并且可以轻松地使用 TFS 版本进行更新：只需创建 NuGet 包并将其删除进入共享文件夹。
请记住，对于我测试的最新 NuGet 位，客户端（控制台和 GUI）不会查看其他源来定位依赖项，因此它会抱怨它无法自动解析它们：您将必须手动安装它们。
I agree with marcind: having a private feed make sense.
My 2 cents are that you don't need to configure a private server: configuring your VS to target a shared folder is enough for distributing the packages and it will be easy to update with your TFS builds: just create the NuGet package and drop it into the shared folder.
Keep in mind that, for the latest NuGet bits that I tested, the client (both the console and the gui) does not look into other feeds for locating the dependecies so it will complaint that it can't resolve them automatically: you'll have to install them by hand.
是的，对你来说拥有一个私有的 NuGet feed 是有意义的，
我不确定是否要进入 dll，但是如果你在 NuGet 包中提供 PDB 以及共享上的库源（然后配置 VS 以了解在哪里这些来源是）那么您应该能够像现在处理 .NET 框架本身一样单步执行代码。
NuGet 旨在与映射到源代码管理的项目良好配合，因此希望您不需要其他任何东西。
Yes, it makes sense for you to have a private NuGet feed
I'm not sure about stepping into the dll, but if you provide PDBs in your NuGet package as well as the library sources on a share (and then configure VS to know where those sources are) then you should be able to step into the code just like you can today for the .NET framework itself.
NuGet was designed to work well with projects that are mapped to source control so hopefully there's nothing else you need.
只要您不使用特定存储库，@Ghidello NuGet 就会自动解析依赖项（控制台中的包源下拉列表设置为“全部”而不是您的私有存储库）
@Ghidello NuGet will resolve dependencies automatically as long as you aren't using a specific respository (the package source dropdown in the console is set to All instead of your private repo)