On 16/10/2014 00:17, Chris Eelmaa wrote:
Hello all,
I have question regarding building mono on windows,
namely I've tried a lot of times, and had a lot of different
problems(such as missing some dependencies, git converting *.sh files
to CRLF ending and cygwin not being able to interpret
On 16/10/2014 08:45, Alex J Lennon wrote:
On 16/10/2014 00:17, Chris Eelmaa wrote:
Hello all,
I have question regarding building mono on windows,
namely I've tried a lot of times, and had a lot of different
problems(such as missing some dependencies, git converting *.sh files
to CRLF
From: Alex J Lennon [mailto:ajlen...@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 as
Q: Why do I want to debug on Windows?
A: Resharper
On 16 October 2014 11:38, Edward Ned Harvey (mono)
edward.harvey.m...@clevertrove.com wrote:
From: Alex J Lennon [mailto:ajlen...@dynamicdevices.co.uk]
Generally
speaking, the only reasons to build on windows are because you want to
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.cro...@silvercurve.co.uk
wrote:
Q: Why do I want to debug on Windows?
A: Resharper
On 16 October 2014 11:38, Edward Ned Harvey (mono)
On 16/10/2014 12:38, Edward Ned Harvey (mono) wrote:
From: Alex J Lennon [mailto:ajlen...@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
This may help you a bit
https://www.google.co.uk/search?client=safarirls=enq=greg+young+sublime+is+sublimeie=UTF-8oe=UTF-8gfe_rd=crei=FsY_VN3ALO3H8gfZwoKwBg
you can do much of VS + R# in sublime/vim if you spend the time to set
it up.
Cheers,
Greg
On Thu, Oct 16, 2014 at 1:45 PM, Alex J Lennon
continued... (grrr PEBKAC)
https://www.jetbrains.com/resharper/features/code_analysis.html
On 16 October 2014 14:35, Bryan Crotaz bryan.cro...@silvercurve.co.uk
wrote:
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
Basically if we could persuade Xamarin to get mono building on Windows and
VS users able to debug Mono, suddenly there would be a lot more developers
able to contribute without having to learn a whole new stack first.
Bryan
On 16 October 2014 14:36, Bryan Crotaz bryan.cro...@silvercurve.co.uk
From: Alex J Lennon [mailto:ajlen...@dynamicdevices.co.uk]
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.
+1
In addition there is a lot of development resource out there with
On 16/10/2014 15:37, Bryan Crotaz wrote:
Basically if we could persuade Xamarin to get mono building on Windows
and VS users able to debug Mono, suddenly there would be a lot more
developers able to contribute without having to learn a whole new
stack first.
Bryan
+1 and I'm happy to put
Oddly I have actually used this thing known as resharper before and
have some idea how it works. You can do a hell of a lot more than
5-10% of what you use. Have you even bothered to go through the post
list that explained how to setup much of what R# can do before
deciding its impossible?
On
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 gregoryyou...@gmail.com wrote:
This may help you a bit
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
From: mono-devel-list-boun...@lists.ximian.com [mailto:mono-devel-list-
boun...@lists.ximian.com] On Behalf Of Bryan Crotaz
Basically if we could persuade Xamarin to get mono building on Windows and
VS users able to debug Mono, suddenly there would be a lot more
developers able to
Contributions are one thing, but there should be a windows build system
implemented and running - even continuous integration running for each
commit. I'm pretty sure there's a Jenkins set up for the linux/mac builds
but non for Windows? Why?
On 16 October 2014 15:45, Edward Ned Harvey (mono)
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...
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
What's the estimation of effort required to get mono buildable in
windows and debuggable in VS? 6 man months? 18 man months?
I do builds from master for Windows regularly (but on Linux using
mingw-w64), so getting it to work shouldn't be anywhere near that
difficult. I've seen someone on irc
On 16/10/2014 16:58, Bryan Crotaz wrote:
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
I have a Windows CI cloud service running (Elastic Bamboo). If it helps get
Windows development going so that I can get in and fix mono bugs when I
find them, I'd be happy to sponsor running a nightly build and test of mono
on a clean Windows box. Let's say for 12 months to start with and see
I'm with you. I have been quite disheartened by the state of CI (or lack
thereof) for Mono, and especially the seemingly constantly broken state of the
Windows build. I haven't wanted to put much effort into fixing the build
because there hasn't seemed to be much of a commitment to keeping it
On 16/10/2014 20:33, Bryan Crotaz wrote:
I have a Windows CI cloud service running (Elastic Bamboo). If it
helps get Windows development going so that I can get in and fix mono
bugs when I find them, I'd be happy to sponsor running a nightly build
and test of mono on a clean Windows box.
In general, a partial implementation is better than no implementation at
all.
When it comes to crypto, things are a little bit different, and we need to
be more careful.
What are the things that would not work from the spec?
Miguel
On Thu, Oct 16, 2014 at 3:20 PM, Martin Thwaites
This topic has been brought up in a ton of other threads I just want
to centralize the topic.
I have felt the pain many others have discussed (6-12 months for an
accept of PR, we actually had a separate distribution of mono for a
while).
Is there background on the issue?
What are the issues that
Thanks for the quick reply Miguel.
The crypto will be at least as secure as the existing MachineKey.Encrypt
methods. It's this page that I've not looked:
http://msdn.microsoft.com/en-us/library/system.web.configuration.machinekeycompatibilitymode%28v=vs.110%29.aspx
There appears to be some new
Hello Greg,
The best approach is to stay engaged in the pull requests and bring the
attention to the mailing list for us to discuss.
Long term, the ideal situation is one where we can give more people commit
rights, and review rights. But until we have developed the skills in the
community
Miguel,
In the meantime, if you need quick hacks, you can always fork Mono
and distribute your forked version with your changes.
To be fair you know the pain we deal with due to this.
For us if we had a backlog of 200 PRs this would be a wonderful
problem to have. I would immediately hire 1-2
Just to give my2cents on this.
I would just like to know that things will get looked at approved at some
point. I saw a while back that there was a flurry of activity on PR's, and
some people (possibly after direction from Miguel) whacked that list down
considerably.
Is there anything that
Long term, the ideal situation is one where we can give more people commit
rights, and review rights. But until we have developed the skills in the
community that are needed, we will continue with the current setup.
This seems to be a chicken-and-egg problem. We need to christen more
reviewers
Hello,
I would say, let us wrap up what you have, and then we can review the
implications that lacking some options might have.
On Thu, Oct 16, 2014 at 3:30 PM, Martin Thwaites monofo...@my2cents.co.uk
wrote:
Thanks for the quick reply Miguel.
The crypto will be at least as secure as the
There is no point in starting a discussion where you are going to cherry
pick facts for the sake of your argument.
As for contributing, which one of *your* pull requests have been pending
and not being reviewed?
Because we would like to provide you with the valuable feedback that you
need to
Hi Miguel,
I've given it a bit more of a look.
The things that wouldn't work is being able to provide custom decryption
algorithms via the web.config. Nothing else seems to be affected.
I'll package it up and send it over, thanks for the help.
Thanks,
Martin
On 16 October 2014 21:26, Miguel
Let me add a couple of points.
First, I have noticed is that:
- Contributors do not make a habit out of checking pull requests; I
know I don't
- GitHub is too chatty, so everyone I know just filters notifications.
I suspect this is why anyone being assigned issues just ignores
Hi Miguel,
I have considered helping out by commenting on PR's, however, I've always
felt that I'm not nearly experienced enough to have my opinion/view
respected by the committer.
I definitely think forcing/gently encouraging people to create a discussion
on mailing list to ask for review would
Hi all,
I've just put up my attempt at getting the MachineKey.Protect and Unprotect
methods available in mono. I'd be grateful if someone give it a quick
review to make sure it makes sense.
https://github.com/mono/mono/pull/1349
Couple of notes. There is no compatibility with encrypted items
Hello,
I was maintaining the Visual Studio solution for the runtime and doing
Windows development for a while but haven't kept up for a number of years
now. We've had a number of build mono on Windows discussions over the
years and various attempts at improving it. Breaking the discussion into
I've always used Npoi, however I'm not sure if it's mono compatible.
On 16 Oct 2014 03:57, Edward Ned Harvey (mono)
edward.harvey.m...@clevertrove.com wrote:
From: mono-list-boun...@lists.ximian.com [mailto:mono-list-
boun...@lists.ximian.com] On Behalf Of Maury Markowitz
I'm testing the
On Oct 15, 2014, at 10:56 PM, Edward Ned Harvey (mono) [via Mono]
ml-node+s1490590n4664186...@n4.nabble.com wrote:
So there's your answer. That particular assembly is unfortunately out of
maintenance for now. Have you considered http://GemboxSoftware.com? I'm
sure there are other packages
From: mono-list-boun...@lists.ximian.com [mailto:mono-list-
boun...@lists.ximian.com] On Behalf Of Maury Markowitz
Wow, fantastic answer!
Glad to help - but I want to emphasize the second part of that answer, which
was, the Class Status page actually indicates the vast majority of Packaging
Hi Maury,
If you're looking for an unzipping library, this one looks pretty easy to use
(and is available via NuGet):
https://github.com/yallie/unzip
There's also a list of alternatives on that page.
Best wishes,
Jeff Bonhag
-Original Message-
From:
On 16.10.2014 15:09, Maury Markowitz wrote:
So does anyone know of a PCL/Mono compatible ZIP library along those lines?
DotNetZip:
http://dotnetzip.codeplex.com/
Robert
___
Mono-list maillist - Mono-list@lists.ximian.com
On Oct 16, 2014, at 9:26 AM, Robert Jordan [via Mono]
ml-node+s1490590n466420...@n4.nabble.com wrote:
DotNetZip:
http://dotnetzip.codeplex.com/
So the problem with the example (code) is that it does file-to-file actions.
System.IO.Package does file-to-stream (basically) - we build new
I'm playing a bit with the VS build files and found two oddities I'd like to
understand before I edit...
1) Almost all of the projects refer to /System/Consts.cs. I do not have such a
file, but I do have Consts.cs.in, which looks a lot like a cs file. I am
unfamiliar with .in - is this
On 15/10/14 22:36, Maury Markowitz wrote:
I'm testing the waters for a Mono/Xamarin port of an existing VB.net code
base. The important part of this code uses System.IO.Package(...)
Is it suitable for production?
Best way to find out is testing it for your use case.
If so, how would I go
45 matches
Mail list logo
