[英]Development environment for ASP.NET with EpiServer
At our company we are going to develop more for the Windows platform than we have done up until now. 在我们公司,我们将为Windows平台开发比迄今为止更多的开发工作。 As this scale of Windows development is new to us it would be nice with some feedback from experienced developers. 由于这种Windows开发规模对我们来说是新的,所以它会得到经验丰富的开发人员的一些反馈。
Requirements we have: 我们的要求:
Our idea: 我们的想法:
Questions: 问题:
Comment answer: 评论答案:
I second Numenor's comment -- go with a free source control like Subversion. 我第二张Numenor的评论-与Subversion之类的免费源代码控件一起使用。 I would be scared to develop on Terminal Services for the simple reason that Visual Studio can be a resource hog if you start doing any debugging. 我很害怕在终端服务上进行开发,原因很简单,因为如果您开始进行任何调试,Visual Studio可能会占用大量资源。 I'm assuming you're going to have more than one person on the project at a time, and I'd think you could get desktops that would work out better for a lower price than a large server that could accommodate those types of terminal server sessions. 我假设您一次将有一个以上的人参与该项目,并且我认为您可以以比一个可以容纳这些类型终端的大型服务器更好的价格获得价格更低的台式机服务器会话。
On top of that, if you have multiple people working on a project on the same physical box, you're going to have problems with two people changing one file...back to the source control recommendation. 最重要的是,如果在同一物理盒子上有多个人在处理一个项目,那么两个人更改一个文件将会遇到问题...回到源代码管理建议。
Andrew Siemer has some great articles outlining how to set up a development environment. 安德鲁·西默(Andrew Siemer)有几篇精彩的文章,概述了如何设置开发环境。 Interestingly enough, they're in his series-in-progress about setting up a StackOverflow type of site. 有趣的是,他们在他的有关设置StackOverflow类型站点的正在进行的系列文章中。 Start with this one , then follow the series to get the scoop on automated builds. 从本教程开始 ,然后按照该系列教程进行自动化构建。
Edit: You probably don't want to use CodePlex as Andrew outlines, but a private Subversion server would work the same way with TortoiseSVN. 编辑:您可能不想像Andrew概述的那样使用CodePlex,但是私有Subversion服务器将与TortoiseSVN相同。 You can get Subversion from CollabNet . 您可以从CollabNet获得Subversion。
Since you are referring to EPiServer my recommendation is to use Visual Studio's built in web server on each developer's PC. 由于您是指EPiServer,所以我的建议是在每位开发人员的PC上使用Visual Studio的内置Web服务器。 Then get some kind of Windows Server and run SQL Server and IIS on it. 然后获得某种Windows Server并在其上运行SQL Server和IIS。 Also use some kind of DNS service that allows you to create sub domain host names that you use to run multiple port 80 sites on the IIS. 还使用某种DNS服务,该服务允许您创建用于在IIS上运行多个端口80站点的子域主机名。
I don't know the exact terms but you might be able to run SQL Developer Edition in this scenario instead of Express. 我不知道确切的用语,但您可以在这种情况下而不是Express上运行SQL Developer Edition。 Then you get the full set of management tools, no size limit on databases and support to import and export data. 然后,您将获得全套的管理工具,对数据库没有大小限制,并且支持导入和导出数据。 If you got customers with both 2005 and 2008 SQL Servers you should run both versions as two different instances so that you can move, create and restore database backups easily between environments. 如果您同时拥有2005和2008 SQL Server的客户,则应将这两个版本作为两个不同的实例运行,以便可以轻松地在环境之间移动,创建和还原数据库备份。
Developers all connect to the same database while developing and when appropriate deploy their projects to the server's IIS web site. 开发人员都在开发时连接到相同的数据库,并在适当的时候将其项目部署到服务器的IIS网站。 If you like you can allow a customer to use it as test site. 如果愿意,可以允许客户将其用作测试站点。
I would put the free VisualSVN Server on the server too and use that instead of CVS. 我也将免费的VisualSVN Server放在服务器上,并使用它代替CVS。
I would also look into renting this as a virtual server somewhere and use some kind of VPN to access it. 我还将研究将其作为虚拟服务器租借到某处,并使用某种VPN对其进行访问。
If you can live with the limitations I don't see any problems using VS Express. 如果可以忍受这些限制,那么使用VS Express不会出现任何问题。
Good luck! 祝好运!
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.