VS2010基本Web应用程序以及扩展的应用程序和版本控制

Question

Currently I have one base webapplication, lets call it "Framework.Presentation". This application contains all of the base items (default code and some default templates) of the web application. For multiple customers, I want to extend this base application with client specific code and templates. The base application is a subversion repository, and for each client we want a different subversion repository.

I had the following structure in mind:

ClientProject
  - Framework
    - Framework.Presentation
  - ClientProject.Presentation

The "ClientProject" is a repository on it's own, with an External to my Framework repository. In my ClientProject.Presentation project, I'll link to the Framework.Presentation project.

This isn't a problem, however:

In the Framework.Presentation I have some templates in the App_Data folder, lets say:

App_Data
  - Templates
    - Default
      - All the files here

In my ClientProject.Presentation I could add the same, without the folder 'Default'. The application will look first directly in the App_Data/Templates , and after it in App_Data/Templates/Default .

Also the Framework.Presentation has an '/Admin' folder, where users should be able to do some admin stuff of the web application.

If I publish the ClientProject.Presentation, all the files fall in place. However, if I want to debug the application in VS2010, the files of the Framework.Presentation aren't copied to the root folder of the ClientProject.Presentation project, so I can't debug all the functions. Also the application cant find his default templates.

In which way can I solve this?

Answer 1

OK, a potential solution is...

Using your file structure, you add the project ClientProject.Presentation to the solution.

You dont add the Framework.Presentation project. Instead you add each file individually to your ClientProject.Presentation as a link file . ( Add -> Existing Item , select the file, click the down arrow on the add button, and select Add As Link ).

This will ensure that the files are still saved in the appropriate location in the file system, but the IDE will know where they live in the solution.

The only drawback is this will be fairly tedious, depending on the size of your Framework.Presentation project.

Answer 2

You could possibly create a Framework.Presentation DLL that is referenced by your ClientProject.Presentation project. You would need to configure your Framework files as embedded resources. I haven't tried this, so I'm not sure how well it would work.

Answer 3

You could use the pre-build event as you suggested to copy all the files from the Framework.Presentation folders to the ClientProject.Presentation . However I suspect that this might get messy. For example:

• How do you handle filename clashes?
• Would you need to exclude the Framework.Presentation files in the ClientProject.Presentation folder so you don't accidentally commit them to subversion.
• Would you also need to automatically update the ClientProject.Presentation project to reference these files? If not, how will they get built and debugged? If so, how do you handle the project reload?
• How would you handle the extra files for clean builds, build server integration, deployment packages, etc.

Answer 4

Create a wrapper solution. In this you should have all of your projects. Add a post build step to do all of the copying ect. You're not going to find a simple or clean solution to your problem. If you're not well acquainted with MSBuild you will be soon. It is certainly capable of doing everything you want, it's just going to be tedious.