When is Response.IsClientConnected slow?
I have a long running ASP response (actually an MVC action) that I want to cancel if the user has navigated away. I think this should be fairly simple:
I have a long running ASP response (actually an MVC action) that I want to cancel if the user has navigated away. I think this should be fairly simple:
Which one of the following two methods has better performance ?
I have simple ASP.NET application which just resizes images with ImageResizer and does nothing else. For testing purposes I disabled disk caching, so images are resized on every request.
I am using File upload control in ASP.Net, followed the below blogs approach.
I have a list: Collection users which has around 100K+ records of users (all user objects fully loaded from the database with fields like Bio, First name, last name etc). This collection is fetched on application start from the database and is kept in memory.
I’ve been looking for a good tutorial to teach me how to make a customized Paging control with a simple DataBound control like Repeater to implement a high performance paging feature.
I have started to use New Relic to monitor the performance of http://alternativeto.net that is a fairly large website.
I use ‘n’ number of server controls in my page. Now I am into performance tuning and I’ve noticed that my ViewState is too large and it makes my page slow.
I have been trying for a week now to reduce the number of requests on our web application but I can’t seem to combine the .axd files. I got a suggestion from somewhere which worked locally (development box) but doesn’t work on our test and production environment as they are both on HTTPS. The developer didn’t comment on that and the component he wrote was last updated in 2011. (I will find the link and update this post).
In my ASP.net project I need to validate some basic data types for user inputs. The data types are like numeric, decimal, datetime etc.