Includes a free version for personal development. A nice simple plugin, not expensive in terms of memory usage, or the time you need to dedicate to actually learning how to use it.
For Test Driven Development, running the tests internally of the IDE is a must. You'd be surprised at how much time you save by not having to switch to an external runner for every test you want to run.
I have heard something about automated tests that will cause you to fail a commit
Check out build automation - MSBuild or NAnt to name a few. Essentially unless the build process is successful you don't commit your code to your repository. For example, if you had broken some code, the build process would fail. If it passed, you could commit your code safely.
For .NET users, MSBuild (Visual Studio uses it internally) would be a nice start. Check out the official site on MSDN and do some searches for more articles on why build automation is a good idea.
Other Tools
Your question asks about the use of FxCop, StyleCop and so forth. Rather than running these externally you can link them in as part of the build process. This will take some effort setting up, but the time saved by using them and embedding them into the build process is massive. On a side note, your code will improve by using these regardless of when you use them.
Free Resharper
Resharper is expensive for personal development. If your company provides it, by all means use it. Could I justify buying it for personal development? No chance. Instead check out CodeRush Express. It's similiar, and less memory hungry than Resharper. I find it doesn't lock up Visual Studio constantly. Plus some of it's features are pretty nice.
You sound very hung up on plugins and tools, and of course tools can be a great help, but I would focus on the actual stuff that you want to learn, rather than tools and frameworks.
What you definitely need is:
SVN (TortoiseSVN is fine)
Testdriven.Net for running your tests
Teamcity or equivalent for doing continous integration
What you don't need yet are all sorts of plugins and frameworks for improving on these basics. Focus on the TDD and the "story of the build", and maybe release management - and while learning this, you will discover what needs you have for tools.
正如其他一些人所说，TestDriven .Net 几乎是必须的。它允许您从 VS IDE 运行测试。如果您的测试在 NUnit 中，它工作得很好。
最后，我建议使用 NCover 来跟踪您的测试覆盖率。它有一个社区版本，也可以通过 TestDriven .Net 从 IDE 执行。
当然还有用于自动构建的 nAnt 和/或 MSBuild。我会更好地推荐nAnt。
希望有帮助
I believe that the pluggins you are interested in are all fine.
Resharper is nice and powerful, but it requires a lot of memory.
As some others have said, TestDriven .Net is almost a must. It lets you run your tests from the VS IDE. It works fine if your tests are in NUnit.
And at last, I would recommend NCover to keep track of your test coverage. It has a community version and it can be executed from the IDE with TestDriven .Net too.
And of course nAnt and / or MSBuild for automated builds. I would recomend nAnt better.
You may want to look into NDepend, which helps you analyze your code base and keep it clean. (Otherwise, I second advice for TestDriven.Net and ReSharper).
发布评论
评论（4）
Test Driven.NET
包括用于个人开发的免费版本。一个不错的简单插件，在内存使用方面或您需要投入实际学习如何使用它的时间方面并不昂贵。
对于测试驱动开发，必须在 IDE 内部运行测试。您会惊讶地发现，无需为每个要运行的测试切换到外部运行器，从而节省了多少时间。
查看构建自动化 - MSBuild 或 NAnt 等。本质上，除非构建过程成功，否则您不会将代码提交到存储库。例如，如果您破坏了某些代码，构建过程就会失败。如果通过了，您就可以安全地提交代码。
对于 .NET 用户来说，MSBuild（Visual Studio 在内部使用它）将是一个很好的开始。查看 MSDN 上的官方网站并搜索更多关于为什么构建自动化是一个好主意的文章。
其他工具
您的问题涉及 FxCop、StyleCop 等的使用。您可以将它们链接到构建过程中，而不是在外部运行它们。设置这需要花费一些精力，但是使用它们并将它们嵌入到构建过程中可以节省大量时间。顺便说一句，无论您何时使用它们，您的代码都会通过使用它们而得到改进。
免费的Resharper
Resharper对于个人开发来说是昂贵的。如果您的公司提供它，请务必使用它。我可以证明为了个人发展而购买它是合理的吗？没有机会。请查看 CodeRush Express。它与 Resharper 很相似，并且对内存的需求更少。我发现它不会经常锁定 Visual Studio。另外它的一些功能非常好。
Test Driven.NET
Includes a free version for personal development. A nice simple plugin, not expensive in terms of memory usage, or the time you need to dedicate to actually learning how to use it.
For Test Driven Development, running the tests internally of the IDE is a must. You'd be surprised at how much time you save by not having to switch to an external runner for every test you want to run.
Check out build automation - MSBuild or NAnt to name a few. Essentially unless the build process is successful you don't commit your code to your repository. For example, if you had broken some code, the build process would fail. If it passed, you could commit your code safely.
For .NET users, MSBuild (Visual Studio uses it internally) would be a nice start. Check out the official site on MSDN and do some searches for more articles on why build automation is a good idea.
Other Tools
Your question asks about the use of FxCop, StyleCop and so forth. Rather than running these externally you can link them in as part of the build process. This will take some effort setting up, but the time saved by using them and embedding them into the build process is massive. On a side note, your code will improve by using these regardless of when you use them.
Free Resharper
Resharper is expensive for personal development. If your company provides it, by all means use it. Could I justify buying it for personal development? No chance. Instead check out CodeRush Express. It's similiar, and less memory hungry than Resharper. I find it doesn't lock up Visual Studio constantly. Plus some of it's features are pretty nice.
您听起来非常依赖插件和工具，当然工具可以提供很大的帮助，但我会专注于您想要学习的实际内容，而不是工具和框架。
您肯定需要的是：
您还不需要用于改进这些基础知识的各种插件和框架。专注于 TDD 和“构建的故事”，也许还有发布管理 - 在学习这一点的同时，您将发现您对工具的需求。
You sound very hung up on plugins and tools, and of course tools can be a great help, but I would focus on the actual stuff that you want to learn, rather than tools and frameworks.
What you definitely need is:
What you don't need yet are all sorts of plugins and frameworks for improving on these basics. Focus on the TDD and the "story of the build", and maybe release management - and while learning this, you will discover what needs you have for tools.
我相信你感兴趣的插件都很好。
Resharper 很好而且很强大，但是它需要大量的内存。
正如其他一些人所说，TestDriven .Net 几乎是必须的。它允许您从 VS IDE 运行测试。如果您的测试在 NUnit 中，它工作得很好。
最后，我建议使用 NCover 来跟踪您的测试覆盖率。它有一个社区版本，也可以通过 TestDriven .Net 从 IDE 执行。
当然还有用于自动构建的 nAnt 和/或 MSBuild。我会更好地推荐nAnt。
希望有帮助
I believe that the pluggins you are interested in are all fine.
Resharper is nice and powerful, but it requires a lot of memory.
As some others have said, TestDriven .Net is almost a must. It lets you run your tests from the VS IDE. It works fine if your tests are in NUnit.
And at last, I would recommend NCover to keep track of your test coverage. It has a community version and it can be executed from the IDE with TestDriven .Net too.
And of course nAnt and / or MSBuild for automated builds. I would recomend nAnt better.
Hope it helps
您可能需要查看 NDepend，它可以帮助您分析代码库并保持其干净。
（否则，我对 TestDriven.Net 和 ReSharper 提出第二建议）。
You may want to look into NDepend, which helps you analyze your code base and keep it clean.
(Otherwise, I second advice for TestDriven.Net and ReSharper).