as a dev platform and work from
there; GTK# sounds like a good place to start.
-Original Message-
From: Martin Hinks [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 21, 2005 2:16 AM
To: Kirk Marple
Cc: mono-list@lists.ximian.com
Subject: Re: [Mono-list] Building a cross-platform networked client
i have a need to
build a new client application, which does basically four things... talks via
Windows Sockets (async i/o)to a remote server over both TCP and UDP, does
file I/O, exposes UI for picking files on the client and showing log/status
messages, and it does interop to a native 3rd
Speaking of WSE2, is there a current status on any WSE2 implementations?
I'm only really looking for these namespaces, not the security/encryption
stuff:
using Microsoft.Web.Services2;
using Microsoft.Web.Services2.Messaging;
using Microsoft.Web.Services2.Addressing;
I have a set of web
I'd talked to
Miguel once about this, and it sounds like Microsoft's Web Services Enhancements
(WSE2) aren't on the Mono roadmap, and that Indigo would be the focal point down
the road.
We have a
service-oriented application that we'll be porting to Mono in the next 6-9
months.
What are
It makes sense if both languages (C# and HSPL) compiled to IL, and were both
processed by the CLR.
You'd have to make separate assemblies which referenced each other, you
couldn't do it inline in the same class.
Look at how IronPython compiles to IL, but it usable from any other .NET
assembly.
The real issue here is about rounding to integers, and enums are ints by
default, so really the numbers are equivalent to:
Positivo = 0,
Negativo = 1,
Neutro = 1
Which would make sense by what you see printed out.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
