Working with IIS in a virtual directory (did not test as seperate site, but I expect it will work fine)

1.  ApplicationOAuthProvider.ValidateClientRedirectUri handles virtual directories now.
2.  Many resharper cleanups
3.  Some other code refactorings
4.  require.js configuration now done in require.configuration.js
5.  security.js takes base url of site into account

Some outside the project activities need to occur for IIS to work.  
Mostly so the app pool can access the localDB database.
Maybe there is a way to add these items so that they run after the build, in the case that IIS is selected.
I didn't make those changes because I don't know if it's better to handle that for the user, or to just document the following somewhere in the template

1.  After the DB is created, run from the command line:
```
	sqllocaldb share v11.0 IIS_DB
```
2.  Edit c:\Windows\System32\inetsrv\config\applicationHost.config
Add a node similar to the following to the applicationPools section.
```xml
<add name="ASP.NET v4.0" autoStart="true" managedRuntimeVersion="v4.0" managedPipelineMode="Integrated">
	<processModel identityType="ApplicationPoolIdentity" loadUserProfile="true" setProfileEnvironment="true" />
</add>
```
Or if you were using the DefaultAppPool	
```xml
<add name="DefaultAppPool" autoStart="true" managedRuntimeVersion="v4.0" managedPipelineMode="Integrated">
	<processModel identityType="ApplicationPoolIdentity" loadUserProfile="true" setProfileEnvironment="true" />
</add>
```
Also the following needs to be run in the database to setup the app pool as a user of the database.
```sql
	create login [IIS APPPOOL\DefaultAppPool] from windows;  --assumes DefaultAppPool, change to ASP.NET v4.0 if needed
	exec sp_addsrvrolemember N'IIS APPPOOL\DefaultAppPool', sysadmin
	go
```