[Mono-dev] Building mono on Windows issues.
mmihajlovic at gmail.com
Thu Oct 16 10:48:31 UTC 2014
Could a service like https://ci.appveyor.com/ not be used to set up a
proper windows build?
On 16 October 2014 12:44, Bryan Crotaz <bryan.crotaz at silvercurve.co.uk>
> Q: Why do I want to debug on Windows?
> A: Resharper
> On 16 October 2014 11:38, Edward Ned Harvey (mono) <
> edward.harvey.mono at clevertrove.com> wrote:
>> > From: Alex J Lennon [mailto:ajlennon at dynamicdevices.co.uk]
>> >> Generally
>> >> speaking, the only reasons to build on windows are because you want to
>> >> debug the code, which is generally better done on mac/linux. Or you're
>> >> trying to accomplish something else, like obtain a specific DLL (such
>> >> Mono.Data.Sqlite)... Which usually you can obtain some other way such
>> >> building on linux and then copying the DLL over to windows.
>> > Agreed, but the the other reason is that you want to use a current Mono
>> > yet nobody has gotten around to an official release of Mono for WIndows
>> > since 3.2.3.
>> Agreed, but that's the point - Why would you want to use Mono on
>> windows? The only reasons I know of are (a) you wish to debug the mono
>> sources using Visual Studio, or (b) you wish to use one of Mono's
>> assemblies in windows, such as Mono.Security, Mono.Data.Sqlite, etc.
>> For case (a), at least for me, it's been easier to transition to Xamarin
>> Studio or Monodevelop on mac/linux.
>> For case (b) I was able to brainlessly copy Mono.Security.dll, and I
>> struggled a little bit to copy Mono.Data.Sqlite.dll, but after a few tries,
>> managed to get it right more easily than getting it to build natively on
>> Mono-devel-list mailing list
>> Mono-devel-list at lists.ximian.com
> Bryan Crotaz
> Managing Director
> Silver Curve
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mono-devel-list