System.Data.SQLite

[I'm posting here rather than 'How to' which is where I saw other build questions, but I didnt see anything that meshed with the problems I am seeing].

 I had originally pulled the source from the packaged source (SQLite-1.0.63.0-source.zip), and couldnt get it to build out of the box.I tryed CVS and largely got the same results. This is where I stand:

Target platform: Win32 (32 bit)

Opening up the solution "SQLite.NET.sln" I get 2 unresolved projects:

• System.Data.SQLite - ManagedOnly
• System.Data.SQLite - Netmodule

It also appears the project is currently really targetting the Compact edition as it has "System.Data.SQLite - Compact" included as well as "testce" and not the "SQLite - Full" project.

To minimize complications with the compact components needing deployment I removed them from the solution and added in "System.Data.SQLite - Full.csproj"project.Changed the build to "Debug".

From here the debug build works, however when attempting to do a release build things get a little more intereresting :-). I understand there is merging of the Interop & the System.Data.SQLite and all sorts of low level fun going on here, but the initial release build fails on:

LINK : fatal error LNK1181: cannot open input file '..\System.Data.SQLite\bin\System.Data.SQLite.netmodule'

Question: Do I need  "System.Data.SQLite - ManagedOnly" or "System.Data.SQLite - Netmodule"? It would appear not for Debug, but in the current project setup they appear to be needed for Release.

Question: What are the differences between "Debug", "Debug - Stock", "StockDebug" - and I presume the same differences apply to the "Release" trio

Many thanks in advance,

Gareth

I'll have this fixed for the 64 release.  I forgot to update CVS with the newer project files since I rearranged a few things.

I've committed the csproj files so things should build now from CVS.

Firstly thanks for the exceptionally quick turn around!

I have the latest from CVS, and can get the release build to work now :-), however the debug is not so happy now:

1>------ Build started: Project: System.Data.SQLite - Netmodule, Configuration: Debug Any CPU ------
1>C:\WINDOWS\Microsoft.NET\Framework\v3.5\Csc.exe /noconfig /unsafe- /nowarn:1701,1702 /platform:x86 /errorreport:prompt /warn:4 /define:TRACE;DEBUG;USE_INTEROP_DLL /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Data.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Transactions.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Xml.dll /debug+ /debug:full /filealign:512 /optimize- /out:obj\Debug\System.Data.SQLite.netmodule /resource:obj\Debug\System.Data.SQLite.SR.resources /resource:SQLiteCommand.bmp,System.Data.SQLite.SQLiteCommand.bmp /resource:SQLiteConnection.bmp,System.Data.SQLite.SQLiteConnection.bmp /resource:SQLiteDataAdapter.bmp,System.Data.SQLite.SQLiteDataAdapter.bmp /target:module AssemblyInfo.cs LINQ\SQLiteConnection_Linq.cs LINQ\SQLiteFactory_Linq.cs SQLite3.cs SQLite3_UTF16.cs SQLiteBase.cs SQLiteCommand.cs SQLiteCommandBuilder.cs SQLiteConnection.cs SQLiteConnectionPool.cs SQLiteConnectionStringBuilder.cs SQLiteConvert.cs SQLiteDataAdapter.cs SQLiteDataReader.cs SQLiteEnlistment.cs SQLiteException.cs SQLiteFactory.cs SQLiteFunction.cs SQLiteFunctionAttribute.cs SQLiteKeyReader.cs SQLiteMetaDataCollectionNames.cs SQLiteParameter.cs SQLiteParameterCollection.cs SQLiteStatement.cs SQLiteTransaction.cs SR.Designer.cs UnsafeNativeMethods.cs

Compile complete -- 0 errors, 0 warnings
1>System.Data.SQLite - Netmodule -> C:\GitRepository\Home\sqlite.net\SQLite.NET\SQLite.NET\bin\System.Data.SQLite.netmodule
2>Error: The operation could not be completed. Unspecified error
3>------ Skipped Build: Project: System.Data.SQLite - ManagedOnly, Configuration: Debug Any CPU ------
3>Project not selected to build for this solution configuration
[rest snipped]

If you have any ideas that would be great, otherwise I'll have to dig into it a bit later.

Many thanks again,

Gareth

Please ignore the previous post - my machine was broken and not the build! A reboot fixed it a treat.

Sorry for any inconvience,

Gareth