如何使用 Debugger 进入 NServiceBus 2.0 并使用 Resharper 进行导航？
我们刚刚决定在我们的项目中使用 NServiceBus，但我们遇到了一些问题。与其每次遇到问题时都“求鱼”，我们更愿意“授之以鱼”。这意味着进行一些设置，以便我们可以进入 NServiceBus 源代码并更深入地了解 NServiceBus。
我们需要一些帮助来弄清楚如何实现这一目标。目前尚不清楚如何让 Visual Studio 在每次编译时成功构建 NServiceBus，因为 NServiceBus 附带其自己的 Nant 构建过程，该过程使用 ILMerge 创建合并的程序集等。
我们已经尝试使用 Nant 脚本构建 NServiceBus，然后引用这些 dll 和 pdb。然而，这并不能让我们走到任何地方，也不能让 VS.NET 和 Resharper 通过“查找用法”和其他功能进行导航。
因此，我们真正想要创建的是一个 VS.NET 解决方案，它构建我们的内部软件和 NServiceBus，并允许我们在它们之间无缝步进和导航。
这可能吗？我们需要做什么才能实现这一目标？
We've just newly decided to use NServiceBus on our project and we're experiencing some problems. Rather than "ask for a fish" every time we hit an issue, we'd prefer to "teach ourselves to fish". This means setting things up so we can step into the NServiceBus source code and understand NServiceBus more deeply.
We need some help figuring out how to pull this off. It is unclear how to get Visual Studio to successfully build NServiceBus upon each compile, since NServiceBus comes with its own Nant build process that uses ILMerge to create consolidated assemblies and so forth.
We have already tried building NServiceBus with the Nant script and then referencing those dlls and pdb's. However, that does not let us step everywhere, and it also does not let VS.NET and Resharper navigate via "Find Usages" and other features.
So what we would really like to create is a VS.NET Solution that builds our in-house software and NServiceBus, and allows us to seamlessly Step and Navigate between them.
Is this possible? What would we need to do to pull this off?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
不完全是您正在寻找的确切答案，但您可以查看我在 NServiceBus 中调试时发表的帖子，其中涉及以下步骤：
“build.bat”
dll 和 pdb 文件在你的
解决方案，以便您可以步入
NServiceBus 源代码。
我已成功将代码中的日志记录行为更改为始终为 Message.ToString() ，以便 Log4Net 日志更加清晰。
在这里查看：
http://www. craftyfella.com/2010/12/debugging-into-nservicebus-so-you-can.html
希望有帮助。
戴夫
Not quite the exact answer you were looking for, but you can check out the post i made on debugging into NServiceBus which involves the following steps:
"build.bat"
dlls and pdb files in your
solutions, so that you can step into
the NServiceBus source code.
I've successfully change the logging behaviour to always to a Message.ToString() in our code so that the Log4Net logs were a bit clearer.
Check it out here:
http://www.craftyfella.com/2010/12/debugging-into-nservicebus-so-you-can.html
Hope it helps.
Dave