And that brings incompatiblity with .NET Core. That makes things just
worse. You cannot force other people to change their sanity just to
match your existing code that premises the wrong behavior that Microsoft
doesn't agree.
Atsushi Eno
On 2015年09月29日 14:58, Martin Thwaites wrote:
I'd have
You have no reason to be afraid of asking Microsoft to change the
behavior. I cannot find any justification to just ask Mono to change
things against Microsoft code behavior without asking Microsoft about it.
Atsushi Eno
On 2015年09月29日 01:15, Martin Potter wrote:
> I wasn’t aware that the M
is not for reporting issues though (as its
README explicitly says so).
Atsushi Eno
On 2015年09月28日 23:15, Martin Potter wrote:
> The default for XamlWriterSettings NewLineChars was changed from "\r\n" to
> "\n" when you imported the reference source and is what is p
Current Microsoft-based implementation is the correct one and it's been
there in post-4.0 versions.
Atsushi Eno
On 2015年09月28日 22:46, Martin Potter wrote:
> Atsushi,
>
> Were you (or someone else) going to get this fixed before 4.2 is ready to
> ship?
>
> Thank you,
> Mar
I had no idea when that commit was made, but that change was wrong.
Microsoft behavior is the one we should use in that case.
Atsushi Eno
On 2015年09月09日 01:50, Martin Potter wrote:
Way back in 2012, this commit
https://github.com/mono/mono/commit/9215ddf7ade5f0f0f54c2adb7b165e4e3e77433b
I have no idea what kind of issue you are talking about, but anyways
mono 3.8.0 is too old. Try newer versions. There should be even packaged
ones:
https://build.opensuse.org/search?utf8=%E2%9C%93_text=mono=Submit+Query_tracker=bnc==0=1=0=1=0=1=0=0_type_id=
Atsushi Eno
On 2015年09月02日 02:45
They are part of WPF which mono does not support at all.
moonlight does not build anymore as we removed required bits in mono
(unless you check out very old mono).
Atsushi Eno
On 2015年07月21日 23:01, Justin Dearing wrote:
I'm running Mono 4.0.2 on Centos 7 from the yum repo
http
4.0 was branched before System.Data import so the mentioned fix is not
there yet. You can check master build from github to see if it indeed
fixes the issue.
Atsushi Eno
On 2015年06月05日 04:38, Peter Hagen wrote:
Hi
Its great to see so many updates lately. Since the 4.0 update I have
had
Wait, you are building mono _on_ Android? I don't think mono supports
custom Android build. Things WON'T work and it is quite as expected.
That's not a bug at all.
We Xamarin don't even use full mono stack. xbuild is totally out of
mobile scope.
Atsushi Eno
On 2015年06月06日 00:26, Cyd
You need a clean build. Unfortunately there is some issue in the build
script that prevents incremental builds that sometimes bites us.
Atsushi Eno
On 2015年06月06日 04:21, Peter Hagen wrote:
Unfortunately I can not build master at the moment
../../../external/referencesource/System.Data.SqlXml
/Desktop/x.proj.
Build succeeded.
0 Warning(s)
0 Error(s)
Time Elapsed 00:00:00.0708910
A precise repro steps would help inspecting possible bugs.
Atsushi Eno
On 2015年06月03日 19:31, Cyd Haselton wrote:
Thing is xbuild doesn't even complain about the syntax errors in that
project
Hello,
I disabled the version check for MDAC on mono master. Could you check if
it works now?
Thanks,
Atsushi Eno
On 2015年05月09日 15:03, Atsushi Eno wrote:
Hello,
It seems that referencesource Odbc implementation has extra check [*1]
that does not match unixodbc behavior. I will disable
Hello,
It seems that referencesource Odbc implementation has extra check [*1]
that does not match unixodbc behavior. I will disable those checks next
week.
[*1]
https://github.com/mono/referencesource/blob/mono/System.Data/System/Data/Odbc/OdbcEnvironment.cs#L25
Atsushi Eno
On 2015年05月08
it or at least
not very soon.
Usually that's correct, but for System.Data.Odbc we use unixodbc that
PInvokes odbc32.dll compatible library. We already imported it.
Atsushi Eno
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http
properties.
So probably those classes generates bytes in some unexpected order?
Though some of those crypto stuff is regressing (regardless of CPU arch)
in recent referencesource porting, so that problem might just be temporary.
Atsushi Eno
On 2015年04月29日 03:40, Neale Ferguson wrote:
The following
. That applies to any of mono versions (even with
referencesource).
Atsushi Eno
On 2015年04月28日 11:16, discofire wrote:
Ok, so it looks as though there is a problem with the System.Data.Odbc
library... a pretty major and glaring problem that I can't believe was even
allowed to be checked into the repository
There is no test, so I don't know if it's good.
Atsushi Eno
On 2015年02月22日 03:32, Alexander Grep wrote:
Hello,
Miguel, thanks for implementing the fix!
Sorry to bother you once more:
I'd be grateful if you could also have a look at
https://bugzilla.xamarin.com/show_bug.cgi?id=20764
by default and people won't notice they can log things though.
Atsushi Eno
On 2015年02月15日 22:38, Miguel de Icaza wrote:
Hello, [ I am CCing Atsushi so he can eyeball the patch ]
Thanks for the background research and for pointing me to that
long-standing bug.
It seems like a pull request
Not really; changes that make it to load other assemblies are also good
(but _if_ that's too much, then it'd be still okay to hard code others).
Atsushi Eno
On 2015年01月28日 08:51, Philip Garrett wrote:
On Jan 27, 2015, at 3:22 AM, Atsushi Eno
atsushi...@veritas-vos-liberabit.com
exist in mono itself would be fine (as long as it works, when those
assemblies can be resolved).
Thanks,
Atsushi Eno
On 2015年01月25日 06:40, Philip Garrett wrote:
Mono.Messaging allows you to specify a custom messaging provider in the
MONO_MESSAGING_PROVIDER appsetting. But it appears only to work
everything
in mono master, so your effort is welcome :-)
I had been working on porting System.Xml but we have handful of issues
to sort out (as it must not depend on code generator for iOS and MS
XmlSerializer, unlike ours, is totally based on that).
Atsushi Eno
On 2014年12月17日 05:35, Bernie
that anyone
can review.
Anyways, basically we need patched version for mobiles. And some of
those reside in mono tree, so before nuking them out they have to be
rewritten to become independent of mono tree.
Atsushi Eno
-- Alex
___
Mono-devel-list
Let's remove my Commons.Xml.Relaxng. It is really isolated work.
Atsushi Eno
On 2014年11月28日 00:01, Alexander Köplinger wrote:
Judging from the recent version bump in git to 3.99 it looks like the
next release after 3.12 will be Mono 4.0.
As this is a major release it'll allow us to remove
Actually the mono runtime team at Xamarin seems to be working on it, so
you should ask them, not me.
But anyways current System.Xml code in referencesource is still
incomplete to actually replace things. It will be done only after
Microsoft's open-sourcing process is done.
Atsushi Eno
specifications, after we have implemented this feature
mostly in 2003-2004.
Atsushi Eno
On 2014年11月12日 15:15, MarLOne wrote:
Hello,
Not sure if this issue has been raised as it is driving me nuts as another
Mono/.Net runtime behavior differences.
I have a xml schema called FamilyTree2.xsd
Actually I was wrong, it's already there:
https://github.com/Microsoft/referencesource/tree/master/System.Xml/System/Xml/Schema
Atsushi Eno
On 2014年11月13日 00:05, Atsushi Eno wrote:
And Microsoft has announced open-sourcing .NET! So you don't have to
spread your hate speech on bugs, we
And Microsoft has announced open-sourcing .NET! So you don't have to
spread your hate speech on bugs, we will take their good code.
https://github.com/dotnet/corefx/tree/master/src
(No XML Schema implementation yet, but I assume that would happen at
some stage.)
Atsushi Eno
On 2014年11月12日
Hi,
On 2014年10月24日 21:04, Jesper Lund Stocholm wrote:
Hi Athushi-San,
-Original Message-
From: Atsushi Eno [mailto:atsushi...@veritas-vos-liberabit.com]
Sent: Friday, October 24, 2014 1:19 AM
To: Jesper Lund Stocholm; mono-list@lists.ximian.com
Subject: Re: [Mono-list] Problems using
Hello,
An element has to contain one ore more pattern,
https://www.oasis-open.org/committees/relax-ng/spec.html#full-syntax
which is missing in your element name='book'/element.
Specify empty/ there.
Atsushi Eno
On 2014年10月21日 15:15, Jesper Lund Stocholm wrote:
I am trying to use
Phew, there was a bug! It was about handling default namespace. I fixed
it in master.
https://github.com/mono/mono/commit/3d9a2b7
Until you get the fixed version, a workaround is to put explicit
declaration on top:
default namespace =
Atsushi Eno
On 2014年10月24日 06:14, Jesper Lund Stocholm
people might have some comments.
Atsushi Eno
morteza adi wrote:
I'm getting crazy :)
I removed my cloned source and get a new clone from git repo. nothing
changed, again same problem.
I also tried to make the code in another pc - ubuntu 12.04 I got a
new error:
make[2]: Entering directory
generalized way of generating appropriate set of projects for
each classlib assembly.
[*1]
https://github.com/atsushieno/mono/blob/msbuilddll2/msvc/scripts/net_4_5_msbuild.sln
Atsushi Eno
Hüning, Christian wrote:
Hi,
I wondered if there is a way to efficiently and effectively develop
mono
Let's get this patch in and fix any possible issue later. Thanks!
Atsushi Eno
(2013年11月07日 18:07), Alistair Bush wrote:
Hi guys,
Please note that I have cleaned this up and bit and submitted a pull request
https://github.com/mono/mono/pull/800
Feedback welcome.
On Wed, Oct 30, 2013 at 11
of moving target, so
you'll have to track the latest API that its base API expects.
Atsushi Eno
(2013年11月03日 11:34), Kendall Shaw wrote:
Does this addin exist:
http://monodevelop.com/Developers/Articles/Refactoring
MonoDevelop defines the refactoring system in the
MonoDevelop.Refactoring addin
From your message I assume you think you can wait for someone to
implement it, but there is no one working on ASP.NET stack. So you are
the most likely one who understand what it is and who is most able to
implement it.
Atsushi Eno
Martin Thwaites wrote:
I'm not sure of the best place
Jonathan Gagnon wrote:
On Fri, Jul 19, 2013 at 1:05 PM, Atsushi Eno
atsushi...@veritas-vos-liberabit.com
mailto:atsushi...@veritas-vos-liberabit.com wrote:
(2013年07月17日 21:25), Jonathan Gagnon wrote:
On Tue, Jul 16, 2013 at 12:16 PM, Atsushi Eno
atsushi...@veritas-vos
(2013年07月17日 21:25), Jonathan Gagnon wrote:
On Tue, Jul 16, 2013 at 12:16 PM, Atsushi Eno
atsushi...@veritas-vos-liberabit.com
mailto:atsushi...@veritas-vos-liberabit.com wrote:
Jonathan Gagnon wrote:
It does not work when the SAML document is not referring to
any DTD
(and not
iD ?), they will have to fix their bug.
Atsushi Eno
(2013年07月12日 23:58), Jonathan Gagnon wrote:
I have encountered a bug similar to 4938
https://bugzilla.xamarin.com/show_bug.cgi?id=4938.
My problem is that mono does not find the reference id because the id
is in uppercase ('ID' instead
it is not implemented. (I won't believe that this override does not
do anything, at least without certain experiment shown.)
No one works on System.Configuration stuff nowadays but if you have some
patch to implement it, that would be welcomed, reviewed and merged if
good :)
Atsushi Eno
Torben H. Nielsen
XmlReaderSettings to consider XmlSchema or DTD. Hence that does not
cause any problem for SAML.
(Also note that SignedXml implementation could override
SignedXml.GetIdElement(). Mono's WCF implementation makes use of it to
support WS-Security ID attribute.)
Atsushi Eno
Jonathan Gagnon wrote:
This is true
and go ahead to
apply the changes.
Atsushi Eno
Thanks,
Jonathan
On Tue, Jul 16, 2013 at 10:24 AM, Atsushi Eno
atsushi...@veritas-vos-liberabit.com
mailto:atsushi...@veritas-vos-liberabit.com wrote:
Whenever SAML document instance refers to its schema or DTD that
will validate ID
. I'm sure that
almost no one cared this API (at least no one contributed to the
implementation), so you're most likely the one at best knowledge here :)
And with code people can talk better.
Atsushi Eno
___
Mono-devel-list mailing list
Mono-devel
I believe we only have EntityFramework.dll (dll name has changed when it
went to codeplex).
Atsushi Eno
Rafael Teixeira wrote:
Seems like the Entity Framework is not properly installed, or is not
being referenced (System.Data.Entity.dll).
Rafael Teixeira
O..:.)
On Tue, Jun 4, 2013 at 2
Hi,
Could you file a bug on bugzilla.xamarin.com? Unless someone else goes
ahead and fix, I'll take care of that obsolete technology at some stage.
Thanks,
Atsushi Eno
Tobias Kiertscher wrote:
Hi,
I tried to run code with XML schema based validation on mono 2.10.8 and
3.0.10 that works
.
I believe there actually wasn't such rejection to make XML Serializer
compatible with .NET and break existing mono users compatibility.
You'll be welcomed to contribute such changes and someone in dev would
take care.
Atsushi Eno
___
Mono-list
to indicate what are new to implement.
Atsushi Eno
IridiumStudios wrote:
Hey guys,
After a quick search, I found that System.Speech is apparently supported in
Mono (
http://go-mono.com/status/status.aspx?reference=4.0profile=4.5assembly=System.Speech
http://go-mono.com/status/status.aspx?reference
No you didn't, or yes we did ;-)
I made some changes to Rx assemblies builds in git master so that they
are now included too.
Atsushi Eno
sebastian wrote:
We noticed that Observable.GetAwaiter is missing in the 4.5 Rx
framework bundled with mono. Did we build mono incorrectly
yw - it still seems like some xml schema issue, namely PSVI handling in
XmlSchemaValidatingReader (ok, less than 0.1% of people understand it).
In case you don't mind patching EF, here is mine that goes beyond that
issue.
Atsushi Eno
Олег wrote:
Many thanks to Atsushi Eno for a solution
should be much easier.
Atsushi Eno
Oleg wrote:
Hello,
There is a 5 months old bug #6653
https://bugzilla.xamarin.com/show_bug.cgi?id=6653 and discussions on
StackOverflow about troubles with Entity Framework when it loads
metadata from xml model:
* How to setup Entity Framework / SQL
. If it is about XmlSchema, there are still two ways to
parse it - XmlSchema.Read() and XmlSerializer.Deserialize() which are
different.)
Atsushi Eno
Alistair Leslie-Hughes wrote:
Hi,
I'm using WINE+Mono to install a Microsoft product. However, when it
tries to validate the Schema (during
That doc looks cool :) I just updated the page. Thanks for sharing the info.
Atsushi Eno
Dimitar Dobrev wrote:
The online documentation for Qyoto is uploaded at
http://api.kde.org/qyoto-4.0.5-api/index.html. I hope it's OK now.
--
View this message in context:
http://mono.1490590.n4
I've been fixing the build. Sorry for inconvenience. You can check
https://wrench.mono-project.com/Wrench/ for ongoing fixes.
In the end of this fixage, Reactive Extensions will be available in mono.
Atsushi Eno
Jonathan Shore wrote:
Mono installation problem. Looks like the System.Reactive
patches. But if you really have reason, share it, I'm
personally all ears :)
Atsushi Eno
Alistair Leslie-Hughes wrote:
Hi,
This framework is constantly appearing as an issue when using WINE+mono.
What would it take, to get the current implementation of the
Presentation Framework from the Olive
Hi,
I thought you are supposed to post the link...?
Atsushi Eno
Dimitar Dobrev wrote:
Hi,
It's been ten days and the page is not updated yet. Is there some kind of a
problem?
--
View this message in context:
http://mono.1490590.n4.nabble.com/Qyoto-description-correction-about-docs
I build mono master on Ubuntu 12.10 without problem. Does it still
happen with the latest master with clean tree?
Atsushi Eno
Matt Calder wrote:
Follow up,
Disabling sgen in configure (--with-sgen=no) allows mono to build. So
I guess the question is, is there a way to build with sgen
I won't remove description without verifying the fact changes. So either
post the link to the doc website or doc repository or whatever. There is
no reason for me to be urged to do it without sufficient information. Or
you can ask others.
Atsushi Eno
Dimitar Dobrev wrote:
I see that we've
Hi,
I'll make changes (maybe by dropping pros-cons style description). Once
you guys get online docs become available, so let us know with the URL
so that we can put link to there then.
Atsushi Eno
Dimitar Dobrev wrote:
Hi all,
A few days ago I integrated generation of XML code comments
They are actually the same encoding.
https://github.com/mono/mono/blob/master/mcs/class/I18N/CJK/CP932.cs#L932
Atsushi Eno
Ian Norton wrote:
On mono 3.0.0 ( amd64 pmono ) the following work fine for me:
csharp using System.Text;
csharp Encoding.GetEncoding(932);
I18N.CJK.CP932
csharp
some platform abstraction layer for System.Speech
API and then write Mac Speech API based implementation (in case you
didn't think about that). It could be in the same assembly, like we do
for System.Windows.Forms.dll.
Hope this helps.
Atsushi Eno
Thanks,
Chris McKinnon
Hello,
You need to use libraries that are built with Mono for Android. Whatever
you're trying to use seems to be built either with Silverlight or WP7,
which is not the case.
Atsushi Eno
masterdimar wrote:
Hi People.
I'm referencing a C# dll (I don't have the code) and I receiving
Cool :) I left my stubs for WF4 in our old olive module which used to
be for new API. It could be reused if you want.
https://github.com/mono/olive/tree/master/class/System.Activities
Atsushi Eno
Charles Benassaya wrote:
Hi,
I'm ceo of Natan, software development company in France. We
As Rodrigo answered, WPF is not available, but System.Xaml.dll exists in
Mono, in case you want to implement or create your own XAML-backed
framework.
Atsushi Eno
Ronaldo Nascimento wrote:
I was just curious if there is any consideration to provide WPF/XAML for
mono or develop something
Hello,
I'm not really a runtime hacker, but I think this sort of function
could be placed in some file (either existing or new) under mono/utils/
directory. Your glib-incomplatible function could not be tested within
eglib tests.
Atsushi Eno
Weeble wrote:
Having diagnosed this bug (when
. Or
Ubuntu/Debian people may already have such packages apart from official
repos. AFAIR there are some 2.0-cil packages in Ubuntu.
Atsushi Eno
IBBoard wrote:
It appears there is a problem with running older .Net apps on the
latest versions of Ubuntu. If you compile for .Net 2.0 (perhaps
because
from mono later, like we killed
1.1 profile in the past. Building for 4.0 is absolutely the right direction.
And this rather sounds like I don't want to build 2.0 packages, so you
build 2.0 packages for me instead ...
Atsushi Eno
Thanks,
IBBoard
On 11 May 2012 09:00, Atsushi Enoatsushi
IBBoard wrote:
Hi...
On 11/05/12 17:38, Atsushi Eno wrote:
IBBoard wrote:
...
Someone in Ubuntu might have decided that GTK# for .Net 4.0 only might
have been a feature and hence not a bug when 2.0 apps won't work,
but it seems like a very badly planned and unnecessary change.
That sounds
One possibility idea is this: interoperability wise, WCF sucks when
there is generic types by adding hash-based suffix on the element names.
So, give explicit name on the dictionary object by subclassing it or
whatever. If it still doesn't work, I have no idea.
Atsushi Eno
hayate wrote:
Hi
- System.Json
Atsushi Eno
Alex Rønne Petersen wrote:
Hello folks!
I'm planning to write and maintain a page listing maintainers of
specific parts of Mono. When you have a patch that you wish to
contribute, it is usually easier to go directly to the maintainer of
the part of the code that you
Just curious, what's blocking you from implementing those methods by
yourself? I'm sure they are taking patches.
Atsushi Eno
HI All:
I noticed that Microsoft.VisualBasic.Strings.StrConv method is not
completely implemented, it does not support:
VbStrConv.Wide
VbStrConv.Narrow
, no
TimeSpan support).
The new sources are in mcs/class/System.Json-new so the existing
System.Jsoncan be easily replaced with it.
[*1] http://aspnetwebstack.codeplex.com
[*2]
https://github.com/mono/mono/blame/master/mcs/class/System.Json/Test/System.Json/JsonValueTest.cs
Atsushi Eno
I'm not very familiar with Macs but maybe because file names under OSX
file system are based on Unicode NFD variant?
Atsushi Eno
Jared Watts wrote:
I opened bug 3860 https://bugzilla.xamarin.com/show_bug.cgi?id=3860
earlier today, but I’m curious if anyone on the dev list has run
I have never tried but this might be a good starter for those interested
in implementing such enhancements.
http://mvp-xml.sourceforge.net/exslt/
Atsushi Eno
Miguel de Icaza wrote:
Hey guys,
The current XPath stack on Mono is tied up to 1.0 because this is what
.NET had.
Every once
released mono versions. AFAIR Paul Betts (the ReactiveUI man)
mentioned some compiler issue at Monospace [*1], but git master worked fine.
[*1] http://www.infoq.com/presentations/Reactive-Extensions-and-ReactiveUI
Atsushi Eno
___
Mono-list maillist
into *another*
file, so that everyone does not have to re-extract your archive over and
over again.
Thanks,
Atsushi Eno
I've narrowed the issue down - it only occurs when XDocument.Load is
used with LoadOptions.PreserveWhitespace. I've uploaded an example
demonstrating this error. The relevant XML
Thanks for the updated test. Now I confirmed and fixed the issue in
master 40f84f3.
Atsushi Eno
Drew DeVault wrote:
Sorry - the poorly-formatted XML issue was an oversight on my part;
it's actually the result of running the program. I have also modified
it to save to a new file instead
that everyone can examine is appreciated.
Atsushi Eno
I can duplicate this problem on Linux Mint 12 and Ubuntu 11.10, but
Microsoft.NET on Windows 7 does not have the issue. The issue is that
my XDocument becomes corrupted the moment it loads, and cannot be
saved. Strangely, I am able to traverse
Yes without the actual xsd we can't do anything.
Atsushi Eno
Dear all,
I'm trying to generate a .cs based on an xsd but I get following error:
[s.canepa@proj13 VectorGraphicAnimation]$ xsd Vga.xsd /classes
/namespace:VectorGraphicAnimation /language:CS
System.InvalidCastException
Hello,
Without code, we cannot give any thoughts.
Atsushi Eno
On 2011/08/26 6:49, blaynebayer wrote:
I get the following error when performing a wcf client request to a third
party web service using soap:
Read by order only possible for encoded/bare format
.
Atsushi Eno
On 2011/08/23 1:32, Jb Evain wrote:
What Atsushi means is that this piece of code is exploiting a private
implementation detail of the .net framework, so no wonder it doesn't
«work» on Mono.
On Tue, Aug 23, 2011 at 10:28 AM, Stefanos A.stapos...@gmail.com wrote:
2011/8/23
I wonder where the corresponding sections in ECMA CLI specification or
.NET documentation that mentions those functions shown in the code are.
Atsushi Eno
On 2011/08/22 19:21, Brandon Perry wrote:
Hi,
The following link contains code that runs just fine in .NET on win 7.
However, when run
be the same - I
had kept committing the fixes on both master and 2.10 when
I used to work on the entire wcf stuff).
Atsushi Eno
Hi Atsushi,
Here is the code (from Microsofts site)
using System;
using System.ServiceModel;
using System.ServiceModel.Description;
using System.ServiceModel.Web
Atsushi Eno
Hi all!
I have setup the CalcService example using WebServiceHost and I'm keep
getting these errors on my screen:
Exception A system exception has occurred. at
System.ServiceModel.Description.WebHttpBehavior+EndpointNotFoundOperationInvoker.Invoke
(System.Object instance
I just confirmed that it does not reproduce (I am pretty sure it must
not, as such problematic error would have flooded this list). If you
still think there is bug, come up with the problematic test xml stream
and corresponding code that creates the actual IFXstream.
Atsushi Eno
Hi,
I'm having
Then as I replied to this thread earlier, it is fixed in git master and
2-10 branches.
Atsushi Eno
Hi, sorry for a delayed response.
If you are referring to
http://veritas-vos-liberabit.com/monogatari/2009/12/mono-wcf-advent-day-6-aspnet-hosting.html
this sample, then I couldn't get
We had support for message security which is about WS-Security very
partially, but we are not going to support it.
Atsushi Eno
I'm trying to migrate an existing application to Mono (v2.10.2).
Therefore I created a test WCF service with BasicHttpBinding and
message security. The client
It is hard for me to parse your message. Do you mean, you could run *my*
sample but couldn't get your case that you didn't give us wsdls and
hence left unfixed?
Atsushi Eno
I just can't get this to work. I tried self hosting, it seems to work
at least a hello world service. Let me see if I
Hello,
Without the actual sources I can only guess, but .NET 4 has
couple of configuration changes which 2.8.x does not likely
to support. Also it has much less configuration elements
support as compared to 2.10.x.
Atsushi Eno
Hi, I am trying to host a simple application with one aspx, asmx
It is more important than you think. You might have written very few
code, but that does tell us that it is driven by default configuration
which tells a lot.
Anyways give it a try with 2.10, which likely give different results :)
Atsushi Eno
Well, It's like a helloworld service
I have really no clue without the actual schemas. But you can disable
metadata services that is extraneous unless you have to serve wsdls.
Atsushi Eno
Ok, tried with 2.10.2. The old error is gone but server returns a fault.
I tried adding MonoSetEnv MONO_STRICT_MS_COMPLIANT=yes as per
wonder what kind of
services you writing. Are you sure you don't hit not-supported
features?
Atsushi Eno
Here's how I fixed my WCF woes: I scrapped everything WCF I had done
and went with ASMX. I struggled with configuration for quite some
time myself. And then, even when I found the magic
No, not UTF-16. Default encoding is platform dependent. e.g. it is MS932
on my Japanese Windows, Latin1 for those in the U.S., and UTF-8 on
modern Linux desktop like gnome2 or 3.
Atsushi Eno
(2011/07/21 11:47), Pablo Ruiz wrote:
Mono uses UTF8 as default encoding. .Net uses UTF16
On Thu
Hello,
Since I cannot get XML and SCHEMA my answer can only be it *could* be :P
And even if there is a bug, you won't get any bugfixes for 1.9.x. It is
way too old. Try 2.10.x or git HEAD instead.
Atsushi Eno
(2011/07/11 4:41), dabeat wrote:
Hi,
When I try to validate an XML against an XSD
Please provide a verifiable test case. We have general NetTcpBinding
examples that are known to work.
https://github.com/mono/olive/tree/master/samples/wcf/tcp-transport
Atsushi Eno
(2011/06/18 0:29), Cocai wrote:
In Mono 2.10.2 when using a the WCF binding NetTcpBinding and using
It is done in git master and mono-2-10 branches.
Atsushi Eno
(2011/06/28 14:58), Atsushi Eno wrote:
Hello,
(2011/06/17 18:05), Cocai wrote:
Hi Atsushi,
After some other test I have discovered:
MyGenericsstring in .Net become i:type=\b:SpeakerOfstring\ but in
Mono
is i:type=\d3p1
that such {0} could work to fill generic type args.
I'll implement it. Thanks for the info.
Atsushi Eno
___
Mono-list maillist - Mono-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-list
);
writer.Close ();
}
}
Atsushi Eno
(2011/06/16 4:35), tferch wrote:
Using System.Xml.XmlWriter, I had a strange problem with writing the
namespace declaration into the file. The line:
writer.WriteAttributeString(xmlns, NCXNamespace,
“http://www.w3.org/2000/xmlns
Not that I know of... at least port 80 is not special in WCF code itself.
Atsushi Eno
(2011/06/17 0:33), Nadeem Backus wrote:
Hello,
I have a working console hosted WCF application that works perfectly fine
on ports 81,8080 and others, but on port 80 the program runs without error
is a
solution.
Atsushi Eno
(2011/06/17 1:38), Cocai wrote:
The serialization of a generic class by DataContractSerializer of a generic
class get different result if it was made in Mono 2.10.2 or in .Net 4, so
they are not interoperable.
I have tried with:
[DataContract]
public class
());
using (var xw = XmlWriter.Create (Console.Out))
ds.WriteObject (xw, r);
}
}
As for the fault, I cannot guess what throws it without the actual
failing code.
Atsushi Eno
(2011/06/12 22:27), James Darbyshire wrote:
Hi Atsushi,
It turns out the problem
Hello,
NotSupportedException is not NotImplementedException, so it is likely
intended to actually throw that error. It is still possible that the WCF
internal goes wrong path and reaches that WriteMessage() part, but
without actual code to examine I cannot guess for sure.
Atsushi Eno
(2011
1 - 100 of 1323 matches
Mail list logo