Hello,

We have problem using MyGeneration 1.3 against latest VistaDB versions (3.3 and 3.4).

We use MyGen plugin obtained by following these instructions at http://community.entityspaces.net/forums/thread/4129.aspx

After resolving several problems of getting right DLLs, correct configuring and getting connected to the database, we are stuck on the step of generating classes.

I don't know how can I attach a screenshot here but some key (as I think) details are following:

Template Error

File: C:\Program Files\MyGeneration13\Templates\EntitySpaces2008\C#\EntitySpaces_C#_Generated_Master.csgen

Exception Type: NullReferenceException

Source Line: EngineExecuteCode

Detail: at Seus.DonNetScript.DotNetScriptExecutioner.EngineExecuteCode(...) at Zeus.SeusExecutioner.ExecuteCode

Same problem if we use MyGeneration 1.2.0.7

It works fine if we use EntitySpaces 2007 but we need EntitySpaces 2008 as tehre are some key features we cannot leave without.

Thanks in advance for a quick answer :-)

Hi

EntitySpaces 2008 uses a different Metadata engine thatn 2007.  If you look in your install directory under the "Code Generation" folder you should see a folder called "EntitySpaces.MetadataEngine.VistaDB" which contains the project/source code for the plugin that you need to compile against your version of VistaDB.  The dll(s) generated by that compile need to be copied to the "Code Generation\Bin\" folder - they might even need copying to the MyGeneration folder, not 100% sure.

Hope that helps

Martin

We are going to ship a MyMeta provider for this too. Right now, for VistaDB and SqlCE if you want to swap version (On MyGeneration only not CodeSmith) you have to recompile the MyGeneration MyMeta plugins and our PlugIn which is installed for you in the release candidate. We do plan to ship the MyMeta plugins for both VistaDB and SqlCE as well on the final release. We know this isn't optimal, but ES2009 will be it's own code generator and all this will be a thing of the past.

---

EntitySpaces | Twitter | BLOG | Please honor our Software License

Hello,

We've got the release, removed old versions of everything, installed the release. Recompiled all required stuff using your instructions. Result is the same - the exception I described in initial post.

Any more help? Does anybody has successfull experience in getting Vistadb 3.3 or 3.4 to work with es 2008 and mygeneration (either 1.2 or 1.3 - problem is same to both)?

I'm assuming that maybe we are still doing something wrong but can't see now what exactly. If anybody had success with same environment, your experience could help much...

I can get you working. I will post back your solution here later tonight. How about we do it for MyGeneration 1.2 as we like that version better. I will post you a very easy solution. Oh, also can you use ES2008 as that would make things better.

---

EntitySpaces | Twitter | BLOG | Please honor our Software License

Mike, thank you very much, I'm looking forward for a solution.

MyGeneration 1.2 is fine, and yes, we are using es2008 (just removed 3rd beta and installed the release today).

Time is critical so your help will be very highly appreciated :-)

Okay, this should work for you but it's kind of weird as MyGeneration 1.2 has a plugin for VistaDB and so does EntitySpaces. This issue will go away in ES2009 however. Here's the solution (Make sure you have MyGeneration closed during this)

Step One

You will find the MyGeneration MyMeta plugin for VistaDB HERE, unzip it and build it against your MyGeneneration 1.2 installs MyMeta.dll and your version of VistaDB. Next copy the newly compiled "MyMeta.Plugins.VistaDB3x.dll" into your MyGeneration folder.

Step Two

We ship the source for our "plugin" with ES2008, in the standard install you will find it here:

C:\Program Files\EntitySpaces 2008\CodeGeneration\EntitySpaces.MetadataEngine.VistaDB

Simply open the solution compile it against your version of VistaDB and copy it into your "C:\Program Files\EntitySpaces 2008\CodeGeneration\Bin" folder and your MyGeneration folder just to be safe. Please let me know if this works, it should.

[Modified]

Oh, and you can redirect our EntitySpaces Data Provider using this FAQ to any version of VistaDB

---

EntitySpaces | Twitter | BLOG | Please honor our Software License

I'm missing setting.settings file and .snk file for the new VistaDB provider after fresh install of 0623 ... are they necessary?

<edit>I removed them ... seems to work, with codesmith</edit>

Thanks for the info - we will try this your tonight, Evgeny's tomorrow - he's quite a few timezones away. 

Mike, thanks to your solution we were able to get it working, at last. Thank you very much and please take our compliments to your responsiveness - you never leave your customers head-to-head with their problems :-)