ecto for Windows (alternate title: Windows install dependencies suck)

About a year and a half ago (in what seems like another life now), I wrote about my first (good) impressions using ecto for OS X. It was a different job, a different blog platform (Movable Type), and a different OS. Now that I’m doing Windows again at work (still OS X at home), I decided to try ecto for Windows against a WordPress blog.

I downloaded ecto for Windows (zip file, ~3.9MB) and was slightly annoyed when the readme told me I needed to download something else, Microsoft .NET Framework 1.1 SP1, which is about 10.5MB. I downloaded it anyway, but got this error message when I tried to install it on my stock Yahoo-issued laptop (which has been rock-solid since I got it just over three months ago):

The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch.

Oh well. I noticed on the .NET Framework 1.1 SP1 page that there was a link to .NET Framework 2.0, so I downloaded that (almost 23MB!) My first thought was, “if this thing installs, there is absolutely no way I’m going to get away without a reboot.” My second thought was “there should be backwards compatibility — maybe it will work.” It installed — with no reboot required. Wow.

Then I tried to install ecto again and got this message:

Microsoft .NET Framework v1.1 SP1 is not installed. Please visit Microsoft website to download and install the framework before installing ecto.

For the heck of it, I tried installing v1.1 again, and got this message again:

The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch.

Deciding that the .NET Framework 2.0 was of no use to me, I went to Add/Remove Programs to remove it and got this message: “Uninstalling Microsoft .NET Framework 2.0 might cause other programs to stop working correctly. Are you sure you want to uninstall Microsoft .NET Framework 2.0?” Ugh. What “other programs” are we talking about? I didn’t really feel like blowing up my laptop, so I stopped right there. The ecto for Windows FAQ addresses this requirement: “Q2: Is the .Net Framework really necessary? ecto for Windows is developed entirely in Visual Studio .Net 2003 using C#. This allow rapid development of new features and debugging.”

My verdict on ecto for Windows is simple: making it easy to get past the install process relatively painlessly would be a nice start. I never got past the first dependency. I shouldn’t have veered off the script and upgraded to .NET Framework 2.0 for the heck of it, but should it really be this painful and require a secondary download that is 3x larger than the software itself to get going? I loved ecto for OS X. I guess I’ll have to wait to see how it works for Windows until ecto works with .NET Framework 2.0.

Update: for those of you who don’t read the comments, Alex writes in with the following excellent news (and barely ten minutes after I posted!):

Support for .Net 2.0 in the installer will be added soon. ecto is .Net 2.0 compatible, it is just that the installer needs to be updated to check for that. A maintainance update will be released this weekend to include .Net 2.0 compatibility.

As a matter of fact, the next major update will require .Net 2.0 framework.

I’ll write more about ecto itself when I get it installed. . . but I certainly admire the rapid response.

Update 11/28/05: Alex Hung e-mailed me on Thursday to let me know that ecto had been updated to include .Net 2.0 compatibility. I just installed the new version of ecto with no problems and am using to update this blog post. Thanks, Alex!

Advertisements

2 thoughts on “ecto for Windows (alternate title: Windows install dependencies suck)

  1. Support for .Net 2.0 in the installer will be added soon. ecto is .Net 2.0 compatible, it is just that the installer needs to be updated to check for that. A maintainance update will be released this weekend to include .Net 2.0 compatibility.

    As a matter of fact, the next major update will require .Net 2.0 framework.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s