Sabastien Pouliot, the titan of Mono security, has rebuilt a Win32 system of his and used my custom Cygwin CD to do a build of Mono from source. His feedback along with Atsushi Enomoto's comments (the XML wonder and Paco CD evaluator extraordinaire) have been the highlight of my week. I have done some new work on the Cygwin installation since the advent of 1.1.2 builds, so you may expect a new version of the Cygwin CD that will allow compilation of the 1.0.x code base as well as the 1.1.x. to be shipped to Novell/Ximian HQ for final disposition.
Along the testing lines, I will like to mention Simon Bain, Sankar Ramalingam, Alain Favre aka "Prettyfly", Paulo Pires and a special thanks to Angel Marin for spotting a big omission on my part for the installation of Mono without any GTK or Gtk# selections.
I have whipped out a new rendition of the installer with some fixes already. Once again I ask for you folks to give it another look over and to kick the tires some more.
The main purpose of this control panel applet is to set the default installation of the Mono runtime to use by the Mono Launcher apps. This will be necessary as users choose to install the 1.0.x and the 1.1.x distributions in a side-by-side fashion. In turn, the launchers will come in two flavors, monoLaunchW.exe for Gtk# apps that we want to launch without the sometimes unsightly Win32 Console window and monoLaunchC.exe which will be intended for applications that want to have their output to stdout shown (great for debugging purposes).
Well, I don't use that much Windows Forms, I have used it so sparingly for non sample work (in the options dialog box for the VSProj2Make add-in for Visual Studio 2003). But what I still use and will use some more of, is either straight Win32 SDK GUIs or MFC/ATL assisted GUIs.
Being that I do a lot of Installer work, I can't count on having Gtk#, Mono or even the .NET Framework installed already when my helper apps are launched. Therefore I have to do native programming still in Win32 :(. I am beginning to look at Windows Template Library (WTL) (again) for some of the components. The last time I looked into WTL it was still being distributed with the Platform SDK back in Oct 2001, and it was not my cup of tea. So far, when I am forced to do complex Win32 GUIs, I tend to do MFC statically linked.
Let's hope that this new WTL thing is friendlier to an Open Source program and as efficient (will settle for close enough) as straight Win32 SDK programming.
I only have 4 working days before leaving for Puerto Rico.
WTL documentation and help files can be found at CodeProject. Very useful things to have around.
http://www.codeproject.com/wtl/
Posted by: Christian Mogensen at November 18, 2004 12:34 PMHey Monkey boy!
You never got in touch with me to snail mail me a custom Cygwin CD. I even offered to host it for you. Is this how you treat your friends? :-D
Anyhow, you'd better be bringing a copy of your custom Cygwin CD to Puerto Rico next week, or I'll sabotage your presentation, like last May! :-D :-D
Just kidding about the sabotage, but do bring a copy of the custom Cygwin CD, and I'll give you a copy of my SNAP DK CD. ;-)
Posted by: PJ Cabrera at November 18, 2004 01:44 PMPJ!
That is why I never got in contact with you :)
I am so bringing it with me, and I was going to get you wined and dinned to persuade you to host the ISO. :)
Paco
Posted by: Paco at November 18, 2004 02:56 PMThank you for you work on the win32 installer of Mono and all thinks you do for this community.
I really enjoy to help testing as much as I can.
Alain Favre as prettyfly
Posted by: Alain Favre at November 19, 2004 04:11 AMWine and dine me to host it? I offered, a month ago!
But okay, I'll just let you wine and dine me, because that's the kind of cheapskate I am. :-)
Posted by: PJ Cabrera at November 19, 2004 08:01 PMNice to see all your hard work paying off! Have a safe trip to Puerto Rico - see you when you get back!
Posted by: Scott Dockendorf at November 23, 2004 01:00 AM