[Mono-dev] Building mono on Windows issues.
bryan.crotaz at silvercurve.co.uk
Thu Oct 16 13:35:21 UTC 2014
You can probably do 5-10% max of resharper this way. Here's some examples
of how it speeds up my day:
On 16 October 2014 14:22, Greg Young <gregoryyoung1 at gmail.com> wrote:
> This may help you a bit
> you can do much of VS + R# in sublime/vim if you spend the time to set
> it up.
> On Thu, Oct 16, 2014 at 1:45 PM, Alex J Lennon
> <ajlennon at dynamicdevices.co.uk> wrote:
> > On 16/10/2014 12:38, Edward Ned Harvey (mono) 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
> >>>> trying to accomplish something else, like obtain a specific DLL (such
> >>>> Mono.Data.Sqlite)... Which usually you can obtain some other way
> such as
> >>>> 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
> > I guess different people will have different use-cases but this is ours
> > (which I don't think is so unique)
> > We develop software targetting Embedded Linux, Windows desktop/server
> > and Windows CE/Embedded Compact with .NET CF.
> > We use Visual Studio (plus Resharper as Bryan so rightly says - couldn't
> > get along without it) as we find this to be a productive development
> > environment.
> > In addition there is a lot of development resource out there with people
> > who know and are qualified on the VS toolchain.
> > Ideally we'd be write once and it'd just work whatever the platform or
> > framework, but the reality is we run into platform dependencies (SQLite
> > as you say, serial comms in the past), native dependencies and
> > configuration issues.
> > From a productivity perspective and for risk management for testing and
> > deployment I wish to be able to develop and debug under Visual Studio
> > with Mono as a framework option.
> > I'd like to be able to do that with Mono on Windows as a check that no
> > issues come up between running on the .NET framework and running on Mono.
> > In addition I'd like to be able to remote debug to Embedded Linux with
> > Visual Studio - which I used to be able to do with Xamarin's Monotools
> > Server before it disappeared.
> > I'm currently investigating a VS plugin to replace Monotools Server
> > which I've not had much luck with yet, but I'm optimistic:
> > https://github.com/DynamicDevices/monodebugvs
> > Cheers,
> > Alex
> > _______________________________________________
> > Mono-devel-list mailing list
> > Mono-devel-list at lists.ximian.com
> > http://lists.ximian.com/mailman/listinfo/mono-devel-list
> Studying for the Turing test
> 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