VistaDB 3.4 Build 67

written by Jason Short on Tuesday, October 07 2008

These are the notes on what changed in the last few builds.  They have all been internal builds, or limited release builds for testing specific issues from customers.  I fully expect that we may see a few new issues pop up once we get this into a much larger base of users than our testing crowd.  As always backup your databases as a matter of good practice before upgrading.

3.3 and previous users

VistaDB 3.3 and previous users must uninstall those builds prior to installation.  The 3.4 line is built using a new installer and cannot detect the old installer.

Also check your GAC to ensure it is clean (navigate to your c:\windows\assembly folder and look for any left behind VistaDB dlls from previous installers).

Thank you

A very sincere thanks goes to all of you who helped us beta the entire 3.4 product release line.  It was a much longer release cycle than we intended. 

We expect to get into a groove of releasing stable builds about once a quarter and patches as needed during the interim.


Build #67, 10/06/2008

ISSUES AND FIXES
There was an issue with medium trust running the obfuscated dll.  The reflected code was apparently trying to run a check on the assembly that is not supported in Medium Trust. This has been resolved.


OTHER NON TICKETED ITEMS
Updated API help file generated



Build #66, 10/01/2008

NOTES
VistaDB License Manager is now an optional run at the end of the install.  It will walk you through getting a license online or emailing us your information.  In the interim you don't have to get a license, but you run in trial mode.

ISSUES AND FIXES
#1279:Security Exception testing for free memory on medium trust - the call to the check free memory may require elevated permissions.  Put a try/catch around that call for a security exception.  We fall back to the default memory allocation if we cannot query the OS.

OTHER NON TICKETED ITEMS
Minor changes to layout of files on install paths.



Build #65, 09/26/2008

NOTES
Partner Build for immediate fix.

ISSUES AND FIXES
#1257:"use default value in updates" broken - Fixed to work as previous releases.  Behavior changed in B63 but there was no regression test in place.

OTHER NON TICKETED ITEMS
Not released to the public.
 

Similar Posts

  1. Looking ahead to 2008, and back at 2007
  2. The first 120 days…
  3. The GC does not solve all memory leaks

Comments are closed

Options:

Size

Colors