Hey guys,
Sami reached out to me, and was wondering how to get started in bringing
some code to Mono, in particular WCF to Mono. So I wrote this small guide
for newcomers.
I would say it takes a couple of steps:
- Build your own local version of Mono on Linux.
- Make sure it works "mcs"
Hi Miguel,
Is there an ETA on merging your "large fork". I don't want to get started
on anything that you guys have already done?
Or could you tell us which areas to stay away from for now? Personally, I
would want to look at some of the system.web things.
Thanks
Martin
On 15 Nov 2014 03:07, "
Hello,
We worked only on System.Configuration, regex, the crypto and web stack.
The rest you can do, including the web stack.
I took a look at asp.net. I think in the long term we want to replace
most of it, but it needs to be done in stages, as it still contains a bunch
of native stuff.m
M
So has it been merged yet?
I'm going to look at the Buffer stuff I shy'd away from before. Then look
at the MachineKey.Protect stuff to implement the things I missed.
I've got a separate question around the mismatch in conventions, but I'll
ask that on a different thread.
I'm struggling to cont
It hasn't. When we do, we will announce.
Two issues: we worked with reference source and the github push is only
slowly getting the bits. And the second is that the layout they are
pushing is different.
On Saturday, November 15, 2014, Martin Thwaites
wrote:
> So has it been merged yet?
>
>
What's the plan on where there are differences in behavior? An example of
this would be uri matching. I would guess it makes sense to use the ms
stuff moving forward, how will changes in current behavior be communicated
On Saturday, November 15, 2014, Miguel de Icaza wrote:
> Hey guys,
>
> Sami
Each one needs to be discussed
Some of the Ms behaviors don't work on Unix, so not only we shouldn't bring
it, we should work towards a better shared set of new Apis
Not sure what you meant in this specific case.
On Saturday, November 15, 2014, Greg Young wrote:
> What's the plan on where ther
Given these obstacles, I think that going forward with the originally
announced plan of removing non-4.5 profile support from the current Mono
code base - without introducing MS code yet - would make the gradual
adoption of MS code much easer.
On 11/15/2014 2:11 PM, Miguel de Icaza wrote:
It
Hey,
It is a tangential problem.
The big problem with removing the profile right now, is that removing it
causes F# to fail building.
We are trying to fix that.
Miguel
On Sat, Nov 15, 2014 at 10:05 AM, Kornel Pal wrote:
> Given these obstacles, I think that going forward with the originally
Let me give more color on the situation.
Tasks:
- *Not building the 2.0 Profile*: while this is a very simple change, it
currently breaks the F# compilation. I have to dig out the reasons, I can
not remember why, but it does. Something related to MSBuild targets or
something.
-
Thanks Miguel,
That clears up a lot. I'll wait until Monday before I ask more questions
:-D enjoy the weekend.
Martin
On 15 November 2014 15:58, Miguel de Icaza wrote:
> Let me give more color on the situation.
>
> Tasks:
>
>- *Not building the 2.0 Profile*: while this is a very simple c
On 15/11/14 15:48, Miguel de Icaza wrote:
Each one needs to be discussed
Some of the Ms behaviors don't work on Unix, so not only we shouldn't bring it,
we should work towards a better shared
set of new Apis
I would be all in favor of this approach. In fact, I'd advocate for having a rule that
12 matches
Mail list logo
