10thmagnitude/application_dotnet

application_dotnet's Issues

Should this depend on the IIS cookbook and ensure sites/pools exist?

Should the provider support managing the underlying app pool/iis site/application that is referenced in the resource?

i.e., if you use the application_dotnet_webapp resource, and reference that it should be installed in a certain IIS app, should the resource manage that IIS app idempotently as well (not for a practice perspective, but to prevent errors?)

maybe at the minimum do some error catching on it?

Provide ability to use a template resource for the web.config

Web.config will vary based upon attributes. Should provide a method to consume a template from an upstream cookbook for the web.config.

I'm not sure exactly the right design method for this, so it will require some discussion. Thoughts?

Should check for appropriate dependencies

This is a design question, and we might need to spend a little bike shedding time on it, but should the resource ensure that the appropriate dependencies exist? i.e, a webapp should ensure that w3svc is running, and a framework 4.5 app should ensure that framework 4.5 is installed?

Sample webapp throws an error when browsed to

When browsing to http://localhost/ApplicationDotNetSample, the following error:

HTTP Error 403.18 - Forbidden

The specified request cannot be processed in the application pool that is configured for this resource on the Web server.



Most likely causes:
•An ISAPI filter or custom module changed the URL to run in a different application pool than the original URL.
•An ISAPI extension (or custom module) used ExecuteURL (or ExecuteRequest) to run in a different application pool than the original URL.
•You have a custom error page that is located in one application pool but is referenced by a Web site in another application pool. When the URL is processed, it is determined by IIS that that it should have been processed in the first application pool, not the other pool.
•The Web site has multiple applications configured. The application this request is configured to run in is set to run in an application pool that does not exist.



Things you can try:
•If you have an application that is trying to process a URL in another application pool (such as trying to process a custom error), ensure that they both run in the same application pool if appropriate.
•If you are trying to process a custom error URL that is located in another application pool, enable the custom errors Redirect feature.
•Verify that the application pool for the application exists.
•Create a tracing rule to track failed requests for this HTTP status code and see if ExecuteURL is being called. For more information about creating a tracing rule for failed requests, click here. 



Detailed Error Information:



Module
   IIS Web Core 

Notification
   BeginRequest 

Handler
   ExtensionlessUrlHandler-Integrated-4.0 

Error Code
   0x00000000 



Requested URL
   http://localhost:80/ApplicationDotNetSample 

Physical Path
   C:\inetpub\wwwroot\ApplicationDotNetSample 

Logon Method
   Not yet determined 

Logon User
   Not yet determined