title: How does IIS7 authorization work when setting up an application outside of wwwroot
body: <p>I tried to add a new application in II7 and point it to another directory on my hard drive outside of wwwroot. I have it under the default app pool and connecting as an application user. The application contains simple static html pages not asp.net and this is my development server and will only be used for just that.</p>
  
  <p>When I try to access the application it throws an error. I did a bit of research on this and the advice I got was to add NETWORK SERVICE to the physical path of the application. This did not work. I then did some more research and instead of using NETWORK SERVICE I added ISUR. This worked.</p>
  
  <p>Out of this I drew two vague conclusions:</p>
  
  <ul>
  <li>NETWORK SERVICE is used for asp.net applications</li>
  <li>IUSR is used for static html pages</li>
  </ul>
  
  <p>Can someone please confirm this.</p>
  
  <ul>
  <li>Is it then safe to say that if my asp.net applications contains html files I would need to add both accounts to my physical path to make it run correctly?</li>
  <li>It also sounds to me that since this a development machine it is probably easier to just connect as and use the account I am logged in with on Windows. Am I right?</li>
  <li>Finally, if I would have addded my test application in a folder under wwwroot instead, would everything have worked since wwwroot and its folders are already setup with the correct privileges for static html and asp.net?</li>
  </ul>
  
  <p>Thank you for all your help.</p>
  
  <p>P.S. any blogs on how to get up to speed with IIS7 would be highly appreciated.</p>