如果我减少使用 Visual Studio Express，我会感到痛苦吗？
随着 Visual Studio 2010 即将发布，以及 C# 4.0 中所有可爱的新功能，我真的很想从 2008 年开始更新。但是，在过去的几年里，我已经设法获得学生定价，甚至通过以下方式获得免费版本： MSDN 学术联盟。
现在我不再是学生了。
我似乎无法证明即使是标准版的 $AU500 的价格标签是合理的目前来说，本质上是一种爱好。尽管我希望如此，但它只是无法支付账单。
因此，我在 Microsoft 网站上读到 Express 版本 EULA 中没有非商业条款，这很好，因为我偶尔会在其中做一些付费工作。不过，与 Professional（我目前使用的以及 2010 beta 版是什么）相比，Express 版本缺少了多少功能？当我伸手去拿不存在的东西时，我是否可能会经历戒断痛苦？
就插件而言，我真正使用过的唯一插件是 VisualSVN，而且我可以手动使用 TortoiseSVN。还有什么我应该注意的吗？
With the upcoming release of Visual Studio 2010, and all the lovely new features in C# 4.0, I would really love to update from 2008. However, over the last few years, I've managed to get student pricing, or even free versions via the MSDN Academic Alliance.
Now I am no longer a student.
I can't seem to justify the $AU500 pricetag of even the Standard version for what is at the moment, essentially a hobby. As much as I may like for it to be, it just isn't paying the bills.
So, I've read on the Microsoft site that there's no non-commercial clause in the Express version EULA which is good because I do the occasional bit of paid work in it. How much is missing from the Express version though, compared to Professional (what I use currently, and what the 2010 beta is)? Am I likely to go through withdrawal pains as I reach for something that just isn't there?
As far as addons go, the only one I've really played with is VisualSVN, and I can live with just using TortoiseSVN manually. Anything else I should be aware of?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（6）
可以在此处找到版本比较：(对于 2008 年）（编辑：可以从 这里）
我不想缺少的功能是：
如果你可以没有这些工具（以及其他不会困扰我个人的限制），那么我想你会用 Express 过得很好。
最后的想法：Express 并不是免费 .net 开发的唯一选择，还有 SharpDevelop 与 Express 相比，它具有一些优势（SVN 集成、紧凑框架支持）。尽管我确信它也有很多限制。
Version comparisons can be found here: (For 2008) (Edit: A far more in depth document can be downloaded from here)
The things that leap out to me as features I wouldn't want to be without are:
If you can live without those (and the other limitations that wouldn't bother me personally) then I guess that you'll get by with Express just fine.
Final thought: Express isn't your only option for free .net development, there is also SharpDevelop which has some advantages (SVN integration, compact framework support) over Express. Though I'm sure it has many limitations too.
你有从事创业工作吗？如果您正在构建下一个杀手级应用程序，请查看 BizSpark：http://www.microsoft.com/bizspark /
Do you do any entrepreneurial work? If you're building the next killer app, check out BizSpark: http://www.microsoft.com/bizspark/
Microsoft 现在提供了一个新程序，允许 Web 开发人员访问 Microsoft Stack，类似于 BizSpark 程序。
它称为Website Spark。 VS 2008 Professional Edition 和 SQL Server 2008 Web Editon 是通过该程序提供的一些工具。
There is new program now available from Microsoft to allow web developers to access the Microsoft Stack similar to the BizSpark program.
It is called Website Spark. VS 2008 Professional Edition and SQL Server 2008 Web Editon are some of the tools available through the program.
在所有事情中，我可能会怀念安装扩展的能力。特别是像 AnkhSVN 和 TestDriven.NET 这样的工具对我来说变得非常宝贵......
我会认真考虑投资一些钱购买 VS，特别是如果你可以通过使用它来工作来收回一些钱。
也许切换到 Eclipse 和 Java 是您的一个选择？
编辑：
顺便说一句，投资几百美元在以前的学生中很常见。如果您是一名设计师，您可能需要在 Adobe 软件上投资 1000 美元。
Of all things I would probably miss the ability to install extensions. Especially tools like AnkhSVN and TestDriven.NET have grown invaluable to me...
I would seriously consider investing some money in purchasing VS especially if you can get some of that back by using it for jobs.
Maybe switching to Eclipse and Java is an option for you?
EDIT:
By the way, investing a few hundred dollars is common among ex-students. If you were a designer you would probably have to invest $1000 on Adobe software.
您将无法拥有具有多种项目类型的解决方案（因此没有混合语言解决方案），也无法拥有解决方案文件夹。
You won't be able to have solutions with multiple project types (so no mixed language solutions), or solution folders either.
主要缺少的是构建解决方案安装程序的能力。
解决方法是使用一些 .NET 开源安装程序来构建安装程序，例如 WiX。
而且多语言解决方案更加麻烦（例如混合C#和VB.NET）。
我使用专业版，但在快捷版中打开和构建我的项目/解决方案时没有遇到任何问题。
The main thing that is missing is the ability to build an installer for a solution.
The work-around is to build the installer using some open source installer for .NET, e.g. WiX.
And multi-language solutions are more cumbersome (e.g. mixed C# and VB.NET).
I use the Professional version, but I didn't experience any problems with opening and building my project/solution in the Express Edition.