NetGore

For #1, keep in mind that it has be populated with the correct schema, and the InstallationValidator checks for this. The schema in 0.3.3 and 0.3.4 are different. Importing the database dump should fix it. If not, let me know.

For #2, is it really "Ëxternals" you see? Or "Externals"? Note the E. If an umlaut ye' see, than a problem tharr be. I just grabbed the download and it worked fine for me. What is the locale of your system? Maybe that is the problem.

For #3... crap. I tested all builds right before packing. I think it was the last-minute code clean-up that broke it.

I'll have to repack the release because of #3, but I'd prefer to wait until the other two issues are resolved, too.

for #1, I just imported the db file that comes with 0.3.4 but it still shows the red unhappy face

for #2, you are right for noticing that. It should indeed be Externals (without the umlaut) it was just a typo i made when posting that. Weird that it works fine for you and not for me :edit: can it be because I use the free version of visual studio 2010?

Hmm... not sure why Visual Studio Express would be having a problem with it, but not sure - never tested it. Can anyone else confirm? If so, that is really going to suck...

Edit: Yep, looks like Visual Studio Express doesn't support solution folders. Weak.

Anyone else have problems with the InstallationValidator saying the database is not correct? I just dropped my local database, let the InstallationValidator import it for me, and it worked just fine.

So that takes care of all issues except for the InstallationValidator and the database schema, which I cannot replicate on my side.

maybe this will help with #1:

the selected test status of the validator comes up with this:

The test threw the following unhandled exception:
System.IO.FileNotFoundException: Could not load file or assembly 'MySql.Data, Version=6.3.5.0, Culture=neutral, PublicKeyToken=c5687fc88969c44d' or one of its dependencies.

File name: 'MySql.Data, Version=6.3.5.0, Culture=neutral, PublicKeyToken=c5687fc88969c44d'

at InstallationValidator.Tests.DatabasePopulated.TestInternal(String& errmsg)

at InstallationValidator.Tests.DatabasePopulated.RunTest(String& errorMessage)

at InstallationValidator.TestableBase.Test(String& errorMessage)

WRN: Assembly binding logging is turned OFF.

To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.

Found the problem. For some reason it is relying on the MySQL .NET connector to be in the GAC - that is, actually install the connector. Should be easy enough to fix.

Edit: Scratch that - something slightly different. Still, easy fix.

Alrighty, 0.3.4 has been re-released with those issues fixed. Thanks for bringing them up.

No problem and thank you for fixing them

Thanks! I had the same problems.

Hi spodi I just went out and checked version 0.3.5 and the problem with the installationvalidator happend again.

the installationvalidator showed an unhappy red face for the final step (database populated), whilst the database is in fact populated:

The test threw the following unhandled exception:
System.IO.FileNotFoundException: Could not load file or assembly 'MySql.Data, Version=6.3.5.0, Culture=neutral, PublicKeyToken=c5687fc88969c44d' or one of its dependencies.

Anyone else getting this problem?

Fixed and re-upped.

In case I screw this up again, and again forget what to do to resolve it: the problem is mysql.data.dll didn't get copied into InstallationValidator's \bin\.