The MonoGame project is set to be an application instead of a library?
 Interesting.  I'll check that out when I get home.  Thanks for the tip.

Sly

On 18 May 2012 09:49, Jonathan Pobst <mon...@jpobst.com> wrote:

> You might want to look at what I wrote here:
>
> https://bugzilla.xamarin.com/**show_bug.cgi?id=5146<https://bugzilla.xamarin.com/show_bug.cgi?id=5146>
>
> If it's the same issue, I don't think it has anything to do with implicit
> references.
>
> Jonathan
>
>
>
> On 5/17/2012 5:36 PM, Konaju Games (Dev) wrote:
>
>> Seeing the other threads about this linking issue, and your decision to
>> exercise your disclaimer clause to now be in favour of implicit linking,
>> could we expect an update for MfA to go back to implicit linking?  This
>> linker issue is a blocker for my work on MonoGame as even adding the
>> reference to Lidgren to my startup project doesn't fix the linker error.
>>
>> Sly
>>
>> On 18 May 2012 01:24, Jonathan Pryor <j...@xamarin.com
>> <mailto:j...@xamarin.com>> wrote:
>>
>>    On May 17, 2012, at 9:20 AM, Konaju Games (Dev) wrote:
>>     > >> We don't implicitly include additional assemblies.
>>     > We have never had to explicitly reference the
>>    Lidgren.Network.Android project from our startup project before.  Is
>>    that a new requirement in MfA 4.2?
>>
>>    I had thought that we always had this requirement, and Visual Studio
>>    has frequently enforced this requirement. I don't know why things
>>    have changed in 4.2. :-/
>>
>>    Doubly odd is that .apk inclusion apparently will include implicitly
>>    referenced assemblies (based on other mailing list threads), while
>>    fast deployment won't.
>>
>>    Be that as it may, I'm currently of the opinion [0] that assemblies
>>    should be explicitly referenced, as it's less "magical" and ensures
>>    that the App developer knows which assemblies will be included (and
>>    thus have some sort of guide for how big the resulting app will be).
>>    Implicitly pulling things in could make things harder, as you start
>>    wondering why assembly X is being stored in your app...
>>
>>      - Jon
>>
>>    [0] Subject to change without notice, additional experience, and/or
>>    (in)sanity.
>>
>>    ______________________________**_________________
>>    Monodroid mailing list
>>    Monodroid@lists.ximian.com 
>> <mailto:Monodroid@lists.**ximian.com<Monodroid@lists.ximian.com>
>> >
>>
>>
>>    UNSUBSCRIBE INFORMATION:
>>    
>> http://lists.ximian.com/**mailman/listinfo/monodroid<http://lists.ximian.com/mailman/listinfo/monodroid>
>>
>>
>>
>>
>> ______________________________**_________________
>> Monodroid mailing list
>> Monodroid@lists.ximian.com
>>
>> UNSUBSCRIBE INFORMATION:
>> http://lists.ximian.com/**mailman/listinfo/monodroid<http://lists.ximian.com/mailman/listinfo/monodroid>
>>
>
>
>
_______________________________________________
Monodroid mailing list
Monodroid@lists.ximian.com

UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid

Reply via email to