Hi
@Xamarin team: I do not want to cross-post to MT list too much, but if
this is of interest
for MT developers, somebody from team pls cross-post it.
On 2012.08.17 11:53, Matthias wrote:
Hi,
I'm using some similar approach too but the problem is that you are losing
some part of the your toolchain namely the ability to refactor code is
reduced. The different files (linked or not) are usually not seen as real
dependency so rename or so fails (correct me when I'm wrong but this happend
to me alot). There are some issues with multiple opened files and debugger
weirdness too.
I would add intelisense weirdness (in VS at least) to this list. That is
the reason to
change projects Properties (default namespace).
It happened a lot that during coding Intelisense finds a class, but
build whines that it cannot
find class.
Solution: default namespace change helps.
I'll try to put more light on this issue in writeup (screenshots etc)
This drawback brings me to another solution that can be a partial solution.
Since some time Microsoft supports Portable Library Tools which include
subsets of some frameworks (Windows Phone, Silverlight, Metro, .NET). There
are some tweaks around to make it work with MonoForAndroid or even with
MonoTouch. The problem is that the library is build against this special
subset framework and lots of features are still missing. It's not compiled
against the mono libs, so there is no compile check but as long as you are
using base library functions and WP/Silverlight as target mono should have
it.
The real advantage is that you have ONE library as real dependency for your
projects and this allows you to use the regular toolchain. For example you
can rename a method of your shared lib in an android project and the same
change is seen in WP project with same shared lib.
The downside is the wrong compilation target. So far I never had problems
with it but maybe someone from Xamarin could give a statement about the
general compatibility between a PLT output and M4A.
I have problem that 24hrs is not enough, so did not have a chance to
take a deeper look into
portable libs...
cheers
mel
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/Stepping-into-standard-NET-libs-tp5711361p5711375.html
Sent from the Mono for Android mailing list archive at Nabble.com.
_______________________________________________
Monodroid mailing list
Monodroid@lists.ximian.com
UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid
--
Miljenko Cvjetko dipl.ing. ET
Direktor/CEO
Projektant rješenja/Solution Architect
Razvojni programer/Senior developer
Voditelj projekta/Project Manager
IX južna obala 13
Kajzerica Zagreb
T: 385 1 7775555
M: 385 91 557 447 3
F: 385 1 7779556
e: mcvje...@holisticware.net
w: http://www.holisticware.net
_______________________________________________
Monodroid mailing list
Monodroid@lists.ximian.com
UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid
