Hello *,
when reading Marius's thread "Example from Mono - FirebirdSql.Data.
Are you missing an assembly reference" I realized, that we have in
code NET directive that we're using to throw away some code that's not
good for Mono. But in fact we're using also MONO directive in build.
So when building on Mono you have to _remove_ NET and add MONO (it's
now not used). And this is IMHO exactly the opposite way. A lot of
people don't know about removing NET directive and in fact it's not
obvious. OTOH using MONO directive makes sense - you're building on
Mono so you have to define it - it has same name, and it's still .NET
code, only under Mono.
So I'm thinking about changing usage from #if (NET) to #if (!MONO) and
removing NET evermore.
So we will have conditional code for Compact Framework (NET_CF), for
.NET FW 3.5 (NET_35), for Entity Framework (ENTITY_FRAMEWORK) and for
Mono (MONO) and few others (not important for this discuss).
What do you think? I hope this can simplify these symbols.
PS: There's also NET_20 symbol which is survival from 1.x versions
builds on .NET 2.0, so we can remove it too (it's not use on any
place).
--
Jiri {x2} Cincura (CTO x2develop.com)
http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Firebird-net-provider mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
