This is actually a .NET issue, not an IIS one. IIS resources wouldn't cover this because it only applies to .NET sites. Really just trying to reinforce the idea that you need to learn about .NET ...
Look at the Issue Tracking Starter Kit from www.ASP.NET. It might be a great place to start from. The starter kits I have played with have been fantastic beginnings to web applications. They are 100% ...
Some results have been hidden because they may be inaccessible to you
Show inaccessible results