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...

This build is designated as a development build because we made a change in the optimizer that could affect a lot of applications.  We don't expect it to cause any problems (it fixes one possible error case), and you are free to Go Live with it with your products.  We just ask that you test your code and let us know if there are any problems.

Logging Build

This build is a full logging build.  Logging does not happen automatically against every run of the engine.  You have to turn it on from the Diagnostics namespace, and the Customer Experience tray app has to be running with logging enabled.  By default the only thing we are logging in the CEIP application are Data Builder runs, and the Visual Studio tools (logging exceptions, errors, etc).

To turn on diagnostic logging within your application

At app or unit test startup you would call the startup like this:

VistaDB.Diagnostic.Support.BeginLogging("Starting Test to demo some error"); 

Then during your application shutdown call the EndLogging method:

VistaDB.Diagnostic.Support.EndLogging("Test shutdown complete");

You could also do the begin and end just around a problem area as well.

There are two boolean options on the logging right now to turn on additional information.  By default we only log exceptions and errors in the engine process.  If you are having a problem with an output being incorrect, or some other SQL specific problem you can turn these two options on to log more detailed information.

VistaDB.Diagnostic.Support.IncludeCommandSQL = true;
VistaDB.Diagnostic.Support.IncludeDataReaderRows = true;

The IncludeCommandSQL includes each SQL command that is executed and the parameters passed as a part of the query.
The IncludeDataRows will log each row returned to the command (NOT recommended unless REALLY necessary to see a problem since these rows can get quite large).

Issues and Fixes

Changed the optimizer code to be a little more deliberate in its choice of indexes.  There was an error case where a compound index containing two columns also had a duplicate index covering the first column of the compound index.

More...