Installing MSSQL 2000 instance on top of MSSQL 2005

I experienced the issue of installing a SQL 2000 instance on top of an existing installation of SQL 2005. Having had the same frustration of not being able to see the 2000 instance remotely I searched and found this article. " must install SQL 2000 SP4 before 2005" on an article gave me a bit of a panic, but is a hint as to the solution.

SQL 2005 requires that you select "Allow remote connections to access this computer" on the Connections tab of server properties. It also requires that the "SQL Server Browser" service is running.

I checked these and found that installing the SQL 2000 had disabled the "SQL Server Browser" service. Restarting this service allowed remote connection to both the sql Server 2000 and 2005 instances.

IE8 Standards mode and IE7 Compatibility mode

 Unfortunately, not all web sites confirm to IE8 standards today. If you have concerns about your web site rendering correctly in IE8 standards mode, then there is some help for you out there:
You can address the issues on a page-by-page basis using the following HTTP meta-tag:

<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />

This tag, when seen by IE8 will render the page in IE7 compatibility mode regardless of whether or not you’ve set IE to run in IE8 Standards mode or not.  This is a great solution for that one page in the site that doesn’t quite render correctly in Standards mode.

Note: Including this in the Asp.net Master Page(s) will cater for IE7 compatibility in all the Content Pages that use the Master Page.

for more info : http://www.ditii.com/2008/08/28/ie8-standards-mode-and-ie7-compatibility-mode/

AjaxControlToolkit and SmartNavigation

After spending almost 4 hours investigating the following problem with an Ajax extension object:

‘Error: Sys.ArgumentTypeException: Object of type ‘AjaxControlToolkit.PopupBehavior’ cannot be converted to type ‘AjaxControlToolkit.PopupBehavior’.
I finally realized the page was using the smartNavigation directive. This directive has become obsolete with .NET 2.0, you can now use Page.SetFocus() and Page.MaintainScrollPositionOnPostBack() instead to obtain similar result. However, during the upgrade process from 1.1, the wizard didn’t flag this directive as a problem, so I was not aware of its presence until I came across the problem above.
Anyway, I was not surprised that upon removing this directive, the page was no longer throwing the javascript exception.
Lesson learned.

source : http://rafsystems.com/2007/05/22/ajaxcontroltoolkit-and-smartnavigation/