CharacterEditor
CharacterEditor copied to clipboard
Successful compile, bad SQL DLL
I am running Win7 x64. In order to open the character.db file successfully. I needed to download and replace the System.Data.SQLite.dll with the version from: http://system.data.sqlite.org/downloads/1.0.87.0/sqlite-netFx40-static-binary-bundle-Win32-2010-1.0.87.0.zip
My build target is the default 32-bit Debug. However since the build is for 32 bit it requires the 32bit .DLL AFAIK.
Running Win7 x64 as well. Currently I just copy it over and replace the reference every time I sync with the main branch. This is my first time dealing with x64 and x86, so not sure why it works.
I can't replicate the problem over here. I needed to build a new DLL because I needed to use a config file to run the DLL with .NET 2.0. I'm not exactly sure what the problem is, honestly.
Zach by chance do you have sqlite installed? I.e: http://system.data.sqlite.org/downloads/1.0.87.0/sqlite-netFx40-setup-bundle-x86-2010-1.0.87.0.exe http://system.data.sqlite.org/downloads/1.0.87.0/sqlite-netFx40-setup-bundle-x64-2010-1.0.87.0.exe I'm not sure if that matters or not. Either way not a big deal. Might just be nice to know when trying to sort out bug reports.
Stop running things in "Any CPU", mine works with "x86" but not with "Any CPU". Warning: "Warning 1 There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "System.Data.SQLite, Version=1.0.86.0, Culture=neutral, PublicKeyToken=db937bc2d44ff139, processorArchitecture=x86", "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project. "
My SQLite is built with "Any CPU", so I have no idea why it's targeting x86.
I did have SQLite installed, by the way. I "uninstalled" it (the uninstalled crashed while uninstalling, said it still uninstalled successfully and I don't see it in the GAC) it still runs just fine when build in x86.
OK so its not in the GAC that should make us all have a consistent base to work from..... still not sure why SQL for .NET is so picky.
Ok, so this is weird. I'm just going to revert back to the .NET 2.0 DLL for now since we know it works. I'd prefer not to have a nasty configuration file to make it work, but I don't see any other option right now.