Friday, May 27, 2005

DCM: 4 new items added to the support page

jed-software.com Host change

Just to let people know, the ISP that hosts my www.jed-software.com domain is transferring to a different host this weekend. There may be some disruptions over the weekend because of this. If you are after the DCM or QC Client download, you can still download these from the old site www.alphalink.com.au/~jed/dcm.htm or www.alphalink.com.au/~jed/QC.

Unfortunately for people wanting support I will only have limited internet access from 5pm Friday to 5pm Sunday. Note these times are based on the GMT +10 time zone.

thanks.

Tuesday, May 24, 2005

DCM: Enabling Quality Insight for Delphi 2005

If you are running a Win32 based configuration, chances are you do not have Quality Insight enabled.

To enable Quality Insight load up your configuration in Delphi Configuration Manager and make sure the package exceptiondiag90.bpl is selected. Make sure you save the configuration.

Now if the IDE gives you an error, you will get the opportunity to send an error report to QualityCentral about the error. I encourage any users that are getting errors to submit their reports (you can do so anonymously if you like). The Quality Insight reports submitted prior to Update 3 helped the Borland engineers fix a bug in Update 3.

Once your report has been added, you can view them using a QualityCentral client. Naturally I recommend JED, QC available from www.jed-software.com.

Sunday, May 22, 2005

DCM: Delphi 2005 Update 3 Version

Borland has just released Update 3 for Delphi 2005.

If you are running a Win32 based configuration with Delphi 2005 the About Box will not be updated to indicate that Update 3 has been installed. This is because the Win32 configurations do not use a package that contains this information.

The package that provides this information to the IDE appears to be delphidotnetide90.bpl.
Naturally if you are running a Win32 configuration, you do not want to include this package as it isn't required.

To verify the update has installed correctly either check the Product Version value in the registry (HKLM\Borland\BDS\3.0\) or look at the timestamps of the files in $(BDS)\Bin\.

Update:
My files have a timestamp of 20/04/2005 2:03AM (dd/mm/yyyy). I'm Australian (GMT +10).