I did a simple "Hello World" in ASP.NET 4.0 and want to test it. When I went to the IIS tool panel below, I got a "warning" (see 'Attention!' below). If I click on changing the ASP.NET Version, and some of my other applications break, can I go back to ASP.NET 3.5? Or are the changes I make in the IIS Tool Control Panel for version reversible? That is, if some of my 3.5 version apps break, can I just use the drop-down box in the Control Panel tool to go back to ASP.NET 3.5? If not reversible it's not worth it for me. I am perfectly happy hosting several ASP.NET 3.5 applications on DASP, and they work fine. If the changes are not reversible using just the drop-down box I may not risk switching to ASP.NET 4.0 at this time. Please let me know. Thank you, PJ2010 IIS Tools: ASP.NET Version This tool allows you to select the ASP.NET Version and the Application Pool Pipeline Mode of your hosting account. NOTE: ASP.NET 4.0 is only available on our Windows 2008 platform. NOTE: Our Windows 2008 platform does not support ASP.NET 1.1. Attention! You have selected to change your hosting account to ASP.NET Version 4.0. IMPORTANT: The selected ASP.NET Version will be applied to your entire website.
...Wait a sec, don't give in yet. Try adding this to your root web.config in the system.web section: <pages controlRenderingCompatibilityVersion="3.5" clientIDMode="AutoID" /> ...See if that helps. I'm pretty sure you can fall back to the previous asp.net version but try that first. ;-) All the best, Mark
did not work Did not help, but thanks anyway. Below is the web.config file, and it's a simple blank page that says "Hello World". I get the error shown in APPENDIX B below when I load the usual string, ending with Default.aspx, into my browser. The browser / server chokes on this attribute line in the config.web file: "<compilation debug="true" targetFramework="4.0"> Clearly my site, which is 3.5, does not expect or recognize this attribute. If I delete it, I get an even more complex error message. For now I will stick to Visual Studio 2008 for ASP.NET, framework 3.5, unless I hear a guarantee that I can go back to 3.5 from 4.0 if I switch, using the DASP tool, to 4.0. Thanks again, PJ //WEB.CONFIG FILE-- <?xml version="1.0"?> <configuration> <appSettings/> <connectionStrings/> <system.web> <!-- Set compilation debug="true" to insert debugging symbols into the compiled page. Because this affects performance, set this value to true only during development. --> <compilation debug="true" targetFramework="4.0"> </compilation> <!-- The <authentication> section enables configuration of the security authentication mode used by ASP.NET to identify an incoming user. --> <authentication mode="Windows"/> <!-- The <customErrors> section enables configuration of what to do if/when an unhandled error occurs during the execution of a request. Specifically, it enables developers to configure html error pages to be displayed in place of a error stack trace. <customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm"> <error statusCode="403" redirect="NoAccess.htm" /> <error statusCode="404" redirect="FileNotFound.htm" /> </customErrors> --> <pages controlRenderingCompatibilityVersion="3.5" clientIDMode="AutoID"/></system.web> <!-- The system.webServer section is required for running ASP.NET AJAX under Internet Information Services 7.0. It is not necessary for previous version of IIS. --> </configuration> APPENDIX B: Server Error in '/HiWorld3A' Application. Configuration Error Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately. Parser Error Message: Unrecognized attribute 'targetFramework'. Note that attribute names are case-sensitive. Source Error: Line 10: during development. Line 11: --> Line 12: <compilation debug="true" targetFramework="4.0"> Line 13: </compilation> Line 14: <!-- Source File: E:\web\MYCOMPANYNAMEHERE\htdocs\HiWorld3A\web.config Line: 12
...Man that stinks. It looks like this should be working, you're doing it the compilation correctly and it's in the correct section. Making changes to your root web.config should also cause a recycle. I'm at a loss here bro. All the best, Mark
see this https://support.discountasp.net/KB/a796/aspnet-40-application-error-unrecognized-attribute.aspx
How much to get two websites going? Today I found out--in case anybody reads this thread in the future--that, as hoped for, you can go back and forth from ASP.NET 4.0 to 3.5 using the IIS tool found here: https://my.discountasp.net/web-manager/iis7-framework.aspx but there's a small catch... The only problem, is that if your applications break using ASP.NET 4.0, and you want to go back to 3.5, you have to go into the Web Application Tool (found here https://my.discountasp.net/webapplication-tool.aspx) for each app, including Silverlight apps, then Remove / Add for each app using the Tool. Then Stop/Start using the IIS panel https://my.discountasp.net/web-manager/iis7-stopstart.aspx And then you are back to your old version of ASP.NET 3.5. My question for this thread, how much does it cost to have two websites going, one running under ASP.NET 3.5, and one under ASP.NET 4.0? I found that for Windows XP (one machine I use for development) and Visual Studio 2008, ASP.NET 3.5 is fine. For Vista/Windows 7 and Visual Studio 2010 (on another machine I use), I might switch for new apps to ASP.NET 4.0. But I don't want to fiddle with the web.config files for the old apps that work fine under ASP.NET 3.5 (too much hassle for me--I think it's harder than it appears to get the old apps to work--short of perhaps republishing them and tweaking them individually, which might be time consuming). I'd rather just pay to have two websites--one running under ASP.NET 4.0 and one running under ASP.NET 3.5--if it's not too much money. DASP has very reasonable prices I found (I forget what I'm paying every month, it's that low!)...so maybe there's a discount for an existing customer to have two versions running? If I don't hear back in this thread in a week or so, I'll just email the sales department. PJ
Since both frameworks cannot run on one account at the same time, you would have to open a second account to use both. If you open a ticket with Sales/Marketing they may be able to hook you up with a discount or a promo offer.
