最佳做法设立＆QUOT;企业＆QUOT;在Visual Studio项目？ [英] Best practices for setting up an "enterprise" project in Visual Studio?

问题描述

我是一个企业风格的应用程序的发展，为6名员工的很小的企业preparing（包括我自己 - 你的问题之前，为什么一个6人的公司需要一个企业应用，我们有很多怎么回事了很多简化它）所需要的流程和工具。与往常一样，我试图按照设立该项目的最佳做法;我将使用.NET 3.5，与数据库是在Windows Server 2003 / SQL Server 2005的。

而我开发和测试的解决方案，我应该有我的主要项目中的一切？我的意思是... Visual Studio 2008专业让你有数据库项目，以及为所有其他类型的项目。对于这个应用程序，我将需要：

• 包含新的数据模式的创建和测试脚本，数据库项目

包含实际code /应用
• C＃项目：
  
  
  
  1. 使用ASP.NET MVC面向客户的网站（S）
  
  
  2. 后端的订单处理系统，可能是基于网络的，但可能是智能客户端
  
  


• 包含包ETL活的应用程序通过我们的供应商（S）提供的数据和现有的客户和订单数据从旧的数据库迁移在SSIS项目。


• 为SQL Server Reporting Services的报表项目

基本上，我想知道，如果它有所有这些为一个庞大的Visual Studio解决方案的一部分，是一个好主意（我们称之为EnterpriseSolution），或者如果我要打破出来，并单独解决这些问题。大部分时间我已经看过了书籍和网站包括它们放在一起，但他们也假设一个开发团队中，DBA，架构师之类的 - 在这种情况下，我所有的人都集于一身。该数据库项目和至少一些ETL流程需要完成，加载到生产应用程序的其余部分之前写的，因为我们需要加载新的供应商的产品在实际环境中（开始出售它们）。

我来，我应该如何开始这个结构有点不知所措，但我想拿出一个总体规划前，我就开始奠定的东西，并开始编码。

就如何解决一个项目像这样有什么建议？

解决方案

这绝对是用在它的几个项目一个解决方案好主意。如果你想使用ASP.NET MVC定义每个层中的一个C＃项目：MVC的Web，服务层，数据访问层和独立的测试项目。
您可以从罗布科纳的店面示例应用程序或<一个学习HREF =HTTP：//www.$c$cplex.com/oxite/Release/ProjectReleases.aspx ReleaseId = 23315相对=nofollow> Oxite

您可以尝试使用也指导套餐从模式和放大器;实践团队：

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

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.

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:

• Database Project containing the create and test scripts for the new data schema
• C# projects containing the actual code/application:
  1. Customer-facing web site(s) using ASP.NET MVC
  2. Back-end order processing system, probably web-based but possibly a "smart client"

• SSIS project containing packages to ETL the "live" application data provided by our vendor(s) and migrate over existing customer and order data from the legacy database.
• Reporting project for SQL Server Reporting Services

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?

解决方案

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

这篇关于最佳做法设立＆QUOT;企业＆QUOT;在Visual Studio项目？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！