Geeks With Blogs

News Opinions and articles on this blog are mine alone and do not represent my employer. All articles and blog entries are posted using a personal computer system outside of my employer network.
Sam Abraham Software Engineer/Architect: Putting Customers First
We are currently in the process of upgrading one of our applications to .Net 4.0. Aside from us geeks wanting to always use latest and greatest technologies, an immediate business need for Silverlight 4.0 features justified our upgrade endeavor. The following is a summary of some issues we ran into with our web project:
For security purposes, the IIS 7 .Net 4.0 ISAPI filter is disabled. “Allow” it from the ISAPI and CGI Restrictions screen as shown:
Figure 1 - Allowing ASP.Net 4.0 ISAPI Filter
By default the Web Setup Project only requires the .Net Framework 4 Client Profile to be installed on target system, which offers a lighter weight install for client machines consuming .Net 4.0 applications. However, using certain .Net 4.0 features requires the full .Net 4.0 Framework as outlined in this link: We hence needed to update the installer to require the complete .Net 4.0 Framework on the target machine and to prompt for its installation if needed.
To accomplish this goal, we updated the installer’s launch conditions to check for .Net 4.0 as well as the installer prerequisites as shown:
Figure 2- Ensure Web Setup Project runs on full .Net 4.0 version

Figure 3 - Launch Conditions screen

Figure 4 - Set launch condition to .Net 4.0.

Figure 5 -Changing installer prerequisites

Figure 6 -Changing installer prerequisites

Posted on Thursday, December 23, 2010 10:01 AM , Tech Talk , ASP.Net 4.0 , .Net 4.0 , webdev , IIS7 | Back to top

Comments on this post: Fun Upgrading to .Net 4.0

No comments posted yet.
Your comment:
 (will show your gravatar)

Copyright © Sam Abraham | Powered by: