Quick question -- where can i find source for XAML parser in mono code
base, I am currently planning to start working on Olive WF.
Best Regards,
Vadi
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
The old XAML parser is available in:
olive/class//PresentationFramework/System.Windows.Markup/
But this does not implement the new System.Xaml.dll API.
There is a very solid XAML parser that we use for Moonlight written in C++:
moon/src/xaml.cpp
I think you could start on the new WF
Hi Miguel, I am strictly following the rule of not using any of MS code or
reflector. The way I started on it is,
1. First create all necessary class skeletons by looking at MSDN
2. then implement test cases with mocks/stubs
3. then do implementation
I am also thinking to follow one
Rodrigo,
Thanks for the input. Any of the other Mono/MacOS X folks have an opinion on
this change? I've been running our heavily multi-threaded app which embeds Mono
and haven't seen any issues. We're going to start removing this #define on our
build machine and our dev's Mono installs and see
Tom,
Looking back, apple had some issues with trylock in the 10.2/10.3 days, and
this came over for safety when we did the initial osx86 port. Its probably
safe to make this change on x86 on trunk, but I'd like some metrics if you
could.
#1, run it for a bit make sure you dont get any
Hi,
I'm wondering why this format doesn't work for mono, when it does for
windows?
I'm trying to send a simple post request to the service, which contains the
following:
{composite:{BoolValue:true,StringValue:aaa},composite2:{BoolValue:true,StringValue:bbb}}
This works fine in VS2008, but I
I'm going to go out on the limb here and guess that under Mono it assumes the
input to be always XML and doesn't look at the MIME type.
The error on line 1, position 1 in XmlTextReader seems to be a dead giveaway
for that. :)
- Steve
--
Steve G. Bjorg
http://mindtouch.com
Hi,
about an year ago I posted the following bug
https://bugzilla.novell.com/show_bug.cgi?id=402833
because we realized that the performance problem in our multi-thread
app was related to memory management:
By removing the #define line as you proposed, the performance problem
disappear and bug
Hello,
Our WebHttpBinding does support json-based requests and responses.
There is a lot of possibilities why you don't get json response instead
of xml, and I can't give you an answer with almost no information.
If you file a bug with the steps to configure and run the service, I'll
have a look.
I reran the revised test case Matteo provided here:
https://bugzilla.novell.com/show_bug.cgi?id=402833
Here are the results with NO_PTHREAD_TRYLOCK defined (i.e. before)
ws1048-snow:~ tom.philpot$ /opt/mono/bin/mono Main.exe
One Thread (method1) time=00:00:00.6318450
One Thread (method2)
Hello Eduardo,
Thanks, your repro was simple enough to try :) Now I'm getting some
ASP.NET integration issue that should be fixed. I'll see if further
issues exist once I fixed the issue I faced now. It may take a while as
I'm now full with other bugs, but I put your case on my stack.
Atsushi
11 matches
Mail list logo
