N1: I tried MVC on mono-develop in Linux and that worked.
N2: There are both advantages and disadvantages. I use visual studio pro and I don't exactly know what's different in Mono-develop. I know there are some features available in mono-develop that are available in visual studio with plugins only, not in the express version.
N3: I think personal preference will decide what's better for you. I think the easiest way to find out is to download the Mono Vmware image and try it. You might have to update the mono-develop packages to use the MVC features of mono-develop. You can use the vmware image with the free version of vmware. Personally I prefer Visual Studio pro because I'm used to it and I'm addicted to resharper.
N3：这是一个很难做出的决定。 我还没有尝试过 MonoDevelop，所以我认为这取决于每个 IDE 之间的开发人员经验，看看哪一个更重要：兼容性易用性（参见 N2），或开发易用性，仅处理兼容性测试/移植。
N1: I'm sure there will be plenty of folks that will try out MonoDevelop for ASP.NET MVC.
N2: If you're focusing more on a cross platform experience with your application, I would say MonoDeveop is the way to go since your apps written in MonoDevelop are sure to run on Mono. If you use Visual Web Developer Express, you're still going to need to run MOMA or some other compatibility checking application to make sure that there has been any Mono incompatible libraries/methods injected into the architecture.
N3: That's a hard call to make. I haven't tried out MonoDevelop yet, so I think it would depend on the developer experience between each IDE and see which one weighs heavier: the compatibility ease (see N2), or the development ease, and simply dealing with the compatibility testing/porting.
VisStud is so much better than MonoDevelop with all of the auto-* stuff. But there is danger in not understanding what the stud generates. My choice is to use VisStud to develop in and port to Mono periodically.
N1: I have not used MVC so I can't anything abt it yet. N2: MonoDevelop is like pro edition of VS, but it doesn't have good designer. But lacks some important features like reports. N3: For web my preference will be VWD but for other stuff I'll prefer MonoDevelop and SharpDevelop
发布评论
评论（4）
N1：我在 Linux 中尝试了 MVC 进行单一开发，并且成功了。
N2：既有优点也有缺点。 我使用 Visual Studio Pro，但我不太清楚 Mono-develop 有什么不同。 我知道 mono-develop 中提供了一些功能，这些功能仅在带有插件的 Visual Studio 中可用，而在 Express 版本中则不可用。
N3：我认为个人喜好会决定什么对你更好。 我认为最简单的方法是下载 Mono Vmware 映像 并尝试一下。 您可能需要更新 mono-develop 软件包才能使用 mono-develop 的 MVC 功能。 您可以将 vmware 映像与免费版本的 vmware 一起使用。 就我个人而言，我更喜欢 Visual Studio pro，因为我已经习惯了它并且我对 resharper 上瘾了。
N1: I tried MVC on mono-develop in Linux and that worked.
N2: There are both advantages and disadvantages. I use visual studio pro and I don't exactly know what's different in Mono-develop. I know there are some features available in mono-develop that are available in visual studio with plugins only, not in the express version.
N3: I think personal preference will decide what's better for you. I think the easiest way to find out is to download the Mono Vmware image and try it. You might have to update the mono-develop packages to use the MVC features of mono-develop. You can use the vmware image with the free version of vmware. Personally I prefer Visual Studio pro because I'm used to it and I'm addicted to resharper.
N1：我确信会有很多人会尝试使用 MonoDevelop for ASP.NET MVC。
N2：如果您更关注应用程序的跨平台体验，我认为 MonoDeveop 是最佳选择，因为用 MonoDevelop 编写的应用程序肯定可以在 Mono 上运行。 如果您使用 Visual Web Developer Express，您仍然需要运行 MOMA 或其他一些兼容性检查应用程序，以确保已将任何 Mono 不兼容的库/方法注入到体系结构中。
N3：这是一个很难做出的决定。 我还没有尝试过 MonoDevelop，所以我认为这取决于每个 IDE 之间的开发人员经验，看看哪一个更重要：兼容性易用性（参见 N2），或开发易用性，仅处理兼容性测试/移植。
N1: I'm sure there will be plenty of folks that will try out MonoDevelop for ASP.NET MVC.
N2: If you're focusing more on a cross platform experience with your application, I would say MonoDeveop is the way to go since your apps written in MonoDevelop are sure to run on Mono. If you use Visual Web Developer Express, you're still going to need to run MOMA or some other compatibility checking application to make sure that there has been any Mono incompatible libraries/methods injected into the architecture.
N3: That's a hard call to make. I haven't tried out MonoDevelop yet, so I think it would depend on the developer experience between each IDE and see which one weighs heavier: the compatibility ease (see N2), or the development ease, and simply dealing with the compatibility testing/porting.
VisStud 在所有 auto-* 方面都比 MonoDevelop 好得多。 但不了解螺柱会产生什么是有危险的。 我的选择是定期使用 VisStud 进行开发并移植到 Mono。
VisStud is so much better than MonoDevelop with all of the auto-* stuff. But there is danger in not understanding what the stud generates. My choice is to use VisStud to develop in and port to Mono periodically.
N1：我还没有使用过 MVC，所以我还不能做任何事情。
N2：MonoDevelop就像VS的专业版，但它没有好的设计器。 但缺乏一些重要的功能，如报告。
N3：对于网络，我更喜欢 VWD，但对于其他东西，我更喜欢 MonoDevelop 和 SharpDevelop
N1: I have not used MVC so I can't anything abt it yet.
N2: MonoDevelop is like pro edition of VS, but it doesn't have good designer. But lacks some important features like reports.
N3: For web my preference will be VWD but for other stuff I'll prefer MonoDevelop and SharpDevelop