Using the method suggested here to redirect the vistadb connector to a newer version of the driver build 38 or build 40 fail

This can be shown easily enough by using either build and running the demo

 I suppose it is possible I did something wrong but I sure do not know what that is

---

"The difference between genius and stupidity is that genius has its limits." - Albert Einstein

The redirection should work, many of our VistaDB folks have used that trick. However, we are having trouble maintaining a relationship with VistaDB. They used to provide us binaries to bind with so our stuff always shipped with their latest build. We will purchase the product ourselves and make sure we always ship on the latest rather than relying on anyone else. That will surely help. We have many VistaDB users, let's see if they chime in.

---

EntitySpaces | Twitter | BLOG | Please honor our Software License

Mike,

Thanx for quick response my concern is that builds 38 and 40 are for those with support contracts and they may have done something differently to deliniate the builds

Hopefully it is something I did wrong but I did as noted in the posts and it says it has trouble loading .40 and then is looking for .33

If I revert to .33 all is ok so who knows

Cheers,

---

"The difference between genius and stupidity is that genius has its limits." - Albert Einstein

I'm having mixed results with build 40 as well.

MyGeneration works after compiling the VistaDB MyMeta plugin with build 40.

I have two active web projects right now.  They both use ES (2007.1.1001.0), VistaDB, and the same web.config file (w/bindingRedirect, copied from one project to the other).

When using VistaDB build 33 both projects work.  After installing VistaDB build 40, one project works while the other fails looking for build 33 (3.20.1.33).  For the time being I have gone back to build 33.  The info below was generated using .NET 2.0 SDK Fusion Log Viewer.

*** Assembly Binder Log Entry  (10/3/2007 @ 2:52:14 AM) ***

The operation failed.
Bind result: hr = 0x80131040. No description available.

Assembly manager loaded from:  C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll
Running under executable  C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\WebDev.WebServer.EXE
--- A detailed error log follows.

=== Pre-bind state information ===
LOG: User = someone
LOG: DisplayName = VistaDB.NET20, Version=3.20.1.33, Culture=neutral, PublicKeyToken=dfc935afe2125461
(Fully-specified)
LOG: Appbase = file:///D:/Programming/aspnet2/OnlineTaskList/src/
LOG: Initial PrivatePath = D:\Programming\aspnet2\OnlineTaskList\src\bin
LOG: Dynamic Base = C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\src\a254436d
LOG: Cache Base = C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\src\a254436d
LOG: AppName = 406f3c03
Calling assembly : EntitySpaces.VistaDBProvider, Version=2007.1.1001.0, Culture=neutral, PublicKeyToken=1c268199fb21bfe8.
===
LOG: This bind starts in default load context.
LOG: Using application configuration file: D:\Programming\aspnet2\OnlineTaskList\src\web.config
LOG: Using machine configuration file from C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\config\machine.config.
LOG: Post-policy reference: VistaDB.NET20, Version=3.20.1.33, Culture=neutral, PublicKeyToken=dfc935afe2125461
LOG: GAC Lookup was unsuccessful.
LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/Temporary ASP.NET Files/src/a254436d/406f3c03/VistaDB.NET20.DLL.
LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/Temporary ASP.NET Files/src/a254436d/406f3c03/VistaDB.NET20/VistaDB.NET20.DLL.
LOG: Attempting download of new URL file:///D:/Programming/aspnet2/OnlineTaskList/src/bin/VistaDB.NET20.DLL.
LOG: Assembly download was successful. Attempting setup of file: D:\Programming\aspnet2\OnlineTaskList\src\bin\VistaDB.NET20.dll
LOG: Entering download cache setup phase.
LOG: Assembly Name is: VistaDB.NET20, Version=3.2.1.40, Culture=neutral, PublicKeyToken=dfc935afe2125461
WRN: Comparing the assembly name resulted in the mismatch: Minor Version
ERR: The assembly reference did not match the assembly definition found.
ERR: Setup failed with hr = 0x80131040.
ERR: Failed to complete setup of assembly (hr = 0x80131040). Probing terminated.

Does this have to due with VistaDB changing the version numbers? Old version number 3.20.1.33 > new version number 3.2.1.40. Also, should EntitySpaces.Interfaces.dll be versioned 2007.0.913.0 instead of 2007.1.1001.0?

Has any progress been made in contacting the VistaDB team?  Has EntitySpaces bought a VistaDB license yet?

I want to use both products together (main reason for buying EntitySpaces when I did), but the BindingRedirect method isn't 100% working.  It's kind of hit and miss at this point. 

By the way, it looks like they will have a new beta build today or tomorrow (build 41) .

We are purchasing VistaDB this weekend. However, VistaDB releases new builds way to often. Whenever we release a build it will aways be on a the lastest VistaDB release from now on. If you grap a newer VistaDB and redirect you might have issues, however, it wouldn't be because of a bug in EntitySpaces.

I'm not sure what you mean, can't redirect, that is a .NET feature, it works, we know it does. We are currently compiled against VistaDB build 33, however, our next beta release will be on the latest official VistaDB.

At this point you're kind of stuck, but we'll be putting a new beta out possibly next weekend, or the next. Sorry about that

---

EntitySpaces | Twitter | BLOG | Please honor our Software License

I see they put out build 41 today, we'll take this into considering and consider make our next beta a little earlier (not this weekend though)

---

EntitySpaces | Twitter | BLOG | Please honor our Software License

What do I mean by can't redirect...I mean it is not working 100% for me on my computers.  It's hit and miss at this point, some projects work while others fail.

EntitySpaces is compiled against build 33 at the moment.  I have all 3.x builds (just downloaded build 41) and was testing against build 40 when I posted my results above about the .NET BindingRedirect method not working.  I've used the BindingRedirect method in the past (before ES was bound against build 33) and found it to work just fine :)

As of build 40, the BindingRedirect method isn't working for me.  I spent some time debugging which is how I generated that Fusion Error Log.  I was trying to see why the BindingRedirect method was failing on one project and not another.  Both were web apps, both had the same version of ES, both had the same BindingRedirect in the web.config file, both were ASP.NET (not ASP.NET AJAX).  Since I couldn't get both projects to use build 40 I dropped back down to build 33 for the time being.  I will probably re-test the web apps this weekend with build 41 to see if it helps.

Also, there is a post over at the VistaDB forums about the BindingRedirect method.  It's different than what is in their help file (and it was causing an issue) since the new minor version number is lower than the previous minor version number.  I tried the solution, it works on one project, but not the other.  http://www.vistadb.net/forums/viewtopic.php?t=2126

Thanks for the update and I can't wait for the next release :) 

 

 

Mike,

 Now it is build 42 according to last email solicitation to subscribe to source.

Can you post an update on when you will have a solution to this. We are about to release our product and we would like the most current version available.

 Cheers,

---

"The difference between genius and stupidity is that genius has its limits." - Albert Einstein

The plan is to post a new beta this week and it will be on the current release of VistaDB, you can do you testing and go live on the beta if you need to, it will have passed all of our regression tests to be released as beta.I might provide you with a special link earlier to allow you to begin your regression testing.

---

EntitySpaces | Twitter | BLOG | Please honor our Software License

I will ask again where are we with this?

At the rate vistadb releases versions we will be another version or two behind by monday!!

 cheers

---

"The difference between genius and stupidity is that genius has its limits." - Albert Einstein

Our current beta is out and using Build 42. I'm lost at this point, we know you can redirect but I think you encountered an error in that the new VistaDB wasn't compatible with the old one we were bound too? Can you please restate what exactly the issue is again.  The 1015 Beta is bound to Build 42. The ultimate solution would be probably to purchase the source, then you could recompile of course if need be.

---

EntitySpaces | Twitter | BLOG | Please honor our Software License

Could you post the redirection code you are using in your config? VistaDB is no longer installed into the VistaDB 3.0 folder, but VistaDB 3.2. Our latest (ES 2007.1.1015.0)  is compiled against VistaDB 3.2 (3.2.1.42). This represents a significant change in the way VistaDB is assigning version numbers. Our previous releases were compile against VistaDB 3.0 (3.20.1.33). Notice that the Minor version number is now .2, not .20. Maybe this is causing problems with how the versions are being redirected.

---

David Neal Parsons
www.entityspaces.net

I am out of office will post code by monday I suppose it is possible that the version numbers are reponsible

We intend to purchase source in the next month or so if we decide to keep VistaDb in product right now they have become an annoyance with this "problem"

---

"The difference between genius and stupidity is that genius has its limits." - Albert Einstein