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
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
/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日
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
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
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
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
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
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
- 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
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
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
://mono.1490590.n4.nabble.com/incomplete-nunit26-migration-patch-td3430831.html
The situation has not been changed since that email (sadly... ;)
Atsushi Eno
Hi, I'd like to see Monodevelop to integrate NUnit 2.5, but I was told
(on monodevelop irc channel) that a requirement
://mono.1490590.n4.nabble.com/incomplete-nunit26-migration-patch-td3430831.html
The situation has not been changed since that email (sadly... ;)
Atsushi Eno
Hi, I'd like to see Monodevelop to integrate NUnit 2.5, but I was told
(on monodevelop irc channel) that a requirement
://mono.1490590.n4.nabble.com/incomplete-nunit26-migration-patch-td3430831.html
The situation has not been changed since that email (sadly... ;)
Atsushi Eno
Hi, I'd like to see Monodevelop to integrate NUnit 2.5, but I was told
(on monodevelop irc channel) that a requirement
://mono.1490590.n4.nabble.com/incomplete-nunit26-migration-patch-td3430831.html
The situation has not been changed since that email (sadly... ;)
Atsushi Eno
Hi, I'd like to see Monodevelop to integrate NUnit 2.5, but I was told
(on monodevelop irc channel) that a requirement
Hello,
importNode() on DocumentType is invalid in DOM Level 2 Core
specification[*1], that's why it had been rejected.
It can be now imported in git (master and mono-2-10).
[*1] http://www.w3.org/TR/DOM-Level-2-Core/core.html#i-Document
Atsushi Eno
(2011/05/18 21:05), Vincent DARON wrote
It's just a bug, so please file one on https://bugzilla.novell.com.
Atsushi Eno
(2011/04/21 18:26), Cocai wrote:
In a simple service like
[ServiceContract]
public interface IMyService
{
[OperationContract]
void Request(Message msg);
}
if is added
of CompareInfo.
Atsushi Eno
(2011/04/14 16:02), Nicklas Overgaard wrote:
Hi,
It's now filed as bug #687444
/Nicklas
On Wed, 2011-04-13 at 17:56 -0300, Rodrigo Kumpera wrote:
Please file a bug report so this bug isn't forgotten.
On Wed, Apr 13, 2011 at 3:52 PM, Nicklas Overgaardnick
Hey,
(2011/04/15 6:31), Jonathan Pryor wrote:
On Apr 13, 2011, at 4:06 AM, Atsushi Eno wrote:
Do you have any ideas how to solve this problem?
Is it actually a problem? :-)
Sadly yes... it blocks us from creating useful WCF diagnostic xml logs.
The reason I ask is that I vaguely recall
Ah, nm, there actually wasn't any wrapper element to single log entry. I
thought they were wrapped by an element for each running process.
So, Flush() would mostly work. That does not solve custom trace
listener, but I don't care :P
Atsushi Eno
(2011/04/15 12:36), Atsushi Eno wrote:
Hey
wrapper for the
TraceListener, which was wrong too as the stream could be already GC-ed).
Atsushi Eno
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
as NotDotNet, make
run-test-ondotnet now passes in corlib (with tons of failures...)
I posted my results to monobin: http://monobin.com/__m20041c31
Atsushi Eno
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman
Thanks for the patch. I have locally applied it to not forget it, and will
examine and commit if it does not regress.
(As I posted earlier WCF work is suspended until build gets fixed.)
Atsushi Eno
(2011/03/25 18:46), Peter Gerbrandt wrote:
Hello everyone,
ContractDescriptionGeneratior
I have almost explained in the subject, but any WCF effort has been
stopped for weeks due to repeating regressions in base stack.
Current one is related to some assembly loader issue I reported to the
team earlier on 18th.
So please don't expect any bugfixes until it gets fixed.
Atsushi Eno
Agreed, though the suggestion may still work if the type has
op_Equality() overload.
Atsushi Eno
(2011/03/25 1:31), Stifu wrote:
From my experience, null checks are really, really cheap, to the point I've
had troubles measuring any difference between code paths with and without
null checks
of `InterlockedExchange' from
incompatible pointer type
make[3]: *** [libmonoruntime_la-threadpool.lo] Error 1
make[3]: Leaving directory `/home/atsushi/svn/mono/mono/metadata'
Now WCF is not hackable state again.
Atsushi Eno
___
Mono-devel-list mailing list
This Windows-specific API is not implemented (note that there are some
*not working* code).
Atsushi Eno
(2011/03/11 8:08), Ondrej wrote:
Hello,
I am trying to port my .Net application to Mono 2.6.4.
The problem I am facing is, that I am not able to send data via the named
pipe by using
Hi Peter,
Thanks again for the patch. I fixed a bit for moonlight build (you can also
assure that by running configure --with-moonlight=yes on topdir and
make PROFILE=moonlight_raw at mcs/class/System.ServiceModel) and
pushed it into git master and 2-10 branch.
Atsushi Eno
(2011/03/11 20:49
Isn't it now part of gnome-desktop-sharp?
Atsushi Eno
(2011/03/10 7:09), Paul Johnson wrote:
Hi,
Not sure why, but gtkhtml-sharp seems to be missing from gtk-sharp-2.12.10
Has it been moved elsewhere or is there a missed dependency somewhere
that the config file is not picking up
Thanks for the nice patch :) I have checked it in git (with some minor
fixes).
Atsushi Eno
(2011/03/08 17:55), Peter Gerbrandt wrote:
Hello,
.NET WCF occasionally transmits value type QNameIndex (0xBC) in attribute
nodes.
I've created a small patch to support this.
The unit tests
Thanks for the nice patch :) I have checked it in master and 2.10 branch
with cosmetic code formatting fixes.
Atsushi Eno
(2011/03/04 19:17), Peter Gerbrandt wrote:
Hello,
I want to use the same interface as service contract and as callback contract.
Currently this is not supported by mono
Your client is likely .NET and tries to use transport security feature.
Turn it off.
Note that MoMA is not helpful for WCF very often because it is impossible
to examine *.config files and which features those config sections require.
Atsushi Eno
(2011/03/01 12:58), Compy234 wrote:
Hey guys
/threadpool.c
Gonzalo is working on it.
Atsushi Eno
(2011/02/25 11:32), Atsushi Eno wrote:
I forgot a couple of notes:
- It should affect only on master, as the verifier fix is only in there.
- A quick remedy would be to temporarily revert the verifier fix, if fixing
Windows build is not very
Hello,
I don't think you really read my message.
Atsushi Eno
(2011/02/17 0:36), rjhdakota wrote:
I am having what I believe is the same problem. You say basic authentication
is working, any examples? Our project needs the ability to authorize a
connection, and currently we cannot. Here
This is not for general mono users list but for those who hack mono itself.
Check mono-list instead and you'll find very similar question there (unless
you are the same person who posted that in fact).
Atsushi Eno
(2011/02/16 5:07), rjhdakota wrote:
I am working on a WCF service in MONO
could be created like this:
ls ../../build/common/*.cs */*.cs | grep -v *-check.cs
Foo.dll.sources
cd Test; ls */*.cs ../Foo_test.dll.sources; cd ..
Atsushi Eno
(2011/02/13 12:11), Miguel de Icaza wrote:
Hello guys,
I have resumed my work on creating visual studio project files
possible to not be based on nunit adding but rather
include a standalone test runner project (executable) that includes all
nunit stuff.
Atsushi Eno
(2011/02/14 18:52), Atsushi Eno wrote:
The newer system should be as convenient as dll.sources model. Without
as easy step as to add just one line
=40host_id=8).
Atsushi Eno
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
marked. And I
won't remove those attributes when there are reasons.
Why don't you just *run* it and see if it works or not instead?
Atsushi Eno
(2011/01/20 22:30), Bob PS Watson wrote:
Hi,
I tested the xml.schema.linq which is the managed provider for Linq to XSD,
has a 3.5 profile dependency
Hi,
To get your patches ready, this page would be a good starter.
http://mono-project.com/Contributing
I'm not sure what you meant on XmlSchemaType.BaseXmlSchemaType, but
those 3 members are implemented AFAIK.
Atsushi Eno
(2011/01/20 3:05), Bob Watson wrote:
Hello,
I’m developing
You might want to read this:
http://nirajrules.wordpress.com/2009/08/03/mtom-vs-streaming-vs-compression-%E2%80%93-large-attachments-over-wcf/
Atsushi Eno
(2011/01/15 22:19), Joel Caner wrote:
Thank you for your reply. Can you tell me if there is another way to send
large data/file then?..can
Not sure where the actual error occurs without stack trace, but 2.6 is
too old
for WCF to try anyways.
And Mtom is almost untested so it will cause any kind of problem (never
expected that there are actually people who use it).
Atsushi Eno
(2011/01/14 23:37), joelcaner wrote:
I am having
Ah, thanks, forgot about that ReleaseInstanceMode property ;-)
Atsushi Eno
(2011/01/11 19:17), Adar Wesley wrote:
Hi,
I was reading this thread and just by chance was reading up on WCF
Services Session instantiation and release today.
I thought the following links might be useful to clear
starters.
Atsushi Eno
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Hi again,
To my understanding, a session (ISession) is usually member of
ISessionChannel types, its lifecycle is bound to the channel, and we
indeed have such implementation in TcpDuplexSessionChannel.
If we got to know .NET behaviors we'll do the same in WCF ;)
Atsushi Eno
(2011/01/10 0:03
Thanks, your patch is applied in git master.
Atsushi Eno
(2011/01/03 2:41), Michel Foucault wrote:
Hi,
I'm trying to use svcutils (mono 2.8.1).
Since it fails with metadataUrl I've try assemblyPath method.
It doesn't work either
I've modified the code of mcs/tools/svcutil/Driver.cs
an answer.
Atsushi Eno
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
visit bug
#660424 tomorrow.
Atsushi Eno
(2010/12/19 4:19), CodeSlinger wrote:
Just a thought - if using WCF, the client and server could be in different
zones so why would you want anything other than UTC time to be passed around
in the first place which is always what should be stored and only
The mono-olive mailing list was shut down to migrate to here (I posted
about that as the last message there), so you are welcome here in the
right place now to discuss WF or Messaging :)
Atsushi Eno
(2010/12/14 11:52), Travis Smith wrote:
Miguel-
I figured contributing to an area I work
hacking as an
alternative effort.
Atsushi Eno
(2010/12/14 12:07), Travis Smith wrote:
http://mono-project.com/Workflow could use to be updated on the
location of the mailing list then.
What's the status of these sections? Are there portions that need love
that I could look at digging
Please file a bug (C# is much better).
Atsushi Eno
(2010/12/07 16:14), Chakotey STME wrote:
This problem still exists.
Does anyone have an idea?
-- Forwarded message --
From: Chakotey STMEchakoteys...@gmail.com
Date: 2010/11/30
Subject: Problem with WCF and IEnumerable
.
Atsushi Eno
(2010/11/29 18:55), Chakotey STME wrote:
Hi,
I have a problem with this code under mono 2.6:
Dim xsdMarkup As XDocument =
XDocument.Load(/home/stefan/xml/PluginConfigSchema.xsd)
Dim schemas As XmlSchemaSet = New XmlSchemaSet()
schemas.Add
from moma.
Atsushi Eno
(2010/11/29 19:17), Atsushi Eno wrote:
You can't use moma report result to assume it *must* work if it does not
report anything. It is explicitly stated on the first page when you ran
moma:
http://www.mono-project.com/Using_MoMA_Guide
It won't report things
Ahh, ok. No worries then.
BTW I mistyped: XDocument.Validate() is *now* implemented in git master ;)
Atsushi Eno
(2010/11/30 0:23), Chakotey STME wrote:
Thats correct.
The Mono analyzer says that it won't work.
Sorry.
Maybe I checked note the correct project with the mono analyzer
to the
SayHi (not SayHi2) and hence blah isn't involved, so, is it really what
you intended?
Code:
Shared library: http://pastebin.com/WSfiaj63
Server: http://pastebin.com/veJ9JubX
Client: http://pastebin.com/jniuHsiz
Can you please file a bug on bugzilla and attach them?
Thanks,
Atsushi Eno
I can't give a definite answer, but at least the throttling limitation
will go away ;-)
Atsushi Eno
(2010/11/22 15:41), Chakotey STME wrote:
hello,
thanks for your answer.
That's correct. I am using mono 2.6
If I change to mono 2.8 - will die clients run parallel?
chakoteystme
2010/11
1 - 100 of 890 matches
Mail list logo