title: Is this a correct approach to design N-layers?
body: <p>I am planning to create different layers, so in my Visual Studio Project, I will have:</p>
  
  <p>BusinessLayer:
  Contains Business objects (entities)
  i.e User, Employee, Products etc</p>
  
  <p>DataAccessLayer:
  Entity Framework</p>
  
  <p>Presentation Layers:
  The Views &amp; ViewModels</p>
  
  <p>So say for example, I want to let user login to this application.</p>
  
  <ol>
  <li>View will display the UI to let User to enter information.</li>
  <li>When User press enter, execute command => ViewModel</li>
  <li>ViewModel will use Entity Framework to query the User data from database, then ViewModel will initalize an User object (from BusinessObject ), and maps the User data to the User object.</li>
  <li>This User object then will store into a static parameter for future use.</li>
  </ol>
  
  <p>So what I really concern is:</p>
  
  <ol>
  <li>Is this correct way to design N-layers?</li>
  <li>Should I sperate each layers to different Visual Studio project?
  (i.e Business objects will be inside another project)</li>
  <li>Is it better to let Business Object to query the data it self? So in
  Business Object construtor will calls entity framework?</li>
  <li>Should I write a Repository class for use entity framework?</li>
  </ol>
  
  <p>I don't mind if this is complicated, because from what I have been told, this application will be huge.  So I want to design it properly, to make it flexible and extendable.</p>
  
  <p>Any advice will be great, thanks.</p>