Wednesday, March 29, 2006

The only way I can find to change the template for the "New Stored Procedure..." command in SQL Server Management Studio is by digging around in the file system:

C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\sqlworkbenchprojectitems\Sql\Stored Procedure\Create Stored Procedure (New Menu).sql

This short and easy to remember path seems to be the file that matches the command.  If you find a better way, please let me know!

Wednesday, March 29, 2006 10:37:49 PM (Central Daylight Time, UTC-05:00)  #    Disclaimer  |  Comments [2]  | 
 Tuesday, March 28, 2006

I have to admit, I’m a little confused.  Joel Spolsky – well-known in the software development blogger community – wrote a post in June of 2004 commenting on Microsoft’s dedication to backwards compatibility.  He cites the following story as an example of this dedication:

I first heard about this from one of the developers of the hit game SimCity, who told me that there was a critical bug in his application: it used memory right after freeing it, a major no-no that happened to work OK on DOS but would not work under Windows where memory that is freed is likely to be snatched up by another running application right away. The testers on the Windows team were going through various popular applications, testing them to make sure they worked OK, but SimCity kept crashing. They reported this to the Windows developers, who disassembled SimCity, stepped through it in a debugger, found the bug, and added special code that checked if SimCity was running, and if it did, ran the memory allocator in a special mode in which you could still use memory after freeing it.

Spolsky goes on to say that in the “Raymond Chen days” this was not unusual for Microsoft.  A quick search of Raymond Chen’s blog for the word “compatibility” confirms this – 66 posts containing the word at least once.  To really get a feel for the importance that Microsoft placed on supporting current customers, you need to read a few of these posts by Chen.
 
In Spolsky’s article, he praises Microsoft for their previous dedication to backwards compatibility, and then laments what he sees as Microsoft’s trend away from backwards compatibility…

Enter March 2006 – Vista is behind schedule.  The New York Times publishes the article “Windows Is So Slow, but Why?”  Their analysis?  Microsoft puts too much emphasis on backwards compatibility and not enough on new innovation. 

Eh?  So who’s right?  Spolsky or The New York Times?

The fact of the matter is that Microsoft is the market leader.  They have a “slight” majority of the market share, and with that majority they feel the need to help their customers make the jump to the next version.  They know – rightly so – that companies don’t have time to sit around and re-write applications that already work fine.  If companies won’t spend time to re-write, then the customers who require those applications can’t upgrade to the latest and greatest (Vista.)  If no one upgrades, Microsoft doesn’t get paid.  And being a business (a fairly successful one at that), Microsoft feels the need to insure some return on their investment – pretty simple.  In addition, they’re not going to start loosing customers any time soon.  The same companies that won’t do a slight re-write for the next version of Windows, surely not going to do a complete re-write to run their apps on a Unix, Linux, or Mac box.

Would it be nice to have Vista before Christmas?  Sure - I’m sure Dell would love it even more - but no one would buy the product when they realized that the applications they want to run no longer work.

Tuesday, March 28, 2006 5:52:24 PM (Central Daylight Time, UTC-05:00)  #    Disclaimer  |  Comments [1]  | 
 Thursday, March 23, 2006

Be sure to get the latest and greatest IE and the compatible developer toolbar - both released this week

Thursday, March 23, 2006 4:59:56 PM (Central Daylight Time, UTC-05:00)  #    Disclaimer  |  Comments [0]  | 
 Friday, March 17, 2006

I just discovered beta 2's new Print Preview dialog, and it's a vast improvement over IE 6.  Notice the UI for changing the page margins - very intuitive.  My only complaint is that it's painfully slow to draw.  Hopefully they'll get it optimized for the RTM.

Friday, March 17, 2006 6:42:06 PM (Central Daylight Time, UTC-05:00)  #    Disclaimer  |  Comments [0]  | 
 Monday, March 13, 2006

I came across an interesting forum post by Suzanne Cook today.  Here's what she had to say about 1.1 assemblies and 2.0 assemblies in the same process:

As of today, only one version of the runtime is loaded per process, no matter which versions of assemblies are later requested.  So, if the v2 CLR is already loaded, it will successfully load a v1 assembly and run it against the v2 CLR (not the v1 CLR) without reloading the already-loaded v2 CLR .dlls.

While we're on this topic, you may want to check out http://blogs.msdn.com/suzcook/archive/2005/01/26/361092.aspx for related compatibility information.

Tuesday, March 14, 2006 12:27:36 AM (Central Daylight Time, UTC-05:00)  #    Disclaimer  |  Comments [0]  |