Re: [Mono-dev] Mono 1.1.9 broken DataGrid
On Wed, 2005-09-14 at 00:50 +0300, Slava Petrenko wrote: Hi all, It seems to me mono 1.1.9 has a broken support for DataGrid's tag asp:BoundColumn. Now property Visible of that tag doesn't affect on column's visibility, it stays visible independently from a value of Visible property. Mono 1.1.9, SuSe Pro 9.3, rpms are taken from mono-project.com Can you try http://primates.ximian.com/~gonzalo/System.Web.dll.gz ? It has all the current fixes from HEAD. 'gunzip' it and run 'gacutil -i System.Web.dll'. -Gonzalo ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Big MCS Problem
I've updated my mono from svn this morning... There's apparently a problem with Mcs : when i try to compile a simple project with : mcs /home/hubert/Projects/test/Main.cs i get : error CS2007: Unrecognized command-line option: `/home/hubert/Projects/test/Main.cs' Compilation failed: 1 error(s), 0 warnings if I do mcs ./Main.cs it works... mcs ./Projects/test/Main.cs works mcs ~/Projects/test/Main.cs don't works... It used to work yesterday...!!! Thanks ___Ce message et les éventuels documents joints peuvent contenir des informations confidentielles.Au cas où il ne vous serait pas destiné, nous vous remercions de bien vouloir le supprimer et en aviser immédiatement l'expéditeur. Toute utilisation de ce message non conforme à sa destination, toute diffusion ou publication, totale ou partielle et quel qu'en soit le moyen est formellement interdite.Les communications sur internet n'étant pas sécurisées, l'intégrité de ce message n'est pas assurée et la société émettrice ne peut être tenue pour responsable de son contenu. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Big MCS Problem
Le mercredi 28 septembre 2005 11:11 +0200, Hubert FONGARNAND a crit: I've updated my mono from svn this morning... There's apparently a problem with Mcs : when i try to compile a simple project with : mcs /home/hubert/Projects/test/Main.cs i get : error CS2007: Unrecognized command-line option: `/home/hubert/Projects/test/Main.cs' Compilation failed: 1 error(s), 0 warnings if I do mcs ./Main.cs it works... mcs ./Projects/test/Main.cs works mcs ~/Projects/test/Main.cs don't works... It used to work yesterday...!!! mcs -- ~/Projects/test/Main.cs works ... but it used to works without -- yesterday Thanks ___ Ce message et les ventuels documents joints peuvent contenir des informations confidentielles. Au cas o il ne vous serait pas destin, nous vous remercions de bien vouloir le supprimer et en aviser immdiatement l'expditeur. Toute utilisation de ce message non conforme sa destination, toute diffusion ou publication, totale ou partielle et quel qu'en soit le moyen est formellement interdite. Les communications sur internet n'tant pas scurises, l'intgrit de ce message n'est pas assure et la socit mettrice ne peut tre tenue pour responsable de son contenu. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___Ce message et les éventuels documents joints peuvent contenir des informations confidentielles.Au cas où il ne vous serait pas destiné, nous vous remercions de bien vouloir le supprimer et en aviser immédiatement l'expéditeur. Toute utilisation de ce message non conforme à sa destination, toute diffusion ou publication, totale ou partielle et quel qu'en soit le moyen est formellement interdite.Les communications sur internet n'étant pas sécurisées, l'intégrité de ce message n'est pas assurée et la société émettrice ne peut être tenue pour responsable de son contenu. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Big MCS Problem
Le mercredi 28 septembre 2005 11:11 +0200, Hubert FONGARNAND a crit : I've filled a bug report : http://bugzilla.ximian.com/show_bug.cgi?id=76255 I've updated my mono from svn this morning... There's apparently a problem with Mcs : when i try to compile a simple project with : mcs /home/hubert/Projects/test/Main.cs i get : error CS2007: Unrecognized command-line option: `/home/hubert/Projects/test/Main.cs' Compilation failed: 1 error(s), 0 warnings if I do mcs ./Main.cs it works... mcs ./Projects/test/Main.cs works mcs ~/Projects/test/Main.cs don't works... It used to work yesterday...!!! Thanks ___ Ce message et les ventuels documents joints peuvent contenir des informations confidentielles. Au cas o il ne vous serait pas destin, nous vous remercions de bien vouloir le supprimer et en aviser immdiatement l'expditeur. Toute utilisation de ce message non conforme sa destination, toute diffusion ou publication, totale ou partielle et quel qu'en soit le moyen est formellement interdite. Les communications sur internet n'tant pas scurises, l'intgrit de ce message n'est pas assure et la socit mettrice ne peut tre tenue pour responsable de son contenu. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___Ce message et les éventuels documents joints peuvent contenir des informations confidentielles.Au cas où il ne vous serait pas destiné, nous vous remercions de bien vouloir le supprimer et en aviser immédiatement l'expéditeur. Toute utilisation de ce message non conforme à sa destination, toute diffusion ou publication, totale ou partielle et quel qu'en soit le moyen est formellement interdite.Les communications sur internet n'étant pas sécurisées, l'intégrité de ce message n'est pas assurée et la société émettrice ne peut être tenue pour responsable de son contenu. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Big MCS Problem
Maybe we had better revert driver.cs in r50836 ... it would be somethat complicated to differentiate file not found and incrrect compiler options. Marek, any good ideas? Atsushi Eno Hubert FONGARNAND wrote: I've updated my mono from svn this morning... There's apparently a problem with Mcs : when i try to compile a simple project with : mcs /home/hubert/Projects/test/Main.cs i get : error CS2007: Unrecognized command-line option: `/home/hubert/Projects/test/Main.cs' Compilation failed: 1 error(s), 0 warnings if I do mcs ./Main.cs it works... mcs ./Projects/test/Main.cs works mcs ~/Projects/test/Main.cs don't works... It used to work yesterday...!!! Thanks ___ Ce message et les 騅entuels documents joints peuvent contenir des informations confidentielles. Au cas o・il ne vous serait pas destin・ nous vous remercions de bien vouloir le supprimer et en aviser imm馘iatement l'exp馘iteur. Toute utilisation de ce message non conforme ・sa destination, toute diffusion ou publication, totale ou partielle et quel qu'en soit le moyen est formellement interdite. Les communications sur internet n'騁ant pas s馗uris馥s, l'int馮rit・de ce message n'est pas assur馥 et la soci騁・駑ettrice ne peut 黎re tenue pour responsable de son contenu. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] HTTPS - MS .NET Client - Linux Mono Server - Interoperability
Hello Sebastien, Things seems to go better for me, but I still have problems with my server side (Mono) authentication and decryption. I now use a PKCS#12 file on my server side. Se below for more info. On Tue, 2005-09-27 at 14:47, Sebastien Pouliot wrote: Hello Yngve, On Tue, 2005-27-09 at 12:01 +0200, Yngve Zackrisson wrote: On Mon, 2005-09-26 at 18:10, Sebastien Pouliot wrote: Hello Yngve, On Mon, 2005-26-09 at 16:26 +0200, Yngve Zackrisson wrote: Hi. I (like Martin Hinks) have problems with the interoperability Martin wasn't talking about HTTPS/SSL/TLS in it's latest email (unless I missed one). The subject was about password based key derivation. Martin wrote (snippet): Which .NET Encryption classes does Mono support that will work cross platform? eg. I encrypt on Windows using .NET and the Linux class can decrypt the same file and visa versa. As I understand, he is asking what (symmetric?) encryption / decryption algorithms that is supported by both platforms. Right?. yes, your problems are about interop but not related to encryption (formats PVK/PKCS12 and certificate stores ;-). between a MS .NET HTTPS client and a Linux (Fedora Core 3) Mono server. What I like to do is a HTTPS call from my MS .NET client to the Linux Mono server. TEST1: mutual - My first test is based on the Mono mutual authentication example: http://svn.myrealbox.com/source/trunk/mcs/class/Mono.Security/Test/tools/mutual/ The difference is that I create the certificates with openSSL and run the client on Win32 and MS .NET. On my client I run: $ mutual.exe me292 TLS client16-cert.p12 xx (where me292 is my server DNS and xx is the p12 password) I then get: ... CertificateValidation CERTIFICATE: Error(s) #-2146762487 Meaning untrusted root, for my server certificate. I have created a trusted CA cert using openssl x509 with the -trustout option. What is the problem?. Must I have the .p12 in the Windows store? If you're using Mono.Security (like the mutual test program) then you must install the root certificate into the *Mono* certificate store (even if you're executing the sample with the MS runtime). OK. I will try to do that ... (I will try to read in on what to install ... ) You can also use MS' HttpWebRequest for mutual authentication. In this case (MS runtime + MS HttpWebRequest) you'll need to install the root certificate into the *Windows* certificate store. or that ... . After the printout of: ... PrivateKeySelection ... PrivateKeySelection(1) no more happens on the client side. That test program wasn't made to output anything useful. It only sends an Hello string to the server. Keep in mind that 'mutual', like others, is a *test* tool and not sample code. On the server side I run: $ openssl s_server -www -cert server16-cert.pem -key server16-key.pem -verify client16-cert.pem -CAfile cacert16t.pem and get: verify depth is 0 Using default temp DH parameters Using default temp ECDH parameters ACCEPT bad gethostbyaddr depth=1 /C=SE/L=Stockholm/O=Test Company AB/OU=IT Department - CA/CN=me292 validity return:1 depth=0 /C=SE/L=Sundsvall/O=Customer Company 16 AB/CN=Mirsad validity return:1 AFAIK, A Hello should be written on the server. An Hello is sent to the server (so the handshake starts) but it doesn't mean the server will output it on the console. TEST2: server - I have also made test with the Mono server example. http://svn.myrealbox.com/source/trunk/mcs/class/Mono.Security/Test/tools/server/ Here I have had problems generating the private key of type .pvk. In openssl there is an new option: openssl rsa -in server16-key.pem -pvk-strong -out server16-key.strong.pvk -pvk-weak -pvk-none And I have tried all of them, But none have helped. I never used OpenSSL to generate PVK files. Either use makecert to generate your certificates or look at my blog to use the PKCS#12 version of the server test tool. OK. I will look at your blog and try to skip the PVK format in favor for PKCS#12. On the Mono server I run: $ mono --debug --verbose MonoSslHttpServer.exe I get a : System.Security.Cryptography.CryptographicException on the Mono server side in : (Mono.Security.Protocol.Tls.Handshake.HandshakeMessage:.ctor (...) Mono.Security.Protocol.Tls.Handshake.Server.TlsClientCertificate.ProcessAsTls1 () Can this
[Mono-dev] Default code page used by mcs
Hi, I committed a patch that added /codepage to our mcs command line that I missed for a long time. Now we don't have to specify the encoding we use in mcs as we pass it on the command line. So mcs can be modifed to use Encoding.Default as the default code page. I think this is what most developers need as they edit their files using the system code page and this is the behaviour of csc.exe as well. Kornél - Original Message - From: Atsushi Eno [EMAIL PROTECTED] To: Kornél Pál [EMAIL PROTECTED] Cc: mono-devel mailing list mono-devel-list@lists.ximian.com Sent: Wednesday, August 31, 2005 6:35 AM Subject: Re: [Mono-dev] mcs patch to say goodbye to SeekableStreamReader Hi, I tried your patch with ComIStreamMarshaler.cs and used -codepage:65001. It worked as expected but it fails with SVN head. The expected behaviour is to compile without errors so you patch solves the bug. Yep - now the fixed patch is going. I've done some tests with files readed as UTF-8 but containing invalid byte sequences even with BOM and it worked as expected. Cool. Thanks for checking it :-) I think the patch should be ported to gmcs as well. I'll ask Martin later. I think we should return using Encoding.Default as the default encoding in mcs but should comfigure mcs using -codepage:28591 -codepage:1252 in mcs/build to use that encoding. Maybe after 1.1.9 as Miguel suggested? I don't think the default encoding problem would happen only to mcs. Atsushi Eno ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] [PATCH] Reworked ImageList (updated)
Hi, I relocated braces to match Coding Guidelines and committed the patch as r50935. Line endings are set to native in SVN so I don't think it should be changed. Kornél - Original Message - From: Jackson Harper [EMAIL PROTECTED] To: Kornél Pál [EMAIL PROTECTED] Cc: mono-devel-list@lists.ximian.com Sent: Wednesday, September 28, 2005 6:37 AM Subject: Re: [Mono-dev] [PATCH] Reworked ImageList (updated) Hi this patch looks ok to me except for the line endings and some of the coding style. Feel free to commit after fixing these. Thanks! Jackson On Tue, 2005-09-27 at 14:10 +0200, Kornél Pál wrote: If you get some exceptions please post the stack trace as well. Kornél - Original Message - From: Kornél Pál [EMAIL PROTECTED] To: Jackson Harper [EMAIL PROTECTED] Cc: mono-devel-list@lists.ximian.com Sent: Tuesday, September 27, 2005 10:29 AM Subject: Re: [Mono-dev] [PATCH] Reworked ImageList (updated) Hi, Hey Kornel, thanks very much for working on this. After applying this patch and updating and rebuilding my libgdiplus (saw you had a patch there) the winforms/treeview sample is crashing for me. If you mean libgdiplus on saw you had a patch there you missed something becasue I don't hack on libgdiplus. I only tested the code on Windows, it works. I don't use graphical Linux so I haven't got a test environment for libgdiplus. That's why I asked to do some tests.:) I did not try this sample previously but now I tried on Windows and works for me without problems. If there really is a problem with libgdiplus it may be a difference in LockBits behaviour. Please try the safe and the unsafe versions as well. I expect performance loss when using GetPixel and SetPixel because it does a lot of unnecessary things. If the safe version works there is something wrong with the unsafe version. May be my code and may be libgdiplus. Kornél - Original Message - From: Jackson Harper [EMAIL PROTECTED] To: Kornél Pál [EMAIL PROTECTED] Cc: mono-devel-list@lists.ximian.com Sent: Tuesday, September 27, 2005 9:10 AM Subject: Re: [Mono-dev] [PATCH] Reworked ImageList (updated) On Mon, 2005-09-26 at 23:30 +0200, Kornél Pál wrote: Hi, I updated the proposed path: Created an IndexedColorDepths nested class that delays palette initialization until it is needed and added an array that contains sqare values for color distances. This should speed up ReduceColorDepth. Hey Kornel, thanks very much for working on this. After applying this patch and updating and rebuilding my libgdiplus (saw you had a patch there) the winforms/treeview sample is crashing for me. Have you tried running this test? Thanks! Jackson Kornél - Original Message - From: Kornél Pál [EMAIL PROTECTED] To: mono-devel-list@lists.ximian.com Sent: Monday, September 26, 2005 2:14 PM Subject: [Mono-dev] [PATCH] Reworked ImageList Hi, I modified nearly everything in ImageList implementation to make it compatible wint MS.NET. For more information look at the source code. The biggest change is that it uses 32-bit ARGB Images anyway to can provide transparency and can return the expected 32-bit Images. To provide compatibility with MS.NET it reduces colors and ignores non-zero alpha levels according to the ColorDepth property. Please do some tests with the new implementation with MS GDI+ as well as Mono libgdiplus. Please review and approve the patch. Kornél ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Big MCS Problem
Hello, Fixed in SVN. Hubert, could you retest it ? Thanks, Marek Maybe we had better revert driver.cs in r50836 ... it would be somethat complicated to differentiate file not found and incrrect compiler options. Marek, any good ideas? Atsushi Eno Hubert FONGARNAND wrote: I've updated my mono from svn this morning... There's apparently a problem with Mcs : when i try to compile a simple project with : mcs /home/hubert/Projects/test/Main.cs i get : error CS2007: Unrecognized command-line option: `/home/hubert/Projects/test/Main.cs' Compilation failed: 1 error(s), 0 warnings if I do mcs ./Main.cs it works... mcs ./Projects/test/Main.cs works mcs ~/Projects/test/Main.cs don't works... It used to work yesterday...!!! Thanks ___ Ce message et les 騅entuels documents joints peuvent contenir des informations confidentielles. Au cas o・il ne vous serait pas destin・ nous vous remercions de bien vouloir le supprimer et en aviser imm馘iatement l'exp馘iteur. Toute utilisation de ce message non conforme ・sa destination, toute diffusion ou publication, totale ou partielle et quel qu'en soit le moyen est formellement interdite. Les communications sur internet n'騁ant pas s馗uris馥s, l'int馮rit・de ce message n'est pas assur馥 et la soci騁・駑ettrice ne peut 黎re tenue pour responsable de son contenu. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] System.Web fails to build
Hi, The error is the following: System.Web.UI.HtmlControls/HtmlHead.cs(162,55): error CS0122: `System.Web.UI.CssStyleCollection.BagToString()' is inaccessible due to its protection level Kornél ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] System.Web fails to build
The error is the following: System.Web.UI.HtmlControls/HtmlHead.cs(162,55): error CS0122: `System.Web.UI.CssStyleCollection.BagToString()' is inaccessible due to its protection level Got that as well under Linux. I'm on revision 50934. Rob ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] MapViewOfFile - I think there is a bug
Hi, According to MSDN, MapViewOfFile should be LPVOID MapViewOfFile( HANDLE hFileMappingObject, DWORD dwDesiredAccess, DWORD dwFileOffsetHigh, DWORD dwFileOffsetLow, SIZE_T dwNumberOfBytesToMap ); I have some code which looks like this dataView = MapViewOfFile(dataMap, FILE_MAP_WRITE, 0, 0, (UIntPtr)BUFFERLEN); This won't compile (can't convert from int to System.UIntPtr). As I understand it though, if I remove (UIntPtr) from before BUFFERLEN, this should then happily compile. However, it doesn't. dataMap is an IntPtr Is this something that needs to go into Bugzilla? TTFN Paul -- Logic, my dear Zoe, is merely the ability to be wrong with authority - Dr Who ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Big MCS Problem
Le mercredi 28 septembre 2005 11:32 +0100, Marek Safar a crit: Hello, Fixed in SVN. Hubert, could you retest it ? Ooops Mono doesn't compile anymore: MONO_PATH=../../class/lib/default:$MONO_PATH /home/hubert/mono/mono/runtime/mono-wrapper ../../class/lib/default/mcs.exe /codepage:28591 -d:NET_1_1 -d:ONLY_1_1 -debug /noconfig -unsafe -nowarn:612,649 -r:mscorlib.dll -r:System.dll -r:System.Drawing.dll -r:System.Data.dll -r:System.Xml.dll -r:System.EnterpriseServices.dll /resource:resources/WebUIValidation.js -target:library -out:../../class/lib/default/System.Web.dll @System.Web.dll.sources error CS2001: Source file `/resource:resources/WebUIValidation.js' could not be found does it comes from your changes? Thanks, Marek Maybe we had better revert driver.cs in r50836 ... it would be somethat complicated to differentiate file not found and incrrect compiler options. Marek, any good ideas? Atsushi Eno Hubert FONGARNAND wrote: I've updated my mono from svn this morning... There's apparently a problem with Mcs : when i try to compile a simple project with : mcs /home/hubert/Projects/test/Main.cs i get : error CS2007: Unrecognized command-line option: `/home/hubert/Projects/test/Main.cs' Compilation failed: 1 error(s), 0 warnings if I do mcs ./Main.cs it works... mcs ./Projects/test/Main.cs works mcs ~/Projects/test/Main.cs don't works... It used to work yesterday...!!! Thanks ___ Ce message et les entuels documents joints peuvent contenir des informations confidentielles. Au cas oil ne vous serait pas destin nous vous remercions de bien vouloir le supprimer et en aviser immiatement l'expiteur. Toute utilisation de ce message non conforme sa destination, toute diffusion ou publication, totale ou partielle et quel qu'en soit le moyen est formellement interdite. Les communications sur internet n'ant pas suriss, l'intritde ce message n'est pas assur et la societtrice ne peut re tenue pour responsable de son contenu. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___Ce message et les éventuels documents joints peuvent contenir des informations confidentielles.Au cas où il ne vous serait pas destiné, nous vous remercions de bien vouloir le supprimer et en aviser immédiatement l'expéditeur. Toute utilisation de ce message non conforme à sa destination, toute diffusion ou publication, totale ou partielle et quel qu'en soit le moyen est formellement interdite.Les communications sur internet n'étant pas sécurisées, l'intégrité de ce message n'est pas assurée et la société émettrice ne peut être tenue pour responsable de son contenu. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] MapViewOfFile - I think there is a bug
Paul F. Johnson wrote: Hi, According to MSDN, MapViewOfFile should be LPVOID MapViewOfFile( HANDLE hFileMappingObject, DWORD dwDesiredAccess, DWORD dwFileOffsetHigh, DWORD dwFileOffsetLow, SIZE_T dwNumberOfBytesToMap ); I have some code which looks like this dataView = MapViewOfFile(dataMap, FILE_MAP_WRITE, 0, 0, (UIntPtr)BUFFERLEN); Are you using that declaration? http://www.pinvoke.net/default.aspx/kernel32.MapViewOfFile It has a bug. This is the correct DllImport: [DllImport(kernel32.dll)] static extern IntPtr MapViewOfFile( IntPtr hFileMappingObject, uint dwDesiredAccess, uint dwFileOffsetHigh, uint dwFileOffsetLow, uint dwNumberOfBytesToMap ); dataView = MapViewOfFile(dataMap, FILE_MAP_WRITE, 0, 0, (uint) BUFFERLEN); Rob ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Big MCS Problem
Le mercredi 28 septembre 2005 14:03 +0200, Hubert FONGARNAND a crit: Le mercredi 28 septembre 2005 11:32 +0100, Marek Safar a crit: Hello, Fixed in SVN. Hubert, could you retest it ? Ooops Mono doesn't compile anymore: MONO_PATH=../../class/lib/default:$MONO_PATH /home/hubert/mono/mono/runtime/mono-wrapper ../../class/lib/default/mcs.exe /codepage:28591 -d:NET_1_1 -d:ONLY_1_1 -debug /noconfig -unsafe -nowarn:612,649 -r:mscorlib.dll -r:System.dll -r:System.Drawing.dll -r:System.Data.dll -r:System.Xml.dll -r:System.EnterpriseServices.dll /resource:resources/WebUIValidation.js -target:library -out:../../class/lib/default/System.Web.dll @System.Web.dll.sources error CS2001: Source file `/resource:resources/WebUIValidation.js' could not be found does it comes from your changes? I think mcs see /resource:resources/WebUIValidation.js as a file to compile... (because there's a slash before resource) Thanks, Marek Maybe we had better revert driver.cs in r50836 ... it would be somethat complicated to differentiate file not found and incrrect compiler options. Marek, any good ideas? Atsushi Eno Hubert FONGARNAND wrote: I've updated my mono from svn this morning... There's apparently a problem with Mcs : when i try to compile a simple project with : mcs /home/hubert/Projects/test/Main.cs i get : error CS2007: Unrecognized command-line option: `/home/hubert/Projects/test/Main.cs' Compilation failed: 1 error(s), 0 warnings if I do mcs ./Main.cs it works... mcs ./Projects/test/Main.cs works mcs ~/Projects/test/Main.cs don't works... It used to work yesterday...!!! Thanks ___ Ce message et les entuels documents joints peuvent contenir des informations confidentielles. Au cas oil ne vous serait pas destin nous vous remercions de bien vouloir le supprimer et en aviser immiatement l'expiteur. Toute utilisation de ce message non conforme sa destination, toute diffusion ou publication, totale ou partielle et quel qu'en soit le moyen est formellement interdite. Les communications sur internet n'ant pas suriss, l'intritde ce message n'est pas assur et la societtrice ne peut re tenue pour responsable de son contenu. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Ce message et les ventuels documents joints peuvent contenir des informations confidentielles. Au cas o_ il ne vous serait pas destin, nous vous remercions de bien vouloir le supprimer et en aviser imm diatement l'expditeur. Toute utilisation de ce message non conforme / sa destination, toute diffusion ou publication, totale ou partielle et quel qu'en soit le moyen est formellement interdite. Les communications sur internet n'tant pas s curises, l'inttgrit de ce message n'est pas assurge et la socite mettrice ne peut atre tenue pour responsable de son contenu. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___Ce message et les éventuels documents joints peuvent contenir des informations confidentielles.Au cas où il ne vous serait pas destiné, nous vous remercions de bien vouloir le supprimer et en aviser immédiatement l'expéditeur. Toute utilisation de ce message non conforme à sa destination, toute diffusion ou publication, totale ou partielle et quel qu'en soit le moyen est formellement interdite.Les communications sur internet n'étant pas sécurisées, l'intégrité de ce message n'est pas assurée et la société émettrice ne peut être tenue pour responsable de son contenu. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] HTTPS - MS .NET Client - Linux Mono Server - Interoperability
Hello Yngve, On Wed, 2005-28-09 at 11:42 +0200, Yngve Zackrisson wrote: Hello Sebastien, Things seems to go better for me, great :) but I still have problems with my server side (Mono) authentication and decryption. I now use a PKCS#12 file on my server side. Se below for more info. ... For the authentication probably an custom channel have to be used. I don't see why this would be required (for client-side certificates) as the authentication is part of the protocol itself. OK. Maybe I do not need this. I just read some articles/samples at msdn about .NET Remoting Authentication and those articles suggested a custom channel. (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/remsspi.asp and http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/remsec.asp and http://msdn.microsoft.com/msdnmag/issues/03/06/NETRemoting/default.aspx ). The examples was about other forms of authentication (Kerberos etc) and encryption so these references may not apply?. I don't think you'll need that unless you have some additional (more than the client certificate) authentication data. ... We intend to sign both our server and client certificates with our own root CA. There is already unix scripts for this using openssl, hence the preference for openssl. Ok, so you'll have a single root CA signing both your server and client certificate. This root certificate will have to be in the Mono's Trusted store on the server. ... Binary formating shall be used. Was there a specific reason for using https and a binary formatting ? If I understand correctly you'll be supplying your own server software ? so you _could_ use SSL without using HTTP(S). Firewalls. Ok, so it's a port issue (not a protocol issue). The server is in house and should be a Linux one. We use latest version on Mono (1.1.9). Is the server software using Mono.Security.dll ? or is it using (vanilla or custom) XSP ? Currently Mono.Security.dll. The intention is to run the services as Windows services in Mono, if that works. Remember that if the Mono service runs under another identity then the trusted root certificate must either be (a) in that user Trust store or (b) in the machine Trust store. I have not got into this yet, so we might have to shift. Currently I host the remote objects in a console application. The clients are Win32 clients using MS .NET (v1.0 or v1.1 with SP enough to handle the certificates). The clients are not connected all the time, but only during initialization and zip file transfer. The installation on the client side should be as simple as possible for the clients. Hence, preferable PKCS#12 client certificates should be used and it should preferable be stored only in one file or in one store (Windows store). You'll either have to : (a) write your own glue (p/invokes) if you want Mono.Security.dll to co-exists with Windows certificate stores; (b) completely skip Mono.Security.dll on the client side. I.e. once installed correctly the MS runtime should be able to find the private key matching the certificate you use in HttpWebRequest. OK. I have gone for (b). First I set the ServicePointManager.CertificatePolicy to an custom class to detect any certificate errors. Then I use a DLL from Mentalis (Org.Mentalis.Security.dll) to extract the client certificates from the Windows store, and then select on the IssuerName. Once that done, I use the Mentalis Certificate.ToX509() method to convert to X509Certificate(s). (See: http://www.mentalis.org/ and http://www.mentalis.org/soft/projects/certificates/ ). Last I create the HttpWebRequest, Add the X509Certificate(s) the requests ClientCertificates and set the WebResponse to the HttpWebRequest.GetResponse(). It seems to work (on the client side). No more Untrusted root, since the certificates is in the Windows store now. That's ok. Other options for extracting the certificate(s) from the Windows store seems to be: Using CryptoAPI calls: http://support.microsoft.com/default.aspx?scid=kb;en-us;895971 Using a CAPICOM wrapper: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dncapi/html/netcryptoapi.asp Using WS-Security with the Web Service Developement Kit: http://www.codeproject.com/csharp/cryptography.asp Yes, they are the other options. As a first step, I would like to have the HttpWebRequest and HttpWebResponse to work toghther with HTTPS. MS version of HttpWebRequest.ClientCertificates will try to find private keys (in it's store) associated with the certificate(s) you're supplying. Note that you may have problems if the client application runs on another identity (e.g. services runs as SYSTEM). OK. (Seems no problem for me). Then, on the server side, you'll get this certificate
[Fwd: Re: [Mono-dev] HTTPS - MS .NET Client - Linux Mono Server - Interoperability]
---BeginMessage--- On Wed, 2005-09-28 at 14:12, Sebastien Pouliot wrote: Hello Yngve, On Wed, 2005-28-09 at 11:42 +0200, Yngve Zackrisson wrote: Hello Sebastien, Things seems to go better for me, great :) but I still have problems with my server side (Mono) authentication and decryption. I now use a PKCS#12 file on my server side. Se below for more info. ... For the authentication probably an custom channel have to be used. I don't see why this would be required (for client-side certificates) as the authentication is part of the protocol itself. OK. Maybe I do not need this. I just read some articles/samples at msdn about .NET Remoting Authentication and those articles suggested a custom channel. (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/remsspi.asp and http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/remsec.asp and http://msdn.microsoft.com/msdnmag/issues/03/06/NETRemoting/default.aspx ). The examples was about other forms of authentication (Kerberos etc) and encryption so these references may not apply?. I don't think you'll need that unless you have some additional (more than the client certificate) authentication data. ... We intend to sign both our server and client certificates with our own root CA. There is already unix scripts for this using openssl, hence the preference for openssl. Ok, so you'll have a single root CA signing both your server and client certificate. This root certificate will have to be in the Mono's Trusted store on the server. ... Binary formating shall be used. Was there a specific reason for using https and a binary formatting ? If I understand correctly you'll be supplying your own server software ? so you _could_ use SSL without using HTTP(S). Firewalls. Ok, so it's a port issue (not a protocol issue). The server is in house and should be a Linux one. We use latest version on Mono (1.1.9). Is the server software using Mono.Security.dll ? or is it using (vanilla or custom) XSP ? Currently Mono.Security.dll. The intention is to run the services as Windows services in Mono, if that works. Remember that if the Mono service runs under another identity then the trusted root certificate must either be (a) in that user Trust store or (b) in the machine Trust store. I have not got into this yet, so we might have to shift. Currently I host the remote objects in a console application. The clients are Win32 clients using MS .NET (v1.0 or v1.1 with SP enough to handle the certificates). The clients are not connected all the time, but only during initialization and zip file transfer. The installation on the client side should be as simple as possible for the clients. Hence, preferable PKCS#12 client certificates should be used and it should preferable be stored only in one file or in one store (Windows store). You'll either have to : (a) write your own glue (p/invokes) if you want Mono.Security.dll to co-exists with Windows certificate stores; (b) completely skip Mono.Security.dll on the client side. I.e. once installed correctly the MS runtime should be able to find the private key matching the certificate you use in HttpWebRequest. OK. I have gone for (b). First I set the ServicePointManager.CertificatePolicy to an custom class to detect any certificate errors. Then I use a DLL from Mentalis (Org.Mentalis.Security.dll) to extract the client certificates from the Windows store, and then select on the IssuerName. Once that done, I use the Mentalis Certificate.ToX509() method to convert to X509Certificate(s). (See: http://www.mentalis.org/ and http://www.mentalis.org/soft/projects/certificates/ ). Last I create the HttpWebRequest, Add the X509Certificate(s) the requests ClientCertificates and set the WebResponse to the HttpWebRequest.GetResponse(). It seems to work (on the client side). No more Untrusted root, since the certificates is in the Windows store now. That's ok. Other options for extracting the certificate(s) from the Windows store seems to be: Using CryptoAPI calls: http://support.microsoft.com/default.aspx?scid=kb;en-us;895971 Using a CAPICOM wrapper: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dncapi/html/netcryptoapi.asp Using WS-Security with the Web Service Developement Kit: http://www.codeproject.com/csharp/cryptography.asp Yes, they are the other options. As a first step, I would like to have the HttpWebRequest and HttpWebResponse to work toghther with HTTPS. MS version of HttpWebRequest.ClientCertificates will try to find private keys (in it's store) associated with the certificate(s) you're supplying.
Re: [Fwd: Re: [Mono-dev] HTTPS - MS .NET Client - Linux Mono Server - Interoperability]
Hello Yngve, On Wed, 2005-28-09 at 14:54 +0200, Yngve Zackrisson wrote: ... Should I add a PKCS#12 cert file to the Mono Store (Machine store) (mono /.../certmgr.exe -add -c -m Trust server16-cert.p12) or add only the CA to the trust store (mono /.../certmgr.exe -add -c -m Trust cacert16t.cer) or anything else to get rid of this error message?. It must be either the user or machine Trusted store (otherwise you'll get a trust error). OK. But witch certificate is preferable to add to the store?: a) mono /.../certmgr.exe -add -c -m Trust server16-cert.p12 or b) mono /.../certmgr.exe -add -c -m Trust cacert16t.cer Trust is transitive, i.e. the server will be trusted if it's signer is trusted. So only the self-signed root certificate needs to be added to the Trust store. I also have a question about the trust of the root CA certificate. The cacert16t.cer above I have created with the following openssl commands: ... $ openssl x509 -in cacert16.pem -trustout -setalias TrustedRootCert -out cacert16t.pem $ openssl x509 -inform PEM -in cacert16t.pem -outform DER -out cacert16t.cer is the first openssl command necessary since the signed client and server certificates, or at least its root CA, should be added to the Windows/Mono (Trust) store?. Currently I use the cacert16t.pem file as -certfile when creating the client and server PKCS#12 files - with the openssl pkcs12 command. Will the cacert16.pem file be enough? I honestly don't know (without reading the man page myself). I don't use openssl much (for x.509 related stuff) because (a) it's formats aren't the one natively used in .NET and (b) I try to dogfood my own tools ;-) ... Yesterday (after your previous email) I tried to use the MS runtime for client certificate without success (same failure). Somehow MS does something different* because the server can't verify the signature (and it's not a key and/or decryption problem - the hash value is different but the padding is ok). Using IE (with the SSL2 client hello) to do the same turned out another problem, very similar to the bug #76254 reported today. [*] The client certificate testing is done with wget/openssl (linux/cygwin) - which sadly doesn't seems enough :( Please let me know if you come up with some solution. I have been working with the HTTPS communication for some 2 months now, and my boss is eager to get an solution :-). Please open a bugzilla issue on bugzilla.ximian.com (e.g. SSL client certificate doesn't work with IE.). That way you'll get notified as soon as (and whenever) I change the bug status. -- Sebastien Pouliot email: [EMAIL PROTECTED] blog: http://pages.infinit.net/ctech/ ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Big MCS Problem
Hello, Le mercredi 28 septembre 2005 à 14:03 +0200, Hubert FONGARNAND a écrit : Le mercredi 28 septembre 2005 à 11:32 +0100, Marek Safar a écrit : Hello, Fixed in SVN. Hubert, could you retest it ? Ooops Mono doesn't compile anymore: MONO_PATH=../../class/lib/default:$MONO_PATH /home/hubert/mono/mono/runtime/mono-wrapper ../../class/lib/default/mcs.exe /codepage:28591 -d:NET_1_1 -d:ONLY_1_1 -debug /noconfig -unsafe -nowarn:612,649 -r:mscorlib.dll -r:System.dll -r:System.Drawing.dll -r:System.Data.dll -r:System.Xml.dll -r:System.EnterpriseServices.dll /resource:resources/WebUIValidation.js -target:library -out:../../class/lib/default/System.Web.dll @System.Web.dll.sources error CS2001: Source file `/resource:resources/WebUIValidation.js' could not be found does it comes from your changes? I think mcs see /resource:resources/WebUIValidation.js as a file to compile... (because there's a slash before resource) It's compilable now. Regards, Marek Maybe we had better revert driver.cs in r50836 ... it would be somethat complicated to differentiate file not found and incrrect compiler options. Marek, any good ideas? Atsushi Eno Hubert FONGARNAND wrote: I've updated my mono from svn this morning... There's apparently a problem with Mcs : when i try to compile a simple project with : mcs /home/hubert/Projects/test/Main.cs i get : error CS2007: Unrecognized command-line option: `/home/hubert/Projects/test/Main.cs' Compilation failed: 1 error(s), 0 warnings if I do mcs ./Main.cs it works... mcs ./Projects/test/Main.cs works mcs ~/Projects/test/Main.cs don't works... It used to work yesterday...!!! Thanks ___ Ce message et les 騅entuels documents joints peuvent contenir des informations confidentielles. Au cas o・il ne vous serait pas destin・ nous vous remercions de bien vouloir le supprimer et en aviser imm馘iatement l'exp馘iteur. Toute utilisation de ce message non conforme ・sa destination, toute diffusion ou publication, totale ou partielle et quel qu'en soit le moyen est formellement interdite. Les communications sur internet n'騁ant pas s馗uris馥s, l'int馮rit・de ce message n'est pas assur馥 et la soci騁・駑ettrice ne peut 黎re tenue pour responsable de son contenu. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com mailto:Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Ce message et les ventuels documents joints peuvent contenir des informations confidentielles. Au cas o_ il ne vous serait pas destin, nous vous remercions de bien vouloir le supprimer et en aviser imm diatement l'expditeur. Toute utilisation de ce message non conforme / sa destination, toute diffusion ou publication, totale ou partielle et quel qu'en soit le moyen est formellement interdite. Les communications sur internet n'tant pas s curises, l'inttgrit de ce message n'est pas assurge et la socite mettrice ne peut atre tenue pour responsable de son contenu. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com mailto:Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Ce message et les �ventuels documents joints peuvent contenir des informations confidentielles. Au cas o� il ne vous serait pas destin�, nous vous remercions de bien vouloir le supprimer et en aviser imm�diatement l'exp�diteur. Toute utilisation de ce message non conforme � sa destination, toute diffusion ou publication, totale ou partielle et quel qu'en soit le moyen est formellement interdite. Les communications sur internet n'�tant pas s�curis�es, l'int�grit� de ce message n'est pas assur�e et la soci�t� �mettrice ne peut �tre tenue pour responsable de son contenu. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Big MCS Problem
Hi, I think mcs see /resource:resources/WebUIValidation.js as a file to compile... (because there's a slash before resource) It's compilable now. Nope. Can't get mcs to compile from source... System.Web.UI.WebControls/BoundField.cs(111,25): warning CS0114: `System.Web.UI.WebControls.BoundField.HeaderText' hides inherited member `System.Web.UI.WebControls.DataControlField.HeaderText'. To make the current member override that implementation, add the override keyword. Otherwise add the new keyword System.Web.UI.WebControls/DataControlField.cs(308,4):: `System.Web.UI.WebControls.DataControlField.HeaderText.set' (name of symbol related to previous warning System.Web.UI.WebControls/RoleGroupCollection.cs(111,15): warning CS0114: `System.Web.UI.WebControls.RoleGroupCollection.OnValidate(object)' hides inherited member `System.Collections.CollectionBase.OnValidate(object)'. To make the current member override that implementation, add the override keyword. Otherwise add the new keyword /home/paul/mcs/class/lib/net_2_0/mscorlib.dll: `System.Collections.CollectionBase.OnValidate(object)' (name of symbol related to previous warning System.Web.Compilation/AspComponentFoundry.cs(43,63): warning CS0618: `System.Collections.CaseInsensitiveHashCodeProvider' is obsolete: `Please use StringComparer instead.' System.Web.Compilation/AspComponentFoundry.cs(153,63): warning CS0618: `System.Collections.CaseInsensitiveHashCodeProvider' is obsolete: `Please use StringComparer instead.' System.Web.Compilation/Directive.cs(80,47): warning CS0618: `System.Collections.CaseInsensitiveHashCodeProvider' is obsolete: `Please use StringComparer instead.' System.Web.Compilation/Directive.cs(80,4): warning CS0618: `System.Collections.CaseInsensitiveHashCodeProvider' is obsolete: `Please use StringComparer instead.' System.Web.Compilation/TagAttributes.cs(55,63): warning CS0618: `System.Collections.CaseInsensitiveHashCodeProvider' is obsolete: `Please use StringComparer instead.' System.Web.Compilation/TagAttributes.cs(162,63): warning CS0618: `System.Collections.CaseInsensitiveHashCodeProvider' is obsolete: `Please use StringComparer instead.' System.Web.Configuration/CompilationConfiguration.cs(81,22): warning CS0618: `System.Web.HttpContext.GetConfig(string)' is obsolete: `see GetSection' System.Web.Configuration/CompilerCollection.cs(45,63): warning CS0618: `System.Collections.CaseInsensitiveHashCodeProvider' is obsolete: `Please use StringComparer instead.' System.Web.Configuration/GlobalizationConfiguration.cs(62,27): warning CS0618: `System.Web.HttpContext.GetAppConfig(string)' is obsolete: `see WebConfigurationManager' System.Web.Configuration/GlobalizationConfiguration.cs(65,23): warning CS0618: `System.Web.HttpContext.GetConfig(string)' is obsolete: `see GetSection' System.Web.Configuration/HttpRuntimeConfig.cs(73,21): warning CS0618: `System.Web.HttpContext.GetConfig(string)' is obsolete: `see GetSection' System.Web.Configuration/PagesConfiguration.cs(72,22): warning CS0618: `System.Web.HttpContext.GetConfig(string)' is obsolete: `see GetSection' System.Web/HttpApplication.cs(147,50): warning CS0618: `System.Web.HttpContext.GetAppConfig(string)' is obsolete: `see WebConfigurationManager' System.Web/HttpApplication.cs(994,91): warning CS0618: `System.Web.HttpContext.GetAppConfig(string)' is obsolete: `see WebConfigurationManager' System.Web/HttpApplication.cs(1088,43): warning CS0618: `System.Web.HttpContext.GetConfig(string)' is obsolete: `see GetSection' System.Web/HttpCacheVaryByHeaders.cs(72,59): warning CS0618: `System.Collections.CaseInsensitiveHashCodeProvider' is obsolete: `Please use StringComparer instead.' System.Web/HttpCacheVaryByParams.cs(47,58): warning CS0618: `System.Collections.CaseInsensitiveHashCodeProvider' is obsolete: `Please use StringComparer instead.' System.Web/HttpContext.cs(169,33): warning CS0618: `System.Web.HttpContext.GetConfig(string)' is obsolete: `see GetSection' System.Web/HttpContext.cs(454,9): warning CS0618: `System.Web.HttpContext.GetConfig(string)' is obsolete: `see GetSection' System.Web/HttpRequest.cs(582,63): warning CS0618: `System.Web.HttpContext.GetAppConfig(string)' is obsolete: `see WebConfigurationManager' System.Web/HttpRequest.cs(1325,9): warning CS0219: The variable `bl' is assigned but its value is never used System.Web/HttpRequest.cs(1324,9): warning CS0219: The variable `ll' is assigned but its value is never used System.Web.Mail/MailMessageWrapper.cs(54,18): warning CS0618: `System.Web.Mail.MailMessage' is obsolete: `The recommended alternative is System.Net.Mail.MailMessage.' System.Web.Mail/MailMessageWrapper.cs(55,38): warning CS0618: `System.Web.Mail.MailMessage' is obsolete: `The recommended alternative is System.Net.Mail.MailMessage.' System.Web.Mail/MailMessageWrapper.cs(59,18): warning CS0618: `System.Web.Mail.MailMessage' is obsolete: `The recommended alternative is System.Net.Mail.MailMessage.' System.Web.Mail/MailMessageWrapper.cs(60,45): warning CS0618:
Re: [Mono-dev] Big MCS Problem
Paul F. Johnson wrote: Hi, I think mcs see /resource:resources/WebUIValidation.js as a file to compile... (because there's a slash before resource) It's compilable now. Nope. Can't get mcs to compile from source... This is not the compiler. System.Web.UI.HtmlControls/HtmlHead.cs(162,55): error CS0122: `System.Web.UI.CssStyleCollection.BagToString()' is inaccessible due to its protection level It's an error in System.Web.UI.HtmlControls/HtmlHead.cs that broke the build. Rob ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Compiling System.Web with CSC
Hi, Miguel. The option of playing with ilasm/ildasm will mess out completely the debug information. PDB uses the tokens from the DLL to identify the class, method, etc. The tokens will be completely messed up by this exercise. I will look at the output of ildasm to analyze better the .Net 2.0 dependencies to see if we can come up with some kind of hack for using the CSC 2.0 compiler. Eyal. On Tue, 27 Sep 2005, Miguel de Icaza wrote: Date: Tue, 27 Sep 2005 18:12:03 -0400 From: Miguel de Icaza [EMAIL PROTECTED] To: Eyal Alaluf [EMAIL PROTECTED] Cc: [EMAIL PROTECTED], Noam Lampert [EMAIL PROTECTED], Philippe Cohen [EMAIL PROTECTED], mono-devel-list@lists.ximian.com Subject: Re: [Mono-dev] Compiling System.Web with CSC Hello, I think it is a bad idea, specially considering that it means that we have to write more and debug more code than we otherwise would. There is an easy solution that I mentioned before which is that we can add support to mcs to generate pdb files instead. MCS already uses the API to generate debugging information, the only difference is that it consumes a Mono-specific API instead of the cross-platform API. We did not use the cross-platform API in the past because we did not have information on how to use it, but now IronPython has code that shows how to use it. Alternatively to upgrading mcs, you can use csc, and then do: ildasm /out:output file.dll sed script ilasm output.il Where the sed script would remove the couple of new keywords on ildasm and replace the 2.x references with 1.x references. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] MapViewOfFile - I think there is a bug
Robert, you are wrong, when you state that uint should be used for SIZE_T. SIZE_T is an unsigned integer with the size of void* that is UIntPtr. Paul, you are right, this is a bug in mcs, I reported it: http://bugzilla.ximian.com/show_bug.cgi?id=76256 If you declare dwNumberOfBytesToMap as IntPtr and cast BUFFERLEN to IntPtr it will compile on mcs as well, and you will get the same result. Kornél - Original Message - From: Robert Jordan [EMAIL PROTECTED] To: mono-devel-list@lists.ximian.com Sent: Wednesday, September 28, 2005 2:07 PM Subject: Re: [Mono-dev] MapViewOfFile - I think there is a bug Paul F. Johnson wrote: Hi, According to MSDN, MapViewOfFile should be LPVOID MapViewOfFile( HANDLE hFileMappingObject, DWORD dwDesiredAccess, DWORD dwFileOffsetHigh, DWORD dwFileOffsetLow, SIZE_T dwNumberOfBytesToMap ); I have some code which looks like this dataView = MapViewOfFile(dataMap, FILE_MAP_WRITE, 0, 0, (UIntPtr)BUFFERLEN); Are you using that declaration? http://www.pinvoke.net/default.aspx/kernel32.MapViewOfFile It has a bug. This is the correct DllImport: [DllImport(kernel32.dll)] static extern IntPtr MapViewOfFile( IntPtr hFileMappingObject, uint dwDesiredAccess, uint dwFileOffsetHigh, uint dwFileOffsetLow, uint dwNumberOfBytesToMap ); dataView = MapViewOfFile(dataMap, FILE_MAP_WRITE, 0, 0, (uint) BUFFERLEN); Rob ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Compiling System.Web with CSC
Hi, MS ildasm is able to extract information from PDB files to IL code. If there is a PDB file it includes variable names in IL code an with /linenum switch it will emit line number information as well. MS ilasm generates a PDB with /debug switch that will contain the names of local variables and line numbers. And I think all the other usual symbols. Kornél - Original Message - From: Eyal Alaluf [EMAIL PROTECTED] To: Miguel de Icaza [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; mono-devel-list@lists.ximian.com; Philippe Cohen [EMAIL PROTECTED]; Noam Lampert [EMAIL PROTECTED] Sent: Wednesday, September 28, 2005 5:52 PM Subject: Re: [Mono-dev] Compiling System.Web with CSC Hi, Miguel. The option of playing with ilasm/ildasm will mess out completely the debug information. PDB uses the tokens from the DLL to identify the class, method, etc. The tokens will be completely messed up by this exercise. I will look at the output of ildasm to analyze better the .Net 2.0 dependencies to see if we can come up with some kind of hack for using the CSC 2.0 compiler. Eyal. On Tue, 27 Sep 2005, Miguel de Icaza wrote: Date: Tue, 27 Sep 2005 18:12:03 -0400 From: Miguel de Icaza [EMAIL PROTECTED] To: Eyal Alaluf [EMAIL PROTECTED] Cc: [EMAIL PROTECTED], Noam Lampert [EMAIL PROTECTED], Philippe Cohen [EMAIL PROTECTED], mono-devel-list@lists.ximian.com Subject: Re: [Mono-dev] Compiling System.Web with CSC Hello, I think it is a bad idea, specially considering that it means that we have to write more and debug more code than we otherwise would. There is an easy solution that I mentioned before which is that we can add support to mcs to generate pdb files instead. MCS already uses the API to generate debugging information, the only difference is that it consumes a Mono-specific API instead of the cross-platform API. We did not use the cross-platform API in the past because we did not have information on how to use it, but now IronPython has code that shows how to use it. Alternatively to upgrading mcs, you can use csc, and then do: ildasm /out:output file.dll sed script ilasm output.il Where the sed script would remove the couple of new keywords on ildasm and replace the 2.x references with 1.x references. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Big MCS Problem
Hello, Fixed in SVN. Hubert, could you retest it ? I do not like the change in r50836 and much less the follow-up fix. Marek, what were you trying to do with r50836 driver.cs? I think we should revert this to its original state and discuss the next steps. Miguel Thanks, Marek Maybe we had better revert driver.cs in r50836 ... it would be somethat complicated to differentiate file not found and incrrect compiler options. Marek, any good ideas? Atsushi Eno Hubert FONGARNAND wrote: I've updated my mono from svn this morning... There's apparently a problem with Mcs : when i try to compile a simple project with : mcs /home/hubert/Projects/test/Main.cs i get : error CS2007: Unrecognized command-line option: `/home/hubert/Projects/test/Main.cs' Compilation failed: 1 error(s), 0 warnings if I do mcs ./Main.cs it works... mcs ./Projects/test/Main.cs works mcs ~/Projects/test/Main.cs don't works... It used to work yesterday...!!! Thanks ___ Ce message et les 騅entuels documents joints peuvent contenir des informations confidentielles. Au cas o・il ne vous serait pas destin・ nous vous remercions de bien vouloir le supprimer et en aviser imm馘iatement l'exp馘iteur. Toute utilisation de ce message non conforme ・sa destination, toute diffusion ou publication, totale ou partielle et quel qu'en soit le moyen est formellement interdite. Les communications sur internet n'騁ant pas s馗uris馥s, l'int馮rit・de ce message n'est pas assur馥 et la soci騁・駑ettrice ne peut 黎re tenue pour responsable de son contenu. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list -- Miguel de Icaza [EMAIL PROTECTED] ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Big MCS Problem
Hello, Fixed in SVN. Hubert, could you retest it ? I do not like the change in r50836 and much less the follow-up fix. Marek, what were you trying to do with r50836 driver.cs? I think we should revert this to its original state and discuss the next steps. I fixed it to allow compile `mcs /home/a.cs' and report error for `mcs /targe:exe' Regards, Marek Maybe we had better revert driver.cs in r50836 ... it would be somethat complicated to differentiate file not found and incrrect compiler options. Marek, any good ideas? Atsushi Eno Hubert FONGARNAND wrote: I've updated my mono from svn this morning... There's apparently a problem with Mcs : when i try to compile a simple project with : mcs /home/hubert/Projects/test/Main.cs i get : error CS2007: Unrecognized command-line option: `/home/hubert/Projects/test/Main.cs' Compilation failed: 1 error(s), 0 warnings if I do mcs ./Main.cs it works... mcs ./Projects/test/Main.cs works mcs ~/Projects/test/Main.cs don't works... It used to work yesterday...!!! Thanks ___ Ce message et les 騅entuels documents joints peuvent contenir des informations confidentielles. Au cas o・il ne vous serait pas destin・ nous vous remercions de bien vouloir le supprimer et en aviser imm馘iatement l'exp馘iteur. Toute utilisation de ce message non conforme ・sa destination, toute diffusion ou publication, totale ou partielle et quel qu'en soit le moyen est formellement interdite. Les communications sur internet n'騁ant pas s馗uris馥s, l'int馮rit・de ce message n'est pas assur馥 et la soci騁・駑ettrice ne peut 黎re tenue pour responsable de son contenu. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Fwd: Re: [Fwd: Re: [Mono-dev] HTTPS - MS .NET Client - Linux Mono Server - Interoperability]]
The bug number in bugzilla for this is 76258. // Yngve Zackrisson. ---BeginMessage--- On Wed, 2005-09-28 at 15:20, Sebastien Pouliot wrote: Hello Yngve, On Wed, 2005-28-09 at 14:54 +0200, Yngve Zackrisson wrote: ... Should I add a PKCS#12 cert file to the Mono Store (Machine store) (mono /.../certmgr.exe -add -c -m Trust server16-cert.p12) or add only the CA to the trust store (mono /.../certmgr.exe -add -c -m Trust cacert16t.cer) or anything else to get rid of this error message?. It must be either the user or machine Trusted store (otherwise you'll get a trust error). OK. But witch certificate is preferable to add to the store?: a) mono /.../certmgr.exe -add -c -m Trust server16-cert.p12 or b) mono /.../certmgr.exe -add -c -m Trust cacert16t.cer Trust is transitive, i.e. the server will be trusted if it's signer is trusted. So only the self-signed root certificate needs to be added to the Trust store. I interpret this as b) above is enough. What I was wondering with this question was whether a) would solve the error #-2146762486 (CERT_E_CHAINING problem) on the server. I also have a question about the trust of the root CA certificate. The cacert16t.cer above I have created with the following openssl commands: ... $ openssl x509 -in cacert16.pem -trustout -setalias TrustedRootCert -out cacert16t.pem $ openssl x509 -inform PEM -in cacert16t.pem -outform DER -out cacert16t.cer is the first openssl command necessary since the signed client and server certificates, or at least its root CA, should be added to the Windows/Mono (Trust) store?. Currently I use the cacert16t.pem file as -certfile when creating the client and server PKCS#12 files - with the openssl pkcs12 command. Will the cacert16.pem file be enough? I honestly don't know (without reading the man page myself). I don't use openssl much (for x.509 related stuff) because (a) it's formats aren't the one natively used in .NET and (b) I try to dogfood my own tools ;-) ... Yesterday (after your previous email) I tried to use the MS runtime for client certificate without success (same failure). Somehow MS does something different* because the server can't verify the signature (and it's not a key and/or decryption problem - the hash value is different but the padding is ok). Using IE (with the SSL2 client hello) to do the same turned out another problem, very similar to the bug #76254 reported today. [*] The client certificate testing is done with wget/openssl (linux/cygwin) - which sadly doesn't seems enough :( Please let me know if you come up with some solution. I have been working with the HTTPS communication for some 2 months now, and my boss is eager to get an solution :-). Please open a bugzilla issue on bugzilla.ximian.com (e.g. SSL client certificate doesn't work with IE.). That way you'll get notified as soon as (and whenever) I change the bug status. I interpret this as I shall create a new bug in bugzilla for this with a short summary of SSL client certificate doesn't work with IE.. I will do that, after installing the CA root cert (cacert16t.cer) into the Mono's machines Trust store, and run a new test case for the bug report. Regards Yngve Zackrisson. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ---End Message--- ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Fwd: Re: [Fwd: Re: [Mono-dev] HTTPS - MS .NET Client - Linux Mono Server - Interoperability]]
---BeginMessage--- On Wed, 2005-09-28 at 15:20, Sebastien Pouliot wrote: Hello Yngve, On Wed, 2005-28-09 at 14:54 +0200, Yngve Zackrisson wrote: ... Should I add a PKCS#12 cert file to the Mono Store (Machine store) (mono /.../certmgr.exe -add -c -m Trust server16-cert.p12) or add only the CA to the trust store (mono /.../certmgr.exe -add -c -m Trust cacert16t.cer) or anything else to get rid of this error message?. It must be either the user or machine Trusted store (otherwise you'll get a trust error). OK. But witch certificate is preferable to add to the store?: a) mono /.../certmgr.exe -add -c -m Trust server16-cert.p12 or b) mono /.../certmgr.exe -add -c -m Trust cacert16t.cer Trust is transitive, i.e. the server will be trusted if it's signer is trusted. So only the self-signed root certificate needs to be added to the Trust store. I interpret this as b) above is enough. What I was wondering with this question was whether a) would solve the error #-2146762486 (CERT_E_CHAINING problem) on the server. I also have a question about the trust of the root CA certificate. The cacert16t.cer above I have created with the following openssl commands: ... $ openssl x509 -in cacert16.pem -trustout -setalias TrustedRootCert -out cacert16t.pem $ openssl x509 -inform PEM -in cacert16t.pem -outform DER -out cacert16t.cer is the first openssl command necessary since the signed client and server certificates, or at least its root CA, should be added to the Windows/Mono (Trust) store?. Currently I use the cacert16t.pem file as -certfile when creating the client and server PKCS#12 files - with the openssl pkcs12 command. Will the cacert16.pem file be enough? I honestly don't know (without reading the man page myself). I don't use openssl much (for x.509 related stuff) because (a) it's formats aren't the one natively used in .NET and (b) I try to dogfood my own tools ;-) ... Yesterday (after your previous email) I tried to use the MS runtime for client certificate without success (same failure). Somehow MS does something different* because the server can't verify the signature (and it's not a key and/or decryption problem - the hash value is different but the padding is ok). Using IE (with the SSL2 client hello) to do the same turned out another problem, very similar to the bug #76254 reported today. [*] The client certificate testing is done with wget/openssl (linux/cygwin) - which sadly doesn't seems enough :( Please let me know if you come up with some solution. I have been working with the HTTPS communication for some 2 months now, and my boss is eager to get an solution :-). Please open a bugzilla issue on bugzilla.ximian.com (e.g. SSL client certificate doesn't work with IE.). That way you'll get notified as soon as (and whenever) I change the bug status. I interpret this as I shall create a new bug in bugzilla for this with a short summary of SSL client certificate doesn't work with IE.. I will do that, after installing the CA root cert (cacert16t.cer) into the Mono's machines Trust store, and run a new test case for the bug report. Regards Yngve Zackrisson. ---End Message--- ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Big MCS Problem
Hello, I do not like the change in r50836 and much less the follow-up fix. Marek, what were you trying to do with r50836 driver.cs? I think we should revert this to its original state and discuss the next steps. I fixed it to allow compile `mcs /home/a.cs' and report error for `mcs /targe:exe' What was wrong with the old code? The old code I had carefully crafted so that scenario would work. I do not like the current set of hacks to catch the /targe:exe as a special case. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Big MCS Problem
Hello, I do not like the change in r50836 and much less the follow-up fix. Marek, what were you trying to do with r50836 driver.cs? I think we should revert this to its original state and discuss the next steps. I fixed it to allow compile `mcs /home/a.cs' and report error for `mcs /targe:exe' What was wrong with the old code? The old code I had carefully crafted so that scenario would work. Well, the old code was commented. So it didn't work. I uncommented it and fixed bug found by Hubert. I do not like the current set of hacks to catch the /targe:exe as a special case. I am not catching /targe:exe as a special case. This is just example. You can use whatever typo what you want. It will not allow you to use `mcs /a' where `a' is some C# source file but I am not sure whether it is allowed location. Marek ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] What about the Windows setup of Mono?
Hi Kornél, I'm working on the windows installer and it should be finished shortly. I'm shooting for today but it may be tomorrow. The good news is that after I'm done automating it the installers will be released in parallel with the mono releases. Your suggestions are very much appreciated. I believe (Paco, correct me if I'm wrong) the reason Paco used batch files instead of setting up environment variables was so that multiple mono versions could be installed in parallel. I will look into packaging libgdiplus with the installer. I think that's a great idea. Wade On Wed, 2005-09-28 at 20:08 +0200, Kornél Pál wrote: Hi, Is anyone working on it? When will it be released? Some suggestions: I don't like to have bat files in bin directory while having executables in lib directory. I think environment variables should be set in Windows instead of using batch files. And I would like to have an option to add mono\bin directory to PATH. Some others from the archive: http://lists.ximian.com/pipermail/mono-devel-list/2005-September/014803.html http://lists.ximian.com/pipermail/mono-devel-list/2005-September/014817.html Kornél ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] What about the Windows setup of Mono?
These are good news.:) May I have a look at the setup script before you build the installer? Kornél - Original Message - From: Wade Berrier [EMAIL PROTECTED] To: mono-devel-list@lists.ximian.com Sent: Wednesday, September 28, 2005 11:47 PM Subject: Re: [Mono-dev] What about the Windows setup of Mono? Hi Kornél, I'm working on the windows installer and it should be finished shortly. I'm shooting for today but it may be tomorrow. The good news is that after I'm done automating it the installers will be released in parallel with the mono releases. Your suggestions are very much appreciated. I believe (Paco, correct me if I'm wrong) the reason Paco used batch files instead of setting up environment variables was so that multiple mono versions could be installed in parallel. I will look into packaging libgdiplus with the installer. I think that's a great idea. Wade On Wed, 2005-09-28 at 20:08 +0200, Kornél Pál wrote: Hi, Is anyone working on it? When will it be released? Some suggestions: I don't like to have bat files in bin directory while having executables in lib directory. I think environment variables should be set in Windows instead of using batch files. And I would like to have an option to add mono\bin directory to PATH. Some others from the archive: http://lists.ximian.com/pipermail/mono-devel-list/2005-September/014803.html http://lists.ximian.com/pipermail/mono-devel-list/2005-September/014817.html Kornél ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] What about the Windows setup of Mono?
Take a look at svn for what I'm doing with the setup script: http://svn.myrealbox.com/viewcvs/trunk/release/windows-installer/ Specifically Mono_template.iss. The process I'm using is quite different than previous windows installers. That being said, there will potentially be some unexpected surprises with the installers being built this way because the process is so different. Please extend your (as in the mono community) patience as we work through any problems that may (and probably will) come up. Wade On Wed, 2005-09-28 at 23:58 +0200, Kornél Pál wrote: These are good news.:) May I have a look at the setup script before you build the installer? Kornél - Original Message - From: Wade Berrier [EMAIL PROTECTED] To: mono-devel-list@lists.ximian.com Sent: Wednesday, September 28, 2005 11:47 PM Subject: Re: [Mono-dev] What about the Windows setup of Mono? Hi Kornél, I'm working on the windows installer and it should be finished shortly. I'm shooting for today but it may be tomorrow. The good news is that after I'm done automating it the installers will be released in parallel with the mono releases. Your suggestions are very much appreciated. I believe (Paco, correct me if I'm wrong) the reason Paco used batch files instead of setting up environment variables was so that multiple mono versions could be installed in parallel. I will look into packaging libgdiplus with the installer. I think that's a great idea. Wade On Wed, 2005-09-28 at 20:08 +0200, Kornél Pál wrote: Hi, Is anyone working on it? When will it be released? Some suggestions: I don't like to have bat files in bin directory while having executables in lib directory. I think environment variables should be set in Windows instead of using batch files. And I would like to have an option to add mono\bin directory to PATH. Some others from the archive: http://lists.ximian.com/pipermail/mono-devel-list/2005-September/014803.html http://lists.ximian.com/pipermail/mono-devel-list/2005-September/014817.html Kornél ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] What about the Windows setup of Mono?
Hopefully, you can continue allowing the Mono Win32 installers to allow parallel installs. I need the ability to have multiple versions of mono installed. Some application working in one version, such as, Mono 1.1.6 do not work in Mono 1.1.8. Wade Berrier wrote: Hi Kornél, I'm working on the windows installer and it should be finished shortly. I'm shooting for today but it may be tomorrow. The good news is that after I'm done automating it the installers will be released in parallel with the mono releases. Your suggestions are very much appreciated. I believe (Paco, correct me if I'm wrong) the reason Paco used batch files instead of setting up environment variables was so that multiple mono versions could be installed in parallel. I will look into packaging libgdiplus with the installer. I think that's a great idea. Wade On Wed, 2005-09-28 at 20:08 +0200, Kornél Pál wrote: Hi, Is anyone working on it? When will it be released? Some suggestions: I don't like to have bat files in bin directory while having executables in lib directory. I think environment variables should be set in Windows instead of using batch files. And I would like to have an option to add mono\bin directory to PATH. Some others from the archive: http://lists.ximian.com/pipermail/mono-devel-list/2005-September/014803.html http://lists.ximian.com/pipermail/mono-devel-list/2005-September/014817.html Kornél ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] What about the Windows setup of Mono?
Hi, I had a look at the script.:) Some notes about .a and other files not required to run Mono: I don't think that there is a need to link to Mono libraries. But a lot of people are using glib and other dependencies that come with the installer to build Mono on cygwing as it is easier to use that version than building from scratch. So .pc and other files required to use it should be retained. Linux version and Windows version installed using cygwin works without setting environment variables so I don't think there is a need to wrap mono.exe (and any other native executable) using a .bat. Of course using .bat files for managed executables is required. And if I use Windows version that comes with installer without unnecessary .bat files by copying .exe-s from lib to bin there are no problems. As only one mono.exe is accessible using PATH at a time I don't see any reason to wrap mono.exe using .bat files and it don't affect side-by-side versioning of Mono. Kornél - Original Message - From: Wade Berrier [EMAIL PROTECTED] To: Kornél Pál [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; mono-devel-list@lists.ximian.com Sent: Thursday, September 29, 2005 12:19 AM Subject: Re: [Mono-dev] What about the Windows setup of Mono? Take a look at svn for what I'm doing with the setup script: http://svn.myrealbox.com/viewcvs/trunk/release/windows-installer/ Specifically Mono_template.iss. The process I'm using is quite different than previous windows installers. That being said, there will potentially be some unexpected surprises with the installers being built this way because the process is so different. Please extend your (as in the mono community) patience as we work through any problems that may (and probably will) come up. Wade On Wed, 2005-09-28 at 23:58 +0200, Kornél Pál wrote: These are good news.:) May I have a look at the setup script before you build the installer? Kornél - Original Message - From: Wade Berrier [EMAIL PROTECTED] To: mono-devel-list@lists.ximian.com Sent: Wednesday, September 28, 2005 11:47 PM Subject: Re: [Mono-dev] What about the Windows setup of Mono? Hi Kornél, I'm working on the windows installer and it should be finished shortly. I'm shooting for today but it may be tomorrow. The good news is that after I'm done automating it the installers will be released in parallel with the mono releases. Your suggestions are very much appreciated. I believe (Paco, correct me if I'm wrong) the reason Paco used batch files instead of setting up environment variables was so that multiple mono versions could be installed in parallel. I will look into packaging libgdiplus with the installer. I think that's a great idea. Wade On Wed, 2005-09-28 at 20:08 +0200, Kornél Pál wrote: Hi, Is anyone working on it? When will it be released? Some suggestions: I don't like to have bat files in bin directory while having executables in lib directory. I think environment variables should be set in Windows instead of using batch files. And I would like to have an option to add mono\bin directory to PATH. Some others from the archive: http://lists.ximian.com/pipermail/mono-devel-list/2005-September/014803.html http://lists.ximian.com/pipermail/mono-devel-list/2005-September/014817.html Kornél ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] change to the 2.0 machine.config file
anyone have a problem with this? I've been hacking on the 2.0 System.Configuration stuff, and the new section types go unused without these entries: Chris Index: machine.config === --- machine.config (revision 50953) +++ machine.config (working copy) @@ -3,7 +3,9 @@ configuration configSections - section name=appSettings type=System.Configuration.NameValueFileSectionHandler, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 / + section name=appSettings type=System.Configuration.AppSettingsSection, System.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a / + section name=connectionStrings type=System.Configuration.ConnectionStringsSection, System.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a / + section name=mscorlib type=System.Configuration.IgnoreSection, System.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a / section name=system.diagnostics type=System.Diagnostics.DiagnosticsConfigurationHandler, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 / section name=system.runtime.remoting type=System.Configuration.IgnoreSectionHandler, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 allowLocation=false/ section name=strongNames type=System.Configuration.IgnoreSectionHandler, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 allowLocation=false/ ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
