带有 EpiServer 的 ASP.NET 开发环境
在我们公司，我们将为 Windows 平台开发比迄今为止更多的产品。由于这种规模的 Windows 开发对我们来说是新的，因此如果能得到经验丰富的开发人员的一些反馈就好了。
我们的要求：
- 从一开始就有 5 名开发人员。
- 一年后将有 15 名开发人员。
- 所有开发人员应该能够同时开发。
- 能够为 ASP.NET 和 EpiServer 5 开发解决方案。
我们的想法：
- 开发人员通过终端服务用于开发的共享服务器。
- SQL Server Express。
- 从一些免费的 Visual Studio Express 版本开始，如果我们需要附加功能，请升级到商业版本。
- 使用 IIS 而不是 Visual Studio 中内置的 Web 服务器。
问题：
- 我们走在正确的道路上吗？
- 就许可费用而言，上述应该是最便宜的，对吧？
- 您如何看待多个开发人员使用共享 TS 服务器进行开发？
- 您知道有哪家公司拥有类似的开发环境吗？
- 我们会立即错过完整 Visual Studio 版本的某些功能吗？使用 Express 版本是一个糟糕的选择吗？
- IIS 是最佳选择吗？如果使用IIS，开发人员可以使用相同的端口进行部署。如果我们使用内置的网络服务器，每个人都必须设置自己的端口，因为我们共享一台机器。
评论答案：
- 我们正在考虑共享服务器，因为它很可能会降低许可成本。所以这纯粹是一个成本问题。我们使用 CVS 进行版本控制。我们的情况是在 Mac 和 Linux 上进行开发，这就是为什么购买 1 个服务器许可证 + Visual Studio 许可证似乎是开始此类开发的一种经济高效的方式。
At our company we are going to develop more for the Windows platform than we have done up until now. As this scale of Windows development is new to us it would be nice with some feedback from experienced developers.
Requirements we have:
- 5 developers from the beginning.
- 15 developers a year from now.
- All developers should be able to develop at the same time.
- Be able to develop solution for ASP.NET and EpiServer 5.
Our idea:
- A shared server which developers use for development through Terminal Services.
- SQL Server Express.
- Start with some free express edition of Visual Studio, upgrade to a commercial version if we need the additional features.
- Use IIS and not the web server built into Visual Studio.
Questions:
- Are we on the right track?
- In terms of license costs the above should be cheapest, right?
- What do you think about multiple developers doing development using a shared TS-server?
- Do you know of any company which has a similar development environment?
- Are we going to miss some features of the full Visual Studio version immediately? Is using Express version a bad choice?
- Is IIS the best choice? If use IIS the developers may use the same port for deployment. If we use the built in web server each one has to set their own port as we're sharing a machine.
Comment answer:
- We are thinking about a shared server as it will most likely decrease the license costs. So it's purely a cost issue. We are using CVS for version control. Our situation is that we develop on Mac and Linux, that's why buying 1 server license + Visual Studio licenses seems to be a cost effective way of starting this type of development.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
由于您指的是 EPiServer，我的建议是在每个开发人员的 PC 上使用 Visual Studio 的内置 Web 服务器。然后获取某种 Windows Server 并在其上运行 SQL Server 和 IIS。还可以使用某种 DNS 服务，该服务允许您创建用于在 IIS 上运行多个端口 80 站点的子域主机名。
我不知道确切的术语，但在这种情况下您也许可以运行 SQL Developer Edition，而不是 Express。然后您将获得全套管理工具、数据库大小无限制并支持导入和导出数据。如果您的客户同时使用 2005 和 2008 SQL Server，您应该将这两个版本作为两个不同的实例运行，以便您可以在环境之间轻松移动、创建和恢复数据库备份。
开发人员在开发时都连接到同一个数据库，并在适当的时候将其项目部署到服务器的 IIS 网站。如果您愿意，您可以允许客户将其用作测试站点。
我也会将免费的 VisualSVN Server 放在服务器上并使用它来代替 CVS。
我还会考虑在某处租用它作为虚拟服务器，并使用某种 VPN 来访问它。
如果您能忍受这些限制，我认为使用 VS Express 不会有任何问题。
祝你好运！
Since you are referring to EPiServer my recommendation is to use Visual Studio's built in web server on each developer's PC. Then get some kind of Windows Server and run SQL Server and IIS on it. 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.
I don't know the exact terms but you might be able to run SQL Developer Edition in this scenario instead of Express. 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.
Developers all connect to the same database while developing and when appropriate deploy their projects to the server's IIS web site. 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.
I would also look into renting this as a virtual server somewhere and use some kind of VPN to access it.
If you can live with the limitations I don't see any problems using VS Express.
Good luck!
我赞同 Numenor 的评论——使用像 Subversion 这样的免费源代码控制。我害怕在终端服务上进行开发，原因很简单，如果您开始进行任何调试，Visual Studio 可能会占用大量资源。我假设您一次会有多个人参与该项目，并且我认为您可以获得比可以容纳这些类型终端的大型服务器以更低的价格更好地工作的台式机服务器会话。
最重要的是，如果有多个人在同一个物理机器上处理一个项目，那么两个人更改一个文件就会遇到问题……回到源代码控制建议。
Andrew Siemer 有一些很棒的文章概述了如何设置开发环境。有趣的是，他们正在他正在进行的关于建立 StackOverflow 类型网站的系列中。 从这个，然后跟随该系列了解自动化构建的独家新闻。
编辑：您可能不想像 Andrew 概述的那样使用 CodePlex，但是私有 Subversion 服务器可以与 TortoiseSVN 一起以相同的方式工作。您可以从 CollabNet 获取 Subversion。
I second Numenor's comment -- go with a free source control like 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. 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. Interestingly enough, they're in his series-in-progress about setting up a StackOverflow type of site. 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. You can get Subversion from CollabNet.