Hi Miguel/Charlie,
If there is no fundamental reason not to use a more recent version, then
I'll add it to my list.
I seem to recall that Nunit 3.0 is removing support for older framework
versions, so if it removes 2.0 we won't be able to do it until the big
purge happens in mono.
Once I've got
Hi,
This is possible on Unix (and Windows) using the IPV6_V6ONLY socket
option. I'm not sure however about how widely this is adopted.
Kornel
On 10/26/2014 5:01 AM, Miguel de Icaza wrote:
I am not sure that Unix can support the idiom surfaced by the
two-parameter Socket.
If K wants to be
There are. Someone needs to survey in depth all the ramifications. Once
that happens, then we might consider it.
On Sunday, October 26, 2014, Martin Thwaites monofo...@my2cents.co.uk
wrote:
Hi Miguel/Charlie,
If there is no fundamental reason not to use a more recent version, then
I'll
Hi,
Inspired by the ASP.NET 4.5 Async Pipeline email thread started by
Martin Thwaites, I realized that there actually is no new async pipeline
in ASP.NET 4.5, it merely provides wrappers around tasks to ease
interfacing with the old async pipeline.
I've looked around a bit, but found no
I'm sure Charlie can tell us what considerations there need to be with
upgrading from 2.4.8 to 2.6.3 (We have the best resource to do that!).
My perception is that the jump to 3.0 might be too big.
On 26 October 2014 13:29, Miguel de Icaza mig...@xamarin.com wrote:
There are. Someone needs
Hello,
The asynchronous pipeline was discussed in various blogs/interviews. Some
switch enables apparently an entirely different flow inside asp.net. The
surface changes were minimal, which is why you won't likely find an API.
On Sunday, October 26, 2014, Kornel Pal kornel...@gmail.com wrote:
Hi Miguel,
Does that have implications in regards to this PR? i.e. is it just that it
doesn't solve the problem, or that the implementation here is wrong?
Thanks,
Martin
On 26 October 2014 13:46, Miguel de Icaza mig...@xamarin.com wrote:
Hello,
The asynchronous pipeline was discussed in
Hi,
Enable dolt on mingw32, something I miss since the change to targeting
mingw32.
Please review my pull request: https://github.com/mono/mono/pull/1367
Thank you.
Kornel
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
Hi all,
I've reached a point where we have an Appveyor configuration file which
successfully builds Mono under Cygwin on an Appveyor build worker
(Windows Server 2012 R2 OS image, I believe).
It's taken longer to get to this point than I had expected, doesn't it
always, but I hope this will be
Brilliant news Alex, I know how much work you put into getting this
working, and how frustrating it must have been to wait for hours to see
whether a build works or not. Well done.
On 26 October 2014 16:14, Alex J Lennon ajlen...@dynamicdevices.co.uk
wrote:
Hi all,
I've reached a point where
Hi,
I've found this, that fits Miguel's description:
http://stackoverflow.com/questions/9562836/whats-the-meaning-of-usetaskfriendlysynchronizationcontext
My PR is is independent of any such changes, and given the API design, I
would be surprised if MS implemented some special handling of
Thanks Kornel,
I've still a few bits of complicated to complete, but I'll feedback as soon
as they are done.
Martin
On 26 October 2014 14:46, Kornel Pal kornel...@gmail.com wrote:
Hi,
I've found this, that fits Miguel's description:
Hi All,
This is a simple PR for the property added in .NET 4.5.
I couldn't find any existing tests for the module, and I struggled to find
a way to test it.
All I've done to test it is added to an existing application I have and it
functioned the same on windows and linux.
Let me know if there
On 26/10/2014 16:05, Alexander Köplinger wrote:
Very good news!
The windows installer is built by
https://github.com/mono/release/tree/master/windows-installer as far
as I know, not the monowiz.win32.nsi in the Mono repo (that looks
indeed very outdated and should probably be removed).
Very good news!
The windows installer is built by
https://github.com/mono/release/tree/master/windows-installer as far as I know,
not the monowiz.win32.nsi in the Mono repo (that looks indeed very outdated and
should probably be removed).
It'd be very helpful if you could also send a PR to
- I'd also like to run the Mono tests as a part of the build
verification. Are they expected to work under Windows/Cygwin?
I was not able to run the tests on Windows/Mono in current master. I
made this PR to address that: https://github.com/mono/mono/pull/1360
They should run on Windows/.NET
On 26/10/2014 16:28, Vincent Povirk wrote:
- I'd also like to run the Mono tests as a part of the build
verification. Are they expected to work under Windows/Cygwin?
I was not able to run the tests on Windows/Mono in current master. I
made this PR to address that:
Hi Guys,
I hope I didn't speak up too quickly. Confession: I thought I was on
the monodevelop list, not the mono-devel list. Delivering a new
version of NUnit to MD users is relatively easy. Switching actual mono
development is another matter, as I know from past discussions.
Nevertheless...
The MonoDevelop NUnit addin already uses NUnit 2.6.3:
https://github.com/mono/monodevelop/blob/master/main/src/addins/NUnit/packages.config
For Mono's own tests, I think your suggestion of unzipping the new version and
running the test suite is a good approach.
-- Alex
Date: Sun, 26 Oct
I am purely provided some background for interested hackers.
I stand by the original position that we should do all the minimal changes
required to get ASP.NET vnext to build/run, even if it does not deliver the
performance/scaling benefits at first.
As for the actual patch, I will review once I
Thanks, hope we can take advantage of that :-)
Date: Sun, 26 Oct 2014 10:21:30 -0700
Subject: RE: [Mono-dev] NUnit version for mono source tests
From: charliepo...@gmail.com
To: alex.koeplin...@outlook.com
If someone runs a test soon and finds bugs using 2.6.3 against 2.4.8, please
file them
Completely agree Miguel.
HttpTaskAsyncHandler is a required class for the webstack to compile (and
run I imagine) so any (working) implementation would be useful.
Thanks for your help as always Miguel.
On 26 Oct 2014 17:24, Miguel de Icaza mig...@xamarin.com wrote:
I am purely provided some
Hi, i found your post
https://mail.gnome.org/archives/commits-list/2013-October/msg04340.html
and right now I an unable to build monodevelop 5.6.2.5
this is full build log (sources from git):
http://pastebin.calculate-linux.ru/ru/show/10192
this is the first error:
CSC: error CS1705: Assembly
Heya! It seems you have gtk-sharp 3 installed on the system.
Did you build it from sources? If so, grab gtk-sharp 2.12.2x and build it
instead.
Арсен Шнурков arsen.shnur...@gmail.com wrote:
Hi, i found your post
https://mail.gnome.org/archives/commits-list/2013-October/msg04340.html
and right
Looks simple.
On Sun, Oct 26, 2014 at 10:57 AM, Martin Thwaites monofo...@my2cents.co.uk
wrote:
Hi All,
This is a simple PR for the property added in .NET 4.5.
I couldn't find any existing tests for the module, and I struggled to find
a way to test it.
All I've done to test it is added
Hi All,
When I put the code in for ReadEntityBodyMode I neglected to implement the
default in the HttpRequestBase.
I've set this to Classic as this should force callers to use the
HttpRequestBase.InputStream instead of the buffered/bufferless methods
(which aren't implemented). Although we have
Hi All,
I don't profess to know what it does, however, I've looked at the usage of
this in the aspnetwebstack, and under a few scenarios, it defaults it's own
helper method to CancellationToken.None. Therefore I'm assuming this is ok
as a default in the code.
Hi All,
This adds a couple of methods to the HttpRequestBase and HttpRequestWrapper
to access the relevant methods on the request.
We do have the GetBufferlessInputStream and it appears to be implemented,
however, it will likely not be used as the setting of the
ReadEntityBodyMode to classic in
Hi All,
Just another quick update.
Some potentially amazing news. I've managed to get a fairly large MVC
5.2/WebAPI running on mono! That is out of the box, without any special
versions of dll's (other than removing the Microsoft.Web.Infrastructure.dll
I think.
So, there are a few outstanding
29 matches
Mail list logo
