Geek asks and answers

Do I really need the contents of App_Start in Ninject.MVC3?

Downloading the Ninject.MVC3 package from NuGet creates this App_Start folder with a simple class; I would add that it doesn't even compile out of the box.

Looking through it, it has no impressive ... functionality ... or at all. I also did not find it in SampleApplicationfor Ninject.Web.Mvc, from which the project itself. (Https://github.com/ninject/ninject.web.mvc/tree/master/mvc3/src/SampleApplication)

Can someone explain the purpose of this folder / class? Removing them does not seem to affect my project. Is there any mystical reason for the ninja why should I keep them? (or even why are they made in the first place?)

+3
source share
3 answers

Ninject.MVC3 App_Start. NinjectMVC3.cs, Ninject. , NinjectMVC3. WebActivator bootstrapper Ninject. NinjectMVC3 Microsoft.Web.Infrastructure, Ninject, NinjectMVC3 WebActivator.

NinjectMVC3 RegisterServices, . , .

Ninject MVC . global.asax.cs .

+1

= "". , -, .

http://weblogs.asp.net/pjohnson/archive/2012/09/07/mvc-4-and-the-app-start-folder.aspx

, , -. .

The usual case with ASP.NET custom folders is that they provide different security permissions. Does anyone know if this App_Start folder is needed in a partial trust environment? that is, with limited web hosting, is this the only place where you can call functions to change the way the site is routed?

It seems that someone from MS is thinking of adding this as an additional layer of security in the future, if it does not already exist. Until I see the real benefits of this, I will simply remove it.

0
source

More articles:


All Articles