Ah, thanks for providing the answers to the comments.
This pull request has been merged.
On Fri, Mar 6, 2015 at 9:25 AM, Steffen Kieß
steffen.ki...@ipvs.uni-stuttgart.de wrote:
Hello,
pull request https://github.com/mono/mono/pull/1155 fixes some issues
with string handling in System.Json:
Hello,
pull request https://github.com/mono/mono/pull/1155 fixes some issues
with string handling in System.Json:
- Escape control characters, as required by JSON spec
- Escape invalid surrogate pairs
- Escape characters invalid in JavaScript strings
- Escape / for HTML script tags
- Fix
On 06/03/2015 12:42, Edward Ned Harvey (mono) wrote:
From: mono-devel-list-boun...@lists.ximian.com
[mailto:mono-devel-list- boun...@lists.ximian.com] On Behalf Of
Federico Di Gregorio
[snip]
I agree that the pattern you've suggested is the better pattern, to
avoid NullReferenceException in a
Hi,
I have discovered that the Mono implementation of WebClient doesn't behave
as described in this MSDN article:
https://msdn.microsoft.com/en-us/magazine/gg598924.aspx
Specifically all Async methods don't capure the current
SynchronizationContext to later run the event handlers on it.
On 06/03/2015 13:12, Marek Safar wrote:
Hi,
I have discovered that the Mono implementation of WebClient doesn't
behave as described in this MSDN article:
https://msdn.microsoft.com/en-__us/magazine/gg598924.aspx
https://msdn.microsoft.com/en-us/magazine/gg598924.aspx
Now that Mono 4.0 gets rid of the 2.0 and 3.5 .NET profiles I fear we'll gonna
break a lot of people that want to compile against those profiles.
Should we put those profiles back into
https://github.com/mono/reference-assemblies? Or at least make it easier to
acquire them?
-- Alex
On 05.03.2015 23:18, mimi wrote:
Thanks Robert! It worked out but I got another problem.
classDictionary = mono_class_from_name(mono_get_corlib(),
System.Collections.Generic, Dictionary' 2); NULL
It's Dictionary`2. Notice the backtick.
classDictionary =
Hi *,
I have discovered that the Mono implementation of WebClient doesn't
behave as described in this MSDN article:
https://msdn.microsoft.com/en-us/magazine/gg598924.aspx
Specifically all Async methods don't capure the current
SynchronizationContext to later run the event handlers on it.
From: mono-devel-list-boun...@lists.ximian.com [mailto:mono-devel-list-
boun...@lists.ximian.com] On Behalf Of Federico Di Gregorio
I have discovered that the Mono implementation of WebClient doesn't
behave as described in this MSDN article:
It seems, the class status page for WebClient
