设立“企业"的最佳实践Visual Studio 中的项目?

问题描述

我正在准备为一家只有 6 名员工的小型企业(包括我自己)开发企业风格的应用程序——在您质疑为什么一家 6 人的公司需要企业应用程序之前，我们有很多工作要做需要很多流程和工具来简化它).与往常一样，我在设置项目时尝试遵循最佳实践；我将使用 .NET 3.5，数据库在 Windows Server 2003/SQL Server 2005 上.

I am preparing for the development of an enterprise-style application for a very small business of 6 employees (including myself -- before you question why a 6-person company would need an enterprise application, we have a lot going on with a lot of processes and tools needed to simplify it). As always I'm trying to follow best practices in setting up the project; I'm going to be using .NET 3.5, with the database being on Windows Server 2003/SQL Server 2005.

在我开发和测试解决方案时，我的主项目中是否应该包含所有内容?我的意思是... Visual Studio 2008 Professional 允许您拥有数据库项目"以及所有其他类型的项目.对于此应用程序，我将需要:

While I'm developing and testing the solution, should I have everything in my main project? What I mean is... Visual Studio 2008 Professional lets you have "database projects" as well as all of the other types of projects. For this application I'm going to need:

• 包含新数据架构的创建和测试脚本的数据库项目
• 包含实际代码/应用程序的 C# 项目:

• Database Project containing the create and test scripts for the new data schema
• C# projects containing the actual code/application:

1. 使用 ASP.NET MVC 的面向客户的网站
2. 后端订单处理系统，可能基于网络，但也可能是智能客户端"

SSIS 项目包含对我们供应商提供的实时"应用程序数据进行 ETL 和迁移旧数据库中的现有客户和订单数据的包.

SQL Server Reporting Services 的报表项目

基本上，我想知道将所有这些作为一个大型 Visual Studio 解决方案的一部分(我们称之为EnterpriseSolution")是否是个好主意，或者我是否应该将它们分解并单独处理它们.我看过的大多数书籍和网站都将它们放在一起，但它们也假设有一个由开发人员、DBA、架构师等组成的团队——在这种情况下，我将他们全部合二为一.在编写应用程序的其余部分之前，需要完成数据库项目和至少一些 ETL 流程并将其加载到生产环境中，因为我们需要在实时环境中加载新供应商的产品(以开始销售).

Basically, I am wondering if it's a good idea to have all of these as part of one massive Visual Studio solution (let's call it "EnterpriseSolution"), or if I should break them out and tackle them separately. Most of the books and websites I've looked at include them all together, but they also assume a team of developers, DBAs, architects and the like - in this case I'm all of them rolled into one. The database project and at least some ETL processes need to be done and loaded into production before the rest of the application is written, since we need to load the new vendor's products in a live environment (to start selling them).

我有点不知所措，我应该如何开始构建它，但我想在开始布置和开始编码之前提出一个整体计划.

I'm a little overwhelmed as to how I should begin to structure this, but I want to come up with an overall plan before I begin to lay things out and start coding.

对于如何处理这样的项目有什么建议吗?

Any suggestions on how to tackle a project like this?

推荐答案

使用一个包含多个项目的解决方案绝对是个好主意.如果要使用 ASP.NET MVC，请为每一层定义一个 C# 项目:MVC Web、服务层、数据访问层和单独的测试项目.您可以从 Rob Conery 的 Storefront 示例应用程序或 Oxite.

It's definitely good idea to use one Solution with several projects in it. If you want to use ASP.NET MVC define one C# Project for each layer: MVC Web, Service layer, Data Access Layer and separate test project.You can learn from Rob Conery's Storefront sample application or Oxite.

您也可以尝试使用来自模式和的指导包实践组:

You can try also to use Guidance Packages from patterns & practises group:

http://msdn.microsoft.com/en-us/practices/default.aspx

这篇关于设立“企业"的最佳实践Visual Studio 中的项目?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！