[Mono-list] API Documentation
Hi, I wanted to created API documentation from the comments which I have written in the code something like in Java we do using Javadoc. Do we have any tool in mono which does the same? Regards, Sunil. ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] Certmgr
Where will certmgr stor the trust store on WindowsXP for a User logged in as Administrator? Also , does Mono.Security.dll will validate a servercertificate if the server trust root is stored in The trusted Root Certification Authorities store using MS .NET certmgr utility? Sunil. ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
RE: [Mono-list] Mono trust stire location
Is there any API's available in mono to Read the trust root certificates from a Trusted root store created using certmgr? Sunil. Sebastien Pouliot [EMAIL PROTECTED] 4/8/2004 3:42:07 PM Sunil, Is it possible that we can speicfy the location where we want to create the trust store. Maybe ;-) It's all depend on *why* the location needs to be specified, like: - changing the directory name isn't hard (e.g. ~/.mono/certificates/... or something more fd.org-friendly); - having a different directory structure per user requires to add configuration files (and tools/documentation/...) but makes it harder to change the implementation later. For example a later Mono release could use an implementation not based on a file system (a database, a directory, a smartcard ...). Problem is that if/when application depends on a specific directory then we have conflict problems. That's why I said it's better to use certmgr to do the job. Note that the same pattern holds true for key pairs and the GAC - you shouldn't depend on their location but use the supplied tools to manipulate them. In this case (trusted certificates being used for SSL/TLS) it's also possible to add application specific code (in the validation callback) to check for untrusted certificates and then search another (application specific) location for roots (but that would be in addition to the existing roots). Sebastien Pouliot http://pages.infinit.net/ctech/poupou.html -Original Message- From: Sunil Kumar [mailto:[EMAIL PROTECTED] Sent: 8 avril 2004 16:57 To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: [Mono-list] Mono trust stire location Hi Sebastie, Is it possible that we can speicfy the location where we want to create the trust store. SUnil. Sebastien Pouliot [EMAIL PROTECTED] 4/8/2004 2:50:22 PM Hello Sunil, All user certificate stores are located under ~/.mono/certs/ The trusted store is ~/.mono/certs/Trust/ But this could change between release, so it's better to use certmgr to add/remove certificates. Sebastien Pouliot http://pages.infinit.net/ctech/poupou.html -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Sunil Kumar Sent: 8 avril 2004 16:42 To: [EMAIL PROTECTED] Subject: [Mono-list] Mono trust stire location Hi , Does anyone Knows the location of the mono trust store? i.e when I add a certificate using certmgr add -c Trust TrustRootCertificate where does my TrustRootCertificate gets added. Regards, Sunil. ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
RE: [Mono-list] Mono trust stire location
Hi Sebastie, Is it possible that we can speicfy the location where we want to create the trust store. SUnil. Sebastien Pouliot [EMAIL PROTECTED] 4/8/2004 2:50:22 PM Hello Sunil, All user certificate stores are located under ~/.mono/certs/ The trusted store is ~/.mono/certs/Trust/ But this could change between release, so it's better to use certmgr to add/remove certificates. Sebastien Pouliot http://pages.infinit.net/ctech/poupou.html -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Sunil Kumar Sent: 8 avril 2004 16:42 To: [EMAIL PROTECTED] Subject: [Mono-list] Mono trust stire location Hi , Does anyone Knows the location of the mono trust store? i.e when I add a certificate using certmgr add -c Trust TrustRootCertificate where does my TrustRootCertificate gets added. Regards, Sunil. ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
RE: [Mono-list] Re: Mono.Security
Sebastin,
I wasn't able to file bug report since we have some problem with HTTP services here
right now. I am attaching all the details with this mail only.
a.Windows, MS.NET runtime/class library
I got following Result after runnign the test program:-
CERTIFICATE:
Format: X509
Name: OU=Organizational CA, O=SUNILK-TREE
Issuing CA: OU=Organizational CA, O=SUNILK-TREE
Key Algorithm: 1.2.840.113549.1.1.1
Serial Number: 27120202EBE69CCC8556EA84716043D2F8CC2981B8B2A54D75094975
EAD0EC111C02
Key Alogrithm Parameters: 0500
Public Key: 3082010A0282010100A320C0566649D81D91EED21CD2569F9A71DA94A69
F7FCB256AB27A94A8864E2DAC5DADD4D74D8206909F19AB48A5F6E5845BECB6EE9546C29B8CA6745
AA0147F6DF56560E997B6DD2B280868AB5090D154F945829F22203615430CC9EC84D8F80E1F41702
0F2BCC3C9A4FDA94A04E7146EA1532611CB35B831F329E7FAAD4E66406FC8BFBF5F49CB5D11232B6
F3B4823F2A1E61F906D862D5FBBDCB3E95B2C8E39F04EC7EF4C42A2BC90731415188FAF8160148BC
6195762023AA25E325D9F90BB1801056D7B0D6C0029520F9E0C4233CB8E785962CF01A512DC25F38
868529E904EE3CD7440606C9866EBF0C13239333DD0533902542C61330D5EFAEDB996DF020301000
1
b.Windows, Mono runtime/class library
Since I haven't configured Mono on a windows box, I wasn't able to complete this
scenario.
c.Linux, Mono runtime/class library
I got following Result after runnign the test program:-
Unhandled Exception: System.Security.Cryptography.CryptographicException: Input data
cannot be coded as a valid certificate.
#0: 0x00349 throw in Mono.Security.X509.X509Certificate::Parse ([O:0x81b3aa0] )
#1: 0xe callvirt in Mono.Security.X509.X509Certificate::.ctor ([O:0x81b3aa0] )
#2: 0xe newobj in
System.Security.Cryptography.X509Certificates.X509Certificate::.ctor ([O:0x81b3aa0]
[1] )
#3: 0x3 call in
System.Security.Cryptography.X509Certificates.X509Certificate::.ctor ([O:0x81b3aa0] )
#4: 0x00030 newobj in
System.Security.Cryptography.X509Certificates.X509Certificate::CreateFromCertFile
([O:0x81abe70] )
#5: 0x3 call in .X509CertTester::Main ([O:0x8146f78] )
I have attached the Test program and certificate with this mail.
Regards,
Sunil
Sébastien Pouliot [EMAIL PROTECTED] 12/11/2003 7:20:33 PM
Sunil,
Ok it's getting stranger. I seems in sync with CVS and can't duplicate the
problem with the 2 candidate certificates I got (the one from
https://www.nldap.com and the one that Carlos sent me).
Can you try, with your certificate, the following code ...
using System;
using System.Security.Cryptography.X509Certificates;
class X509Tester {
[STAThread]
static void Main (string[] args)
{
X509Certificate x = X509Certificate.CreateFromCertFile (args[0]);
Console.WriteLine (x.ToString (true));
}
}
... on
a. Windows, MS.NET runtime/class library
b. Windows, Mono runtime/class library
c. Linux, Mono runtime/class library
and fill a bug report with the results and the certificate used. I'll look
into this ASAP.
Thanks
Sebastien Pouliot
Security Architect, Motus Technologies, http://www.motus.com
work: [EMAIL PROTECTED]
home: [EMAIL PROTECTED]
blog: http://pages.infinit.net/ctech/poupou.html
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Sunil Kumar
Sent: 11 décembre 2003 00:22
To: Matt Ryan; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; Parameswaran S
Subject: Re: [Mono-list] Re: Mono.Security
Looks like there is some problem with the Mono's
System.Security.Cryptography.X509Certificates.X509Certificate class.
I tried to create a certicate object using CreateFromCertFile method and a
ASN1 DER encoded certicate file ,but its throwing exception. I did the same
thing on windows using MS .NET with the same certificate file and its
working. Below is the code snippet:-
try{
X509Certificate cert = X509Certificate.CreateFromCertFile(certfile);
}Catch(Exception e)
{
Console.WriteLine(Error: + e.Message);
return;
}
On linux it throws following exception:-
Error: Input data cannot be coded as a valid certificate.
Regards
Sunil.
Carlos Guzmán Álvarez [EMAIL PROTECTED] 12/9/2003 9:56:53 PM
Hello:
There is also an internet-accessible eDirectory server that (I'm told)
anyone can use for testing purposes, at http://www.ndlap.com.
Thanks very much.
I have made a little test trying to negotiate the Handshake protocol
against the www.nldap.com using .NET 1.0 and the SSL/TLS libraries
sources from my local tree, with success, i will try to make the same
test using mono, and update the mono cvs sources as soon as possible.
--
Best regards
Carlos Guzmán Álvarez
Vigo-Spain
___
Mono-list maillist - [EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/mono-list
___
Mono-list maillist - [EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Re: Mono.Security
Yes. Here is a ssldump output captured using ssldump on linux: New TCP connection #1: rahul.blr.novell.com(60060) - sunilk.blr.novell.com(636) 1 1 0.0152 (0.0152) CS Handshake ClientHello Version 3.1 cipher suites Unknown value 0x35 Unknown value 0x2f TLS_RSA_WITH_3DES_EDE_CBC_SHA TLS_RSA_WITH_DES_CBC_SHA TLS_RSA_WITH_RC4_128_SHA TLS_RSA_WITH_RC4_128_MD5 compression methods NULL 1 2 0.0281 (0.0129) SC Handshake ServerHello Version 3.1 session_id[32]= e6 85 b6 94 1e 9a eb 39 43 2d 47 2d b6 8b 61 1b 1f ba 29 b3 df cf 90 ba 5e 43 95 20 ed 50 10 5b cipherSuite Unknown value 0x35 compressionMethod NULL 1 3 0.0282 (0.) CS Handshake ClientHello Version 3.1 cipher suites Unknown value 0x35 Unknown value 0x2f TLS_RSA_WITH_3DES_EDE_CBC_SHA TLS_RSA_WITH_DES_CBC_SHA TLS_RSA_WITH_RC4_128_SHA TLS_RSA_WITH_RC4_128_MD5 compression methods NULL 1 4 0.0286 (0.0003) SC Handshake Certificate 1 5 0.0286 (0.) SC Handshake ServerHelloDone 1 6 0.0464 (0.0177) SC Handshake ServerHello Version 3.1 session_id[32]= 7f 79 13 d4 4b 89 4d eb b4 9c 6e 76 cb ba 84 5f a6 98 30 69 02 08 84 24 c8 ed 1f 87 80 a2 60 5a cipherSuite Unknown value 0x35 compressionMethod NULL 1 7 0.0466 (0.0002) SC Handshake Certificate 1 8 0.0466 (0.) SC Handshake ServerHelloDone Regards Sunil Carlos Guzmán Álvarez [EMAIL PROTECTED] 12/6/2003 5:19:33 PM Hello: Do you have any idea of what might be the cause of problem? Your LDAP server requires client authentication ?? -- Best regards Carlos Guzmán Álvarez Vigo-Spain ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] Re: Mono.Security
Carlos,
I am using SslClientStream class in my client program to talk to an LDAP server
over SSL. But the handshake is not completing properly and the client hangs in
between. I wrote the following lines of code to do this:-
//certfile is a ASN1 DER encoded
selfsigned certificate file.
X509Certificate Cert =
X509Certificate.CreateFromCertFile(certfile);
Socket sock = new Socket (
AddressFamily.InterNetwork,
SocketType.Stream,ProtocolType.IP);
IPAddress hostadd =
Dns.Resolve(host).AddressList[0];
IPEndPoint ephost = new
IPEndPoint(hostadd,port);
sock.Connect(ephost);
NetworkStream nstream = new
NetworkStream(sock,true);
SslClientStream sslstream = new
SslClientStream(nstream,host,true,
Mono.Security.Protocol.Tls.SecurityProtocolType.Default,
new X509CertificateCollection(new
X509Certificate[]{Cert}));
System.IO.Stream input= sslstream;
System.IO.Stream output=sslstream;
I am using input and output stream to read and write on the socket. The certificate
looks like okay since i have used the same certificate to talk to the ldap server over
ssl using Openssl libraries.
Here is a log from the server which may give you some clue of what is happening on the
server side:-
LDAP: Monitor 0x508 received signal l
LDAP: Monitor 0x508 initiating TLS handshake on connection 0x9176cc0
LDAP: (164.99.145.182:51124)(0x:0x02) DoTLSHandshake on connection 0x9176cc0
LDAP: (164.99.145.182:51124)(0x:0x02) Connection 0x9176cc0 sending read
blocked signal r to monitor 0x508
LDAP: Monitor 0x508 received signal r
LDAP: Monitor 0x508 signaling read blocked connection 0x9176cc0
LDAP: (164.99.145.182:51124)(0x:0x02) Connection 0x9176cc0 sending read
blocked signal r to monitor 0x508
LDAP: Monitor 0x508 received signal r
In case of OpenSSL library ( When the handshake completes properly ) following log is
generated:-
LDAP: New TLS connection 0x9176cc0 from 164.99.159.221:2943, monitor = 0x508,
index = 1
LDAP: Connector sending signal l to monitor 0x508 for new connection 0x9176cc0
LDAP: Monitor 0x508 received signal l
LDAP: Monitor 0x508 initiating TLS handshake on connection 0x9176cc0
LDAP: (164.99.159.221:2943)(0x:0x02) DoTLSHandshake on connection 0x9176cc0
LDAP: (164.99.159.221:2943)(0x:0x02) Connection 0x9176cc0 sending read blocked
signal r to monitor 0x508
LDAP: Monitor 0x508 received signal r
LDAP: Monitor 0x508 signaling read blocked connection 0x9176cc0
LDAP: (164.99.159.221:2943)(0x:0x02) Completed TLS handshake on connection
0x9176cc0
LDAP: (164.99.159.221:2943)(0x:0x02) Connection 0x9176cc0 sending handshake
signal h to monitor 0x508
LDAP: Monitor 0x508 received signal h
Do you have any idea of what might be the cause of problem?
Regards
Sunil.
Carlos Guzmán Álvarez [EMAIL PROTECTED] 12/5/2003 6:08:23 PM
Hello:
I was trying to use some of the classes provided in
Mono.Security.Protocol.Tls like TlsSocket,TlsSession etc.
I have removed it two weeks ago, and replaced it with an SslClientStream
implementation similar to the existent in the .NET 1.2 documentation.
Can anyone tell me about the status of these classes.
They are under development, and at this moment they have some limitations:
- Client only.
- No real server certificate validation (only the certificate date and
target host are validated now).
- No client authentication.
The supported Cipher Suites for TLS protocol are:
- TLS_RSA_WITH_AES_256_CBC_SHA
- TLS_RSA_WITH_AES_128_CBC_SHA
- TLS_RSA_WITH_3DES_EDE_CBC_SHA
- TLS_RSA_WITH_DES_CBC_SHA
- TLS_RSA_WITH_RC4_128_SHA
- TLS_RSA_WITH_RC4_128_MD5
And for SSL3 are:
- SSL_RSA_WITH_3DES_EDE_CBC_SHA
- SSL_RSA_WITH_DES_CBC_SHA
- SSL_RSA_WITH_RC4_128_SHA
- SSL_RSA_WITH_RC4_128_MD5
I was busy this week and have no time for work on it but i have plans
for restart the work next week.
BTW I was looking for a way to create SSL/TLS
[Mono-list] Mono.Security
Hi I was trying to use some of the classes provided in Mono.Security.Protocol.Tls like TlsSocket,TlsSession etc. But looks like these classes are not included in the Mono.Security.dll . Can anyone tell me about the status of these classes. BTW I was looking for a way to create SSL/TLS socket, Is there any other way thru which I can do without using TlsSocket class? Regards Sunil ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] Re: Problems with Mono's System.DirectoryServices
Rhys, SearchResultCollection and SearchResult classes are still not completed and they are in progress ,thats why I haven't included them in the System.DirectoryServices.dll build. That is the reason these files are not appearing in System.DirectoryServices.dll . I will be completing them soon. Regards, Sunil Rhys Weatherley [EMAIL PROTECTED] 11/28/2003 9:41:47 AM Hi Sunil, I've been trying to get Mono's System.DirectoryServices to compile with Portable.NET, and I've found a couple of problems. First, the constructor for SearchResultCollection is declared as internal PropertyCollection() (i.e. it has the wrong name). The SearchResult class refers to a type called Properties (line 45) that does not appear to exist anywhere that I could find. When I exclude these two classes from the build, it compiles fine. I note that the System.DirectoryServices.dll.sources file does not appear to contain those two classes. Was it a deliberate choice that those two classes were omitted from the build, or merely an oversight? Cheers, Rhys. ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] Re: Question for Sunil
Yes,You will be able to connect to Any other LDAP server ,even Active Directory. Regards, -Sunil santiago gavilanes [EMAIL PROTECTED] 11/22/2003 9:15:33 PM Dear Sunil, I download your code for conection to an Novel LDAP Server, and I have a doubt, my question is, your code serve for connect to another kind of LDAP server, for example Active Directory. Warm Greetings Santiago Gavilanes Quito - Ecuador _ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] .NET C# LDAP Library
Try this URL, http://forge.novell.com/modules/xfmod/project/?ldapcsharp I have uploaded all the files and the Binaries under the Latest file release Section, So now you don't need to worry about checking out the sources form CVS. Regards, Sunil Kumar [EMAIL PROTECTED] Novell Bangalore www.novell.com ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] Mono on embedded Linux
Hi, I was just curious to know whether any work has been done on running Mono on embedded devices ? Regards, -Sunil ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] .NET C# LDAP Libraray.
Hi, Recently we have completed a implementation of .NET C# LDAP libraries and checked in the sources at forge.novell.com CVS. Anyone can access the sources at:- http://forge.novell.com/modules/xfmod/cvs/cvsbrowse.php/ldapcsharp/CsharpLDAP LDAP Libraries for C# enables you to write applications that access, manage, and update information stored in Novell eDirectory* or other LDAP-aware directories. The above libraries can be build on both Windows and Linux platform. I have included the build script for both of these platform. If anyone faces any difficulty they can post it to the mailing list at novell forge or can contact me at [EMAIL PROTECTED] Regards, Sunil Kumar Novell,Bangalore [EMAIL PROTECTED] ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
RE: [Mono-list] .NET C# LDAP Libraray.
Jason, Thanks for all your feedback and comments.Since this was the intial release and we expected to receive a lots of feedback and comments so that we can make improvemets in the C# LDAP Libraries. My response to your comments below:- Q1. Just to add my 2 cents...I know while it was easier to run the Java Language Conversion Assistant on the existing Novell Java LDAP source code, what you end up with leaves a lot to be desired. I see a number of places where the converter mangled parameter names. Response:- Let me know exactly where have you seen such kind of mangled parameter names? Q2. Also, there's a plethora of static const integers exposed in a number of classes, namely LDAPConnection and LDAPException. To truly comply with C# conventions, these should be replaced with standard enumerations. Response:- The static const integers you are talking about are constants which will be used by application using C# LDAP libararies and the LDAP Libraray both . Constants like : public const int SCOPE_BASE = 0; public const int SCOPE_ONE = 1; public const int SCOPE_SUB = 2; public const int LDAP_V3 = 3; public const int DEFAULT_PORT = 389; public const int DEFAULT_SSL_PORT = 636; Instead of application defining these constants themselves everywhere, we have included this as part of the Library itself . I donn see any harm in defining these constants and exposing them outside, Insted I see it will be lot more useful in most of the cases. e.g see a sample example of C# apllication which will be using this:- LDAPConnection ldapconn; intldapVersion = LDAPConnection.LDAP_V3; intldapPort = LDAPConnection.DEFAULT_PORT; // connect to the server ldapconn.connect( ldapHost, ldapPort ); // bind to the server ldapconn.bind( ldapVersion, loginDN, password ); Q3. In a lot of ways, it's a tough call as whether it's best to stick with the existing API used in the Java code when porting it to C#. On one hand, if you just mirror the Java API in C#, it's much easier to port existing Java client classes over to C#. But I don't think that should be the only goal when porting com.novell.ldap.*. I think it's important to make the C# API as true to Microsoft's guidelines as possible. Classes like LDAPSearchResults should implement the appropriate collection interfaces so foreach and indexers can be used, etc. Response:- As far as using collection interfaces in LDAPSearchResults and other classes are considered. Instaed of implementing those interfaces we have used already implemented collection objects. e.g In LDAPSearchResults class ,If you see we have used System.Collections.ArrayList at many places like for storing searchresults and references:- private System.Collections.ArrayList references; // Search Result References private System.Collections.ArrayList entries; // Search entries private System.Collections.ArrayList referralConn = null; // Referral Connections Regards, Sunil Kumar Novell,bangalore www.novell.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ben Maurer Sent: Thursday, November 13, 2003 4:18 PM To: Matt Ryan Cc: [EMAIL PROTECTED] Subject: Re: [Mono-list] .NET C# LDAP Libraray. Hello Matt, I was taking a quick look at your sources, they look great! One thing I did notice, however, is that you guys are naming your classes things like: LDAPFoobar However, in c# the guidelines for when you have a situation like that: 1) if the first part is two letters, keep it uppercase (eg, IPAddress) 2) otherwise, only have the first letter uppercase (XmlTextWriter, LdapFoobar) Right now, you are early enough in the design process that this can easily be fixed with a tad of grep magic (no need to worry about history-- there is nothing to loose). I would highly advise running FxCop (i realize it only runs in Windows, some day I think we should make something like it for mono). Better to catch stuff like this early when you dont have to take compat, cvs history etc into account. -- Ben ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] .NET C# LDAP Libraray.
Ben, Thanks a lot for pointing out for sticking to C# naming Guidelines . We are looking into it, what best we can do about it. Regards, Sunil Kumar Novell,bangalore Ben Maurer [EMAIL PROTECTED] 11/14/2003 5:47:36 AM Hello Matt, I was taking a quick look at your sources, they look great! One thing I did notice, however, is that you guys are naming your classes things like: LDAPFoobar However, in c# the guidelines for when you have a situation like that: 1) if the first part is two letters, keep it uppercase (eg, IPAddress) 2) otherwise, only have the first letter uppercase (XmlTextWriter, LdapFoobar) Right now, you are early enough in the design process that this can easily be fixed with a tad of grep magic (no need to worry about history-- there is nothing to loose). I would highly advise running FxCop (i realize it only runs in Windows, some day I think we should make something like it for mono). Better to catch stuff like this early when you dont have to take compat, cvs history etc into account. -- Ben ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
