We have posted updates to all of the new SKUs released earlier this month.  Each SKU if present in your account will show the downloads in the VistaDB 4 area of the download site.

Each of the downloads below have been tested to work with Visual Studio 2008 and Visual Studio 2010.

Existing current account holders will have their existing product sku replaced with the new ones over the next few days.  Then you will see these in your download section.

There is no new engine build as a part of this update.

Addons vs Engine Builds

Add-ons will not be updated at each new build of the engine.  In most cases nothing changes in the Add on SKUs.  When we have changes in them we can now release them independent of the release cycle for the main engine. 

For now we will keep the same version number as whatever the current VistaDB 4 engine was at that time.  All of these downloads are flagged as Build 14 because that is when they were released.  But in the future they may skip several releases of the engine.  Only the most recent version of each will be kept in the download site to avoid confusion.

More...

Build #14

We are very pleased to release Build 14 of VistaDB 4.0.  There are a number of small fixes present, but the biggest reason for this release was that Build 13 had an installer bug preventing users from installing on 32 bit machines, or machines with only the TFS Shell installed (not the full VSTS, just the shell).  This was causing quite a few people to not be able to start their trial. 

Trial Users

We have reset all trial start dates from when Build 13 was released in order to give everyone a new trial window. 

When asked if you want to use your existing trial license click No, and enter your trial email address to get a new trial license.  It will expire 30 days from the day you get the trial license.

Server Explorer Nodes

We had to rotate a GUID for 4.x to avoid a conflict in 3.x (see below).  This results in all current Server Explorer nodes for 4 prior to Build 14 not working with Build 14.  Remove all VistaDB Server Explorer nodes prior to upgrading to avoid an error in Visual Studio after installing Build 14.  If you have already upgraded see the NOTES section below for details on how to fix this post install.

There was a conflict between VistaDB 3 and VistaDB 4 being used in strongly named datasets on the same machine.  This was due to one GUID in the DDEX provider not being rotated when we moved to 4.x.  After installing Build 14 or higher you can now have both side by side, but the 3.x install is broken after removing 4.0 prior to Build 13.  See the NOTES section below for how to repair your 3.x install.

More...

Build #13

This build has a lot of minor changes from user tickets, but the major update is for Visual Studio 2010 RC.

Visual Studio 2010 RC

Visual Studio 2010 RC now works.  There were several changes in Visual Studio between beta 2 and the RC with respect to data providers and plugin installation.  We have fixed these issues. 

Hopefully the Visual Studio 2010 final release will not introduce any more surprises.  Beta 2 has not been tested with this build, we do not intend to support it.

VistaDB 3 and 4 side by side in Visual Studio 2008

There is a conflict that impacts Visual Studio 2008 side by side of our two data sources.  Once VistaDB 4 has been installed Visual Studio 2008 still knows about VistaDB 3.x, but it will not show it for new connections from the Server Explorer (this will impact Strongly Typed Datasets that reference Server Explorer connections). 

In order to fix this you will need to first uninstall VistaDB 4 prior to build 13. 

Then run InstallDesigner for VistaDB 3 from the VistaDB 3 install path like this:

C:\Program Files (x86)\VistaDB 3\VisualStudio\InstallDesigner.exe  ( 32 bit users will not have an x86 in the program files )

After running this command line tool you should see the VistaDB 3 entry in Visual Studio 2008 again. 

Finally, install VistaDB 4 build 13 or higher and you will have two entries present.

Changes and Fixes

There are a number of small changes from user tickets.  Read through the list below if you are looking for something specific.

More...