Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I read over the msdn page on the -i here. I’ve never even used this tool before. I’ve always configured my apps in IIS just fine. So why would anyone need to use this for .NET 2.0 or 3.5 web apps?
I’m running IIS 7 on a Win 7 PC, do I even need this?
This is something that you don’t normally need to use, is more for troubleshooting than for doing anything standard.
Sometimes there’s issues with the .NET framework installation on IIS so ASP.NET applications don’t work quite properly. To solve this you need to re-install ASP.NET on IIS, the most common way to do that is, first doing
aspnet_regiis -uto uninstall and thenaspnet_regiis -ito re-install.This is something that you normally won’t need to use, I have very seldom used it, but the times I have, it saved my life.
It used to be more common on “older” versions of the .NET Framework, like 1.0, 1.1 and maybe 2.0 but after .NET 3.0 the use of these commands is very, very rare.