performance?
-
Hello Does anyone knwos if there is any performance gain in this conversion: Plain Old ASP code, with file a virtual includes to ASPX, maintaining the same site structure. Just renaming .asp to .aspx and making the apropriate code tuning. Thanks
-
Hello Does anyone knwos if there is any performance gain in this conversion: Plain Old ASP code, with file a virtual includes to ASPX, maintaining the same site structure. Just renaming .asp to .aspx and making the apropriate code tuning. Thanks
I think by definition there is. As classic ASP is always interpreted code, and ASP.NET is always compiled (at least after the first use) code... compiled is faster than interpreted. How much of a performance gain that is, or whether it is percievable for you, I don't know. happy new year! :beer:
-
Hello Does anyone knwos if there is any performance gain in this conversion: Plain Old ASP code, with file a virtual includes to ASPX, maintaining the same site structure. Just renaming .asp to .aspx and making the apropriate code tuning. Thanks
Max Santos wrote:
Just renaming .asp to .aspx and making the apropriate code tuning.
You realise the 'code tuning' is a rewrite, right ? Any code you leave in the aspx, rather than codebehind, will get compiled every time, you'll be where you started, assuming it all even works. Christian Graus - Microsoft MVP - C++
-
I think by definition there is. As classic ASP is always interpreted code, and ASP.NET is always compiled (at least after the first use) code... compiled is faster than interpreted. How much of a performance gain that is, or whether it is percievable for you, I don't know. happy new year! :beer:
It would be good to know... are those a lot of pages?? it could be rather hard to acomplish this, IMO :omg:... daniero
-
Max Santos wrote:
Just renaming .asp to .aspx and making the apropriate code tuning.
You realise the 'code tuning' is a rewrite, right ? Any code you leave in the aspx, rather than codebehind, will get compiled every time, you'll be where you started, assuming it all even works. Christian Graus - Microsoft MVP - C++
Christian Graus wrote:
Any code you leave in the aspx, rather than codebehind, will get compiled every time
Thats my point... But because i have no time to a complete rewrite, and aparently old ASP on IIS6 is much slower that ASPX (and i have no IIS5 at hand) i was thinking on a "quick and dirty" fix:-D
-
Christian Graus wrote:
Any code you leave in the aspx, rather than codebehind, will get compiled every time
Thats my point... But because i have no time to a complete rewrite, and aparently old ASP on IIS6 is much slower that ASPX (and i have no IIS5 at hand) i was thinking on a "quick and dirty" fix:-D
I'd do some testing before worrying too much. Christian Graus - Microsoft MVP - C++
-
It would be good to know... are those a lot of pages?? it could be rather hard to acomplish this, IMO :omg:... daniero
Not as hard as to do a complete rewrite with codebehind in the time frame i have available ;)
-
Not as hard as to do a complete rewrite with codebehind in the time frame i have available ;)
oh ok, I thought you were going to leave the code and just translate asp to asp.net in the page... that's what it first seemed like :). daniero
-
Hello Does anyone knwos if there is any performance gain in this conversion: Plain Old ASP code, with file a virtual includes to ASPX, maintaining the same site structure. Just renaming .asp to .aspx and making the apropriate code tuning. Thanks