What's the estimation of effort required to get mono buildable in windows and debuggable in VS? 6 man months? 18 man months?
I don't have time to donate but I'd be happy to put some money in a pot with some of you to hire someone to work on this full time. Feels like a concerted full time effort would bear more fruit than occasional toe-dips in the water. Bryan Crotaz Silver Curve > On 16 Oct 2014, at 14:54, DavidKarlas <david.kar...@gmail.com> wrote: > > About debugging Mono on remote device(Linux) from VisualStudio... > http://www.giesswein-apps.at/mono aka. > https://github.com/giessweinapps/MonoDebugger > > About compiling itself... Don't want to sound like jerk but... It's open > source make it compilable with Visual Studio tool chain and open PR... > > About code analysis... Did you enable Source analysis in MonoDevelop/XS? > It's not resharper but it's open source if you miss some code action feel > free to PR... > > I think it doesn't make much sense to remote debug Linux Desktop/Mac Desktop > from Windows thats probably why Novell remote debugger died... > > > > -- > View this message in context: > http://mono.1490590.n4.nabble.com/Building-mono-on-Windows-issues-tp4664183p4664212.html > Sent from the Mono - Dev mailing list archive at Nabble.com. > _______________________________________________ > Mono-devel-list mailing list > Mono-devel-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-devel-list _______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list