Related Links

Empty project template mvc4

I really like that aspnetmvc is a nuget package, and the empty project should only contain this.. why is web api there? why is entity framework there? since there is not any controller the other "crap" should not be there when the word empty is used.

Then we have the script folder. The jquery libs are old references.. remove knockout, modernizer, jquery ui... empty perhaps means that there should not be any scripts?

It would be really nice if the empty project contained there bare minimal needed to run an mvc site.

Re: Empty project template mvc4

daniel.persson

Please clean up the empty project template!

I really like that aspnetmvc is a nuget package, and the empty project should only contain this.. why is web api there? why is entity framework there? since there is not any controller the other "crap" should not be there when the word empty is used.

Then we have the script folder. The jquery libs are old references.. remove knockout, modernizer, jquery ui... empty perhaps means that there should not be any scripts?

It would be really nice if the empty project contained there bare minimal needed to run an mvc site.

I agree with your openion. But think yourself if someone created an empty project then it will quickly need to add controllers, views, entity framework, widely used script libraries, http services, etc. It will be very painfull for lot of developers(using
MVC 3 empty project template) to explicitly add(or through nuget) jquery, modernizer, ef, etc. So, these elements are there to quickly add them in your project. If a developer not using these elements they can leave(or delete) them.

Re: Empty project template mvc4

If you want to use a standard boilerplate then you will probably not choose something that is called Empty in the first place. Every time I create an Empty project, the first thing I have to to is remove all noise (and I have not heard of anyone who doesn't).
If I were to create a site where I want a working shell then I would choose something named accordingly (like Standard-template or Intranet-template). It is more natural to add something to an empty-template solution than to delete from it - which is why your
argument is confusing. Hope this makes sense?

Re: Empty project template mvc4

daniel.persson

If you want to use a standard boilerplate then you will probably not choose something that is called Empty in the first place. Every time I create an Empty project, the first thing I have to to is remove all noise (and I have not heard of anyone who doesn't).
If I were to create a site where I want a working shell then I would choose something named accordingly (like Standard-template or Intranet-template). It is more natural to add something to an empty-template solution than to delete from it - which is why your
argument is confusing. Hope this makes sense?