Hi,
As part of filling .NET 2.0 API, I am wondering how and what we need to do
secure remoting support (introduced in 2.0), namely HttpChannel, TcpChannel
and IpcChannel. (I'd like to put my disclaimer - am far from familiar
with those
remoting stuff, so don't hit me if I am misunderstanding the
2007/10/1, Sanghyeon Seo [EMAIL PROTECTED]:
Shouldn't = be ^= instead? The current implementation doesn't return
True for m.IsPublic even after m.IsPublic = true is executed.
Should be = ~masked, instead of = masked, like other properties?
--
Seo Sanghyeon
Hey Tyler,
If you need this urgently, please provide a fix.
If not - it will be somewhere in my todo list and will be fixed in a couple of
weeks.
Regards,
Konstantin Triger
-Original Message-
From: [EMAIL PROTECTED] [mailto:mono-devel-list-
[EMAIL PROTECTED] On Behalf Of R. Tyler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 1, 2007, at 1:42 AM, Konstantin Triger wrote:
Hey Tyler,
If you need this urgently, please provide a fix.
If not - it will be somewhere in my todo list and will be fixed in
a couple of weeks.
Would you recommend just adding another
Hey,
On 10/1/07, Sanghyeon Seo [EMAIL PROTECTED] wrote:
Should be = ~masked, instead of = masked, like other properties?
Yeah, good catch. This is a regression I introduced when I wrote the
Is* property generator. The good news is that now, I only have to
change the code generator to change all
On Mon, 2007-10-01 at 17:00 +0900, AtsushiEno wrote:
Hi,
As part of filling .NET 2.0 API, I am wondering how and what we need to do
secure remoting support (introduced in 2.0), namely HttpChannel, TcpChannel
and IpcChannel. (I'd like to put my disclaimer - am far from familiar
with those
Hello,
I would like to use sockets with mono on mipsel.
This is a sample code which works well on PC:
using System;
using System.IO;
using System.Net.Sockets;
class ClientDemo {
public static void Main(string[] args) {
string serverIp = x.x.x.x;
Hi,
The patch that changed the generic type definition to be the same instance
of the fully open instantiation introduced a small issue in the encoding of
types. This issue is quite subtle and gmcs produces it only on rare
situations.
If you use, for example: ILGenerator::Emit
Try/catch does not seem the best way to do it, and unfortunately I don't have
time now to look into the code.
Temporary you may yet do this workaround and compile your own version, so
unblock yourself until the fix is available.
Regards,
Konstantin Triger
-Original Message-
From: R.
Hi Kosta and Tyler,
Having worked on this code with Kosta and following this thread a couple of
questions come to my mind.
1. Are there any other types that need special care, besides Nullable? How
about generic types?
As far as I remember, we don't have any tests with generics. Are we
Hi Atsushi,
AtsushiEno wrote:
Hi,
As part of filling .NET 2.0 API, I am wondering how and what we need to do
secure remoting support (introduced in 2.0), namely HttpChannel, TcpChannel
and IpcChannel. (I'd like to put my disclaimer - am far from familiar
with those
remoting stuff, so
Hey Adar,
It's nice to get your 2 cents :-)
1. Are there any other types that need special care, besides Nullable? How
about generic types?
As far as I remember, we don't have any tests with generics. Are we
missing anything else?
Don't think, since this is a binary
On Oct 1, 2007, at 10:47 AM, Konstantin Triger wrote:
2. I was trying to think of a good strategy for implementing this,
and havn't made up my mind yet.
I agree with Kosta that the try, catch approach is not the
best way. I think something a bit more fine grained
should be used.
13 matches
Mail list logo
