In the former case, the account that IIS Express uses is the account you use to log on to your
Windows machine. This account is usually something like DomainNameUserName or MachineName
UserName. While logged in with this account on Windows, you start up Visual Studio, which in
turn starts up IIS Express. This means that the entire web server runs with your credentials. Because
it’s likely that you’re an Administrator or a power user on your local Windows machine and have
permissions to access all files that make up your site, things probably worked fine so far without any
changes to the security settings.
In the latter case, where IIS is used, things are quite different. By default, an ASP.NET application
under IIS runs with a special account created when you installed IIS. This account is called
ApplicationPoolIdentity.
You won’t fi nd the ApplicationPoolIdentity user account on your system directly, because it depends
on the name of the configured application pool.
Because the application pool you saw earlier runs in Integrated Pipeline mode, you only need to
configure a single user account. If you are running in Classic mode (which isn’t necessary for the
Planet Wrox website) you also need to configure another account called IUSR. This account is used
by IIS to serve non-ASP.NET content such as HTML fi les and images. Consult the IIS documentation
for more information about Classic mode and the IUSR account.
After you have determined the account that you need to configure, the final step is to configure the
filesystem.