This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
When we try to run, it looks like Lightspeed is requiring a specific (old) version of VistaDB. We receive the following error: Could not load file or assembly 'VistaDB.NET20, Version=3.3.1.54, Culture=neutral, PublicKeyToken=dfc935afe2125461' or one of its dependencies. The system cannot find the file specified.
I have, installed locally and set to copy local (plus in the GAC) VistaDB 3.3.1.57 (which is the oldest licensed version available), and it's failing to find/load this file. Is there a build that works against the newer releases of VistaDB, preferably 3.5? (Or even the 4.0RC?) |
|
|
|
|
The current nightly builds of LightSpeed are built against VistaDB 3.5.2.84 (July 2009). You can get the nightly build from the downloads page (free edition) or the store (retail edition). Let us know if you still see problems! |
|
|
|
|
Ivan, Thanks for your response. We've tried updating, and now we can run, but unfortunately, I'm not sure exactly where and how you got 3.5.2.84 of VistaDB. The current released version (for paying customers, too), is 3.5.1.84, and the only pre-release versions are the 4.0 branch. Although we can now build, we get compatibility warnings. Are there plans to either move the nightly to the VDB4 tree, or at least go to the latest released VDB version, since the one you're using doesn't seem to be available on VistaDB's site now? |
|
|
|
|
Hmm, that's strange. The version we build against came from the VistaDB site, and was the current released version at the time. So I'm not sure why the build number would be incorrect. We'll investigate this and update the nightly builds to 3.5.1.84 if appropriate. In the meantime, it might be worth adding a binding redirect to your config file and see if that resolves the warnings. Regarding moving to VDB4, the impression I get from the VistaDB site is that VDB4 is a potentially compatibility-breaking change (e.g. they had an article about migrating file formats). So we will probably switch to VDB4 as part of LightSpeed 3 (by which time VDB4 will be fully released). We would welcome feedback from you or other VistaDB users on this. |
|
|
|
|
Thank you for looking into it. I managed to eliminate some warnings via Binding redirects, but there is still one that we cannot avoid, unfortunately. I just logged in again now and verified- the VistaDB current release is 3.5.1.84, and then there is the 4.x betas. As for VistaDB 4 - From what I've seen, the API is very close. But there are definite compatibility changes to the files, so it probably requires a separate provider (? - just a guess). It is in the final release candidate now, though (Build 5), so, from our point of view, it would be great to be able to migrate to using 4 for our development work, since we're targeting a release date that will be far enough forward to be post-VDB 4 release. I'm not sure what your plans are for timing for LightSpeed 3 - but VistaDB 4 has some huge advantages (and will probably perform much better for LightSpeed), so we'd love to use it ASAP.
Thank you for your responses! -Reed |
|
|
|
|
Actually, on reflection, there's nothing that stops us offering separate VistaDB3 and VistaDB4 providers, thus However, there are some commercial details to be worked out between us and the VistaDB folks before we can do this. Hopefully we can do this quickly but that's not always been possible in previous discussions. I'll post again on this thread when we know how quickly we'll be able to move on this. |
|
|
|
|
Thank you very much Ivan. We're commercial customers of VistaDB (with multiple licenses), so if it helps - you can always show them this thread (or ask, and I'll contact them) as proof that their user base wants LightSpeed/VistaDB integration. Sometimes being able to say that there are current, paying customers of theirs asking can help get things moving. ;)
-Reed
|
|
|
|
|
Hi Reed, Just posting an update to say I've got in touch with Jason Short about obtaining a license so that we can support VistaDB vNext better for our users. He's going to get back to me soon so hopefully we'll have our hands on the required bits in the very near future. I'll keep you updated as things progress :-) Kind regards, John-Daniel Trask |
|
|
|