If you want to try out the LINQ Preview, I mentioned in my previous post then make sure that you have VS 2005 RC1 installed. It will install even if Beta 2 is available but will screw up VS and the only solution currently seems a format.
ASP.NET 2.0 boasts of a new Menu control. You can create multi-level menus using this. It is not the best, but is decent enough to satisfy most common needs.
One thing that I had a problem with recently, is that if you have a multi-level menu, clicking a parent will result in a postback to the server. This was not a problem, till we decided we would improve the performance by turning viewstate off for controls that did not need them. Now suddenly, when you click the top level item, certain controls in the current screen will lose state.
The way out is to set the selectable property of items that is not mapped to an action. This way not only do we avoid unwanted postback, but also get around a need to have unwanted viewstate.
I remember reading an article on how CLR Stored Procedures are faster than TSQL server side cursors to loop thru records in the server (I seem to have lost the link to that article).
I was working on some performance tuning on some stored proc which used server side cursors. So I thought maybe moving them to CLR proc may improve performance. So I did a small test with a dummy cursor, incrementing a counter inside the loop. For a table with 50K records, the TSQL proc took around 3 secs, while the CLR proc took <1 sec.
The procedure I was tuning, really loops thru the table takes certain columns, does some computations and checking (some complex logic here, which is why I had to use cursors in the first place) and then updates another table with the final value. So I converted the TSQL proc to a CLR stored proc and checked the performance. The CLR proc was taking longer than the TSQL proc. My guess is that the TSQL proc, though it has a slower cursor, seems to have faster execution of the Update statements. Since there were 50K updates to be done, I guess the performance gains due to the faster cursor was overshadowed by the slower updates taking place.
So, there is no easy rule on performance when comparing TSQL and CLR procs. Do a performance test before you choose which to use.
Was just playing around in VS 2005 Beta 2. In the machine.config, the processModel section has an attribute autoConfig="true". But I am unable to find any documentation for this particular attribute. A google search resulted in a link to a winfx help page, which seems to have been modified and currently contains no reference to auto config.
So does this mean, this was a new feature that has been removed or is it a new attribute that has not yet been documented?
If you are trying to run the new Profiler that ships with SQL 2005, Feb CTP and above on Windows 2003 (Currently I am running the April CTP and the problem exists there too), you may have some problems. Usually there are no error messages, it just runs and sits in the task manager, but no UI appears. Nor does it run correctly from the command line. Nothing really happens.
The problem seems to be due to the new profiler exe being signed. The way to get it to run is to install the Windows 2003 SP1.
More information about this problem is available here.
If you are trying to create Test projects with the Visual Studion Team System 2005, and get the following error:
Then it most probably means that you have not installed the Team Foundation Client. Looks like this is a known issue with Beta 2. This may also occur if uninstallation of Beta 1 is not correct. You can try using the Beta 1 removal tool available for download at http://go.microsoft.com/fwlink/?linkid=47065.
Thanks to Hong Gao for the post that helped solve this problem.
Browsing around I just found this post which contains a consolidated list of posts on how you can uninstall a .NET 2.0 beta/CTP installation. Now with Beta 2 available, I am sure quite a few of you would want to remove the older Beta 1 or CTPs to install the new Beta 2..:-)