Devart Forums

Compatibility
Supports SQLite servers from 3.23 and higher on .NET Framework 2.0 and higher and Mono.

Do you have step by step instructions on getting this to work? All of my efforts have led me to the message: "No access to the given Key"

Visual Studio 2010
Ubuntu 11.10
Mono 2.8.10
SQLite 3.x

Patrick

Windows XP
Mono 2.8.10

License not found. Please view "Licensing" topic in LinqConnect documentation for details or contact Devart technical support.

In my project, I have exe.licenses created and listed, and set to Embedded Resource. dotPeek show it embedded as DevArtTest.exe.liscenses

This is the command I used to build the resource:

"C:\Program Files (x86)\Mono-2.10.8\lib\mono\4.0\lc.exe" -v -t "exe" -c "licenses.licx" -i "Devart.Data.Linq.dll" -i "Devart.Data.SQLite.Linq.dll" -i "Devart.Data.SQLite.dll" -i "Devart.Data.dll"

Sorry for the delay. The license resource should be compiled via the Windows license generator. The proper way of doing this is described, e.g., in
http://www.devart.com/dotconnect/sqlite ... ml#compile

If you are using the LinqConnect trial, it is necessary to add the following entry to the licenses.licx file before compiling the license: Please tell us if this helps.

StanislavK wrote:

Code: Select all

Devart.Data.SQLite.Linq.Provider.SQLiteDataProvider, Devart.Data.SQLite.Linq

Devart.Data.SQLite.Linq.Provider.SQLiteDataProvider, Devart.Data.SQLite.Linq

This is what is in the file, which matches what you've indicated. It does not work.

Do you have step by step instructions on how to get this running, or a sample project/application showing it working in Mono? While the help file is good with general statements, it is not a good 'follow these steps and it will work' instruction set.

I am troubleshooting a lot of what I do not know in efforts to get this product working. The scenario we are looking for is build in Windows and deploy to Mono. While my test application is an exe, we will be doing the data access piece in a library so the licensing will need to accommodate that.

We will send you a sample project, please check that it is not blocked by your mail filter.

Generally, the following steps should be performed to run an application that uses LinqConnect under Mono:
1) Create a licenses.licx file and add the following entry to it: (this is actually done automatically if you are using Visual Studio to develop your application);
2) If you are going to use LinqConnect in an assembly that in turn is used by other applications, create the licenses.config file and specify the latter applications there. Place licenses.config next to licenses.licx.
3) Generate the license resource:
- find the license compiler (lc.exe) at the machine (with Windows) where LinqConnect is installed;
- run the compiler with the following command line: (the target should be just the application name, without the path to it);
- get the generated file ('MyApplication.exe.licenses') and add it to your project as an embedded resource.

As the license resource is available in the project, it should be possible to compile and run the application under machines where LinqConnect is not installed and, in particular, under Mono.

If the problem persists, you can send us your test project, so that we are able to analyze the licensing issue in details.

JIC: the assemblies from the Professional edition of LinqConnect need no technical licensing.

Thank you very much for your support. I think the key issue (mine) was that I took the statement that you need to add the license manually under Mono as if you are running it under Mono. In reality that is only if you are building under Mono, which I am not. I am new to developing for Mono, but very experienced in .NET.

We will be getting a Professional Site License. We need to double check some key points but things are looking well.