.Net, ASP.Net, C#, VB.net, SQL Server, Xml, CSS, Design Patterns related tips, tricks, code snippets, articles, links, thoughts, etc. from Binu & Subi Thayamkery.

Binu Thayamkery is a seasoned software architect with more than 13 years of experience in developing enterprise grade connected systems using Microsoft Technologies. In his current position as a lead consultant-solution architect with Prudential Financial, he is working on architecture of next generation investment reporting framework using .net 3.5/WCF/AJAX, etc. He holds a Masters Degree in Computer Science from Colorado State University. Subi Thayamkery is an experienced software developer with more than 8 years of developing various application software systems ranging from workflow automation systems to compliance management tools. She currently works as a technology consultant for Prudential Financial where she helps develop a new system for corportate governance department. She holds an Electrical Engineering degree from New Jersey Institute of Technology.

Friday, February 15, 2008

ASP.Net v1.1 and v2.0 side by side

Its common knowledge that we can run ASP.Net v1.1 and v2.0 side by side. If both the versions of .Net frameworks are installed on the server, IIS management console will provide a new ASP.Net tab in the property page (right click on your IIS application/vdir, select properties). Here you can select which version of ASP.Net you want to target.

If you are moving from v1.1 up, it is highly probable that you will have some applications still using older versions of .Net, in that case your new application in the same server will need to be configrued for ASP.Net 2.0. Even after you run if you get an error saying "Server application not available", check to see whether new application is running under the same application pool as older ones. By default, it will be using DefaultApplication Pool. Create a new application pool and assign this pool for your new ASP.Net 2.0 application.

Cheers!