title: Is Dependency Injection a must in asp.net MVC?
body: <p>I am currently viewing multiple tutorials (and reading books) to start working with ASP.NET MVC.</p>
  
  <p>I see that ninject (or similar) is widely used to implement Dependency injection and from what i understood the main issue here is resource allocation from the classes i need. </p>
  
  <p>We want to be sure  for example that we have only one instance of the repo object.</p>
  
  <p>I need to learn first things first so i am interested in knowing how i would create an ASP.NET MVC without using DI techniques and still be correct as far as my object resources are concerned</p>
  
  <p>More info:</p>
  
  <p>I have made some winforms applications. These apps where using a Business Layer DLL (BLL). This BLL had access to my DAL DLL (plain ADO.NET). they are working quite well..</p>
  
  <p>No i want to use the SAME BLL to MVC apps. </p>
  
  <p>With injection or not?</p>
  
  <p>Without injection implementation?</p>
  
  <p>Do i just create the BLL object in my controller constructor and that's all?</p>