On Mon, 01 Mar 2010 21:36:06 -0500
Miguel de Icaza mig...@novell.com wrote:
Hello,
[snip]
There are many different versions of the SQLite provider. However, Mono
has a couple of
different versions: Mono.Data.SqliteClient which is 1.1 only. It will not
work with NET_2_0
profile
Hello,
With the upcoming release of Mono 2.8 we are dropping the 1.0 profile
as developers moved a long time ago to the generics-based 2.0 profile
and because it is maintenance burden for us.
In addition to this, I would like to stop distributing some libraries
that were either never
Hello Kornél,
Don't make compiler generated classes sealed by default.
What is benefit of not doing that?
This is also related to the same class because that was explicitly
removing the sealed modifier to enable the static modifier.
Although currently only a single compiler generated
Hi Marek,
Although currently only a single compiler generated class benefits
from both of these modifications I don't see any drawbacks and in my
opinion the changes result in a more properly designed compiler
generated class infrastructure.
I am not sure what does more properly designed
I could be wrong, but I think this is a compilation flag, ie: when you build
Mono from sources.
Unless building Mono from sources doesn't bother you, if I were you, I'd be
lazy and patiently wait for Mono 2.8.
ShankarH wrote:
HI,
I am new to Mono studio.
I have mono 2.6 installed and
A brief look into gnome git for f-spot and banshee, I found that:
- f-spot may still use the old Mono.Data.SqliteClient
- banshee has its own copy of Mono.Data.Sqlite
Not sure what other apps that may depend on Mono.Data.SqliteClient.
--- On Tue, 3/2/10, Marek Habersack gren...@twistedcode.net
Hi All,
We are looking at using one of the assemblies from the Mono release
under the terms of the LGPL license in a commercial closed source
application. My understanding is that this is allowed as long as we do
not modify the compiled assembly in any way. The issue that we face is
that this
Is there an equivalent to LockFileEx on Linux? What would it be?
How would you lock a file that will work on .net on windows and mono on linux
and mono on windows and mono on mac os x, etc?
I would like this info so all DllImport attributes can be removed from
csharp-sqlite to make it fully
Hello,
* Drop Microsoft.JScript and `mjs'
We should drop Microsoft.Vsa as well then.
Done as well.
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
On Tue, 2010-03-02 at 12:21 -0500, Jacques Beaurain wrote:
... The issue that we face is
that this assembly is not signed and we need to be able to place the
assembly in the GAC of Microsoft Windows systems. What is the
recommended way to handle this situation?
In particular we are
On Tue, 2010-03-02 at 12:29 -0800, Daniel Morgan wrote:
Is there an equivalent to LockFileEx on Linux? What would it be?
No. There's flock(2) and fcntl(2), but these are advisory in nature
only. (Meaning that any other process with access rights to the file
can come along, ignore the advisory
On Tue, Mar 2, 2010 at 4:28 PM, Jonathan Pryor jonpr...@vt.edu wrote:
On Tue, 2010-03-02 at 12:29 -0800, Daniel Morgan wrote:
Is there an equivalent to LockFileEx on Linux? What would it be?
No. There's flock(2) and fcntl(2), but these are advisory in nature
only. (Meaning that any other
On Tue, 2010-03-02 at 21:03 -0500, Avery Pennarun wrote:
Probably the question needs to be rephrased a little. sqlite itself
obviously works fine on Linux, so clearly Linux has the kind of
locking that is needed in order to make sqlite work...
Yes, work. There's a difference between working
On Tue, Mar 2, 2010 at 9:54 PM, Jonathan Pryor jonpr...@vt.edu wrote:
In short, SQLite (1) uses advisory file locking (as FileStream.Lock()
provides under Mono), then (2) requires that all SQLite users actually
use libsqlite.so (otherwise they won't use the internal management).
Well, I'm
14 matches
Mail list logo
