Geek Answers Handbook

Can I reuse ASP.NET MVC Views for different projects?

This is the next question to question .

This is a good solution for sharing common ideas in many projects using a control source. However, I have a few Subversion specific questions that I think.

Subversion Externals allows you to include a folder from a separate repository in your working copy, so you can define the "External" property in the root of the working copy that the folder added: [/ Web / Views / Forum], for example.

  • What happens if you want to override one of these views with a version related to one of the dependent projects?
  • If you added an extra view to this folder, will SVN transfer it to the shared repository?

Is the answer at this point “wait for MVC2,” since I believe it is better for such scenarios?

Thanks GC

+5
source share
1 answer

svn: external links are not the answer to your problem.

Just to clarify: when using svn: externals you really add a link to the actual external repository. No matter what you modify / add / delete and commit (if you have access to an external repository) from your working copy, you will simply be bound to this repository. All others using the same repo (whether external or not) will receive these changes on subsequent updates.

, , . , , .

. , , ASP.Net MVC 2. , , " " mvc2 mvccontrib

+2

More articles:


All Articles