.NET Framework 4.0 not registered on IIS during installation - by Zbynek Bartos

Status : 

  Not Reproducible<br /><br />
		The product team could not reproduce this item with the description and steps provided.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 736573 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 4/12/2012 8:57:31 AM
Access Restriction Public


In some cases .NET 4.0 installer doesn't register the on IIS. .NET 4.0 should be registered properly on IIS already during .NET installation and no further command (aspnet_regiis.exe -iru) should be needed.
Sign in to post a comment.
Posted by Microsoft on 5/14/2012 at 10:28 AM
Running aspnet_regiis during your custom installer is a suitable workaround, and indeed this is what the built-in Web Deployment Projects do. Any further questions about the behavior of aspnet_regiis would be better made on the ASP.NET forum topic at http://forums.asp.net/26.aspx/1?Configuration+and+Deployment
Posted by Zbynek Bartos on 5/10/2012 at 9:18 AM
I'm just considering maybe a warkaround to this issue: To run 'aspnet_regiis.exe -ir' command before every application installation run (i.e. just to integrate 'aspnet_regiis' command into installation process).

I guess it could be helpful. But I'm worrying about all consequences on the production server. Perhaps all web application already installed and running on the server will be down for a while. But could it cause any other unexpected problems?

According to the aspnet_regiis options description, '-ir' option should only register .NET, without any other application affecting, right?
Posted by MS-Moderator10 [Feedback Moderator] on 4/13/2012 at 3:26 AM
Thanks for your feedback. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Zbynek Bartos on 4/13/2012 at 12:07 AM
We need to know any warkoround or anything else about the issue aproximately within a week. Could be, do you think?
Posted by MS-Moderator01 on 4/12/2012 at 9:49 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)