Put this in the location bar of your web browser :
I'm happy to hear that the next VS ASP.NET designer will be huge!
It will fix some stuff and bring nice value additions to the poor actual VS2005 one :
I've just noticed that a new beta version of the Internet Explorer Developer Toolbar is available! Not yet final but I like this Web Developer tool. No more toolbar menu in IE but a shortcut button instead, which open the bottom panel, the menu is inside this one now (but I think toolbar will be back again soon, or at least as an option).
Despite all the cool things in it I advise people NOT to install this version as it is far for stable and some features simply crash.
If you still want to try it, don't forget to uninstall previous beta versions.
Still in beta but it comes with enhancements over previous versions, including:
- Style Tracer: Right mouse click on a style value for an element and select Style Tracer to find the style rule that is effecting that value.
- CSS Selector Matches: View a report of all style rules set and how many times they are used on the current page.
- View Source: View the formatted and syntax colored source of the original page, currently rendered page, element or element with the styles that are effecting it.
What is it?
In case you don't know this IE extension, here is the official description:
You've deployed your app in prod server, you run it on the browser and you get an exception:
These days I was working on a web app dealing with large amount of data.
When it comes to display these data we use GridView and enable pagination in one click.
First thing to know is by default ASP.NET 2.0 GridView default paging is very poor in terms of performance because it first gets all data from db, and then trims the results to render the current page. And it does the same when you change to next page and the others!
Note that it was the same problem with ASP.NET 1.x DataGrid, then you had to implement custom paging to make things smart, that means getting only data that you need to display if you have multiple pages in your grid.
With ASP.NET 2.0 you can very easily use custom paging, without writing a line of code behind!
Scott Mitchell wrote a very good article on how to implement this using the SQL Server 2005 new ROW_NUMBER() keyword and configuring your Object Data Source properly :
Problem is my current app is using SQL Server 2000...
But chance is Greg Hamilton wrote a very nice tutorial to do the same in SQL Server 2000 using the SET ROWCOUNT command :
A More Efficient Method for Paging Through Large Result Sets in SQL Server 2000
One more thing on the same idea of performance, many people, when creating primary key/foreign key relationships for joigning tables forget that while an index is automatically created on the primary key column, an index for a foreign key IS NOT automatically created, and must be created manually if needed. That could help if your paging's query use JOIN clauses.
And the final touch, now that we have Top efficient SQL work, we can move the GridView inside an ASP.NET AJAX UpdatePanel and let users navigate through data without PostBack!
If you have 1 min and VS already opened, just try this :
The definitive Coder's Happy New Year.
I have been blog-tagged by Etienne, so I need to list 5 personnal things. Easy for me to tell 5 things others may not know about me as... few people know me !
My name is Laurent Duveau and I'm a .NET developer in Montréal, Canada.
What a surprise this morning for the very first day of the year... I was awarded MVP by Microsoft !!!
2007 couldn't start better for me !