Open Source Business Conference and green light means go.


I just got back from a successful trip to San Francisco and I’m very glad to be home again.  However, I really wish I could attend the Open Source Business Conference 2004 in downtown San Francisco.  It’d be really interesting to listen to speakers address the issue I’ve highlighted from their introduction:


[read more]

Comments (4)

  1. Leslie Easter says:

    I recently stumbled upon your blog. Very interesting ready. I hope that you keep at it. I apologize for reaching back into the past, but I had a few comments re: Setup is…

    First, you may be interested in some further reading. A few years back I ran into a ton of research that was done in a gradute-level program. It was on deployment models. Very extreme but cool stuff. A second article that was also done a few years ago was specifically on setup/deployments. That one was done by someone at Microsoft. I can dig into more of these if you’re interested, but you’re on the right track.

    Second, I would like to respectfully disagree with your two Axioms of Setup. I understand that you intention was to keep the model simple and light, however, I do believe there are basic rules of engagement when designing an install. Let me provide you with a couple primary rules.

    1. The setup must validate that key software/hardware application requirements are met before modifying the system.

    Comments: This is currently what the Windows Installer model provides for. Through the immediate mode the install developer has the opportunity to verify system requirements are met (eg, LaunchConditions, etc).

    2. In the event that the install detects an invalid install condition, a full rollback should be performed.

    Comments: Also, provided for nicely by Windows Installer. Historically, up to WIndows Installer a full and complete rollback was not attainable.

    3. The install should make every possible effort to insure its own success.

    Comments: Ideally, at the end of the install a process should be launched that queries back through the application to verify connectivity and basic launching functionality has been achieved.

    4. A uninstall should cleanly uninstall the application resources and application data. System ref counted resources are exempted.

    Comments: With the exception of user data which the user should have the option to remove.

    I’m sure I could round these out a bit more. I only have a few minutes and wanted to add this to the discussion.

    Your comments are appreciated.

  2. Imagine a blog entry where I discuss Open Source at Microsoft via posts on Josh Ledgard’s blog.

  3. The oft promised Windows Installer XML (WiX) toolset has released under a true Open Source Software license (Common Public License) on SourceForge.net (a first for Microsoft). The WiX toolset is a command-line compiler and linker for creating Windows Installer packages (MSI and MSM files) from XML source code. This blog entry kicks off a new category “Windows Installer Xml (WiX)” where I will talk about building MSI files with the toolset.