Default Restructuring MVC3 Project Directories and NuGet

Question

I once watched TekPub video on MVC2 , which suggested renaming the Content folder as Public, adding scripts to this folder, etc.

Several developers whom I show MVC have preferred this structure and have tried it. However, with the inclusion of NuGet, it seems that folders are expected to be in standard places. For instance. JQuery I think it just fits in the \ Scripts folder. Guess what is the configuration convention.

Do I need to restructure the default folders at all, but explain to NuGet where to put them? Is it just a bad idea to change the default layout?

Answer 1

The problem is that at the present time, when you create the package, you specify in the .nuspec file the path to which the file will end up. So right now, everything is pretty hardcoded to go to / Content.

We discussed the possibility of adding virtual folders or placeholders to your .nuspec file. The end user can then define the mapping to say that all $ scripts files go to / public / js, etc.

You can see the discussion here http://nuget.codeplex.com/discussions/256542

We can create a problem for this and make people vote for it.

Answer 2

Nuget , . - , Nuget , .

, , - .