Sometimes our experiences are not what we think they are...
-
http://blogs.msdn.com/dougste/archive/2008/02/29/should-i-authenticode-sign-my-net-assembly.aspx[^] The above article talks about how an ASP.NET web app was slow to start up the first time. I've seen comments from various people about this problem over the years, and usually it's someone claiming they "tried" ASP.NET and were not impressed with the speed or some such. I guess it goes to show that our experiences are not always what we think they are. You have to give something an honest effort sometimes to know for sure if your initial reaction is true as rule, or as an exception.
-- Where are we going? And why am I in this handbasket?
-
http://blogs.msdn.com/dougste/archive/2008/02/29/should-i-authenticode-sign-my-net-assembly.aspx[^] The above article talks about how an ASP.NET web app was slow to start up the first time. I've seen comments from various people about this problem over the years, and usually it's someone claiming they "tried" ASP.NET and were not impressed with the speed or some such. I guess it goes to show that our experiences are not always what we think they are. You have to give something an honest effort sometimes to know for sure if your initial reaction is true as rule, or as an exception.
-- Where are we going? And why am I in this handbasket?
Erik Funkenbusch wrote:
You have to give something an honest effort sometimes to know for sure if your initial reaction is true as rule, or as an exception.
Yeah, true enough. But to be fair, i've used a lot of ASP.NET apps that are slow to start up. Or heck, just plain slow. At some point, you have to ask: who out there is actually making an honest effort, initially or ever?
But who is the king of all of these folks?
-
http://blogs.msdn.com/dougste/archive/2008/02/29/should-i-authenticode-sign-my-net-assembly.aspx[^] The above article talks about how an ASP.NET web app was slow to start up the first time. I've seen comments from various people about this problem over the years, and usually it's someone claiming they "tried" ASP.NET and were not impressed with the speed or some such. I guess it goes to show that our experiences are not always what we think they are. You have to give something an honest effort sometimes to know for sure if your initial reaction is true as rule, or as an exception.
-- Where are we going? And why am I in this handbasket?
asp.net is dreadfully slow on first access and works great every other time. This is especially true if your app is part of sharepoint, heck even sharepoint it's self. In addition I post updates often to my perimeter web server for customers review, and of course the customer is the first one to access the site after I publish. Solution, write application that wakes up every so often and traverses published web sites (even ones that require log in). No more calls from customers. Yea. Kinda proud of it, easy to write about 15 lines of code or so.
MrPlankton
modified on Friday, February 29, 2008 2:29 PM
-
asp.net is dreadfully slow on first access and works great every other time. This is especially true if your app is part of sharepoint, heck even sharepoint it's self. In addition I post updates often to my perimeter web server for customers review, and of course the customer is the first one to access the site after I publish. Solution, write application that wakes up every so often and traverses published web sites (even ones that require log in). No more calls from customers. Yea. Kinda proud of it, easy to write about 15 lines of code or so.
MrPlankton
modified on Friday, February 29, 2008 2:29 PM
MrPlankton wrote:
Solution, write application that wakes up every so often and traverses published web sites (even ones that require log in). No more calls from customers. Yea.
I like it! Good one. Of course they may start asking about it when they see you in their access logs. Seems as though it's something that should be built into asp.net as an option in the web config or something, to keep assemblies in cache.
When everyone is a hero no one is a hero.
-
asp.net is dreadfully slow on first access and works great every other time. This is especially true if your app is part of sharepoint, heck even sharepoint it's self. In addition I post updates often to my perimeter web server for customers review, and of course the customer is the first one to access the site after I publish. Solution, write application that wakes up every so often and traverses published web sites (even ones that require log in). No more calls from customers. Yea. Kinda proud of it, easy to write about 15 lines of code or so.
MrPlankton
modified on Friday, February 29, 2008 2:29 PM
You can pre-compile the site and also use NoCompile pages in conjunction with web application projects. That helps a lot.
You have, what I would term, a very formal turn of phrase not seen in these isles since the old King passed from this world to the next. martin_hughes on VDK