Friend access was granted to System.Net

[schappel]

Friend access was granted to System.Net

[slodge]

There is no way to solve this properly yet....

It's a problem only when compiling in MonoDevelop (not VS)

The MonoTouch solution works around this by building to a System.Net.Touch.dll name and then doing a rename to System.Net.dll

I have opened this up on https://bugzilla.xamarin.com/show_bug.cgi?id=8035 last month (and on StackOverlfow in September - http://stackoverflow.com/questions/12433701/building-a-system-net-surrogate-dll-under-monotouch-avoiding-a-friend-access)

I've got agreement from engineers at both Xamarin and Microsoft than one or both of them should ship these shim dll's really... but no real action from either yet.

As a workaround, I will put the same workaround as Touch has for this - will do at some point this week....

For MonoDroid, a similar fix will be needed for the System.Xml.Serialization shim too.

Sorry about leaving this in there thsi long (Redth told me about it at the end of last week)

Stuart

[slodge]

ie if you need this to build for you now:

1. Change the System.Net.Droid output assembly name to System.Net.Droid.dll
2. Add a rename PostBuild task - see CustomCommands in the Touch version - https://github.com/slodge/MvvmCross/blob/vnext/PortableSupport/System.Net.Touch/System.Net.Touch.csproj
3. Maybe, you will also need to edit a few csproj files (mainly the samples) so that they reference the bin/Droid/debug/System.Net.dll by file rather than by project

The main delay for me doing this myself is setting up my Mac for Droid development!

Hope that helps

Stuart

[slodge]

If that doesn't make sense you can ping me on http://jabbr.net/#/rooms/mvvmcross - although I have a feeling we are in different timezones :)

[schappel]

Thanks, that seems to do the trick. I guess the fun part is trying to keep the projects consistent between Windows and OSx.

On a different note, I must say from what I have seen you have done a great job. I previously have used Caliburn.Micro in a number of WP7 / WPF applications, and it doesn't seem like too much of a leap to get my head around MvvmCross. BTW: If you ever decided to merge with Caliburn I think the ultimate Mvvm Framework could be created. (just saying)

[schappel]

To get around the Windows (Visual Studio) / OSx (MonoDevelop) I just hacked the project file (based on a previous post of yours) to conditionally change the assembly output name:

    <AssemblyName Condition="'$(OS)' != 'Windows_NT'">System.Net.Droid</AssemblyName>
    <AssemblyName Condition="'$(OS)' == 'Windows_NT'">System.Net</AssemblyName>

[slodge]

I do believe I fixed this and checked in the changes... but I haven't tested yet!

[slodge]

Finally tested on the Mac - it didn't build....

Problem still there with the xml serialization project

Fixed that now....

• so closing.

Thanks again for the bug report - bug squashed :)