Updated Utility: Unleash It 2.1.1

Published 24 September 04 04:58 PM | mhawley

I've released a new version of Unleash It that fixes multiple problems that people were having. Most notably, exclusion of folders when a VS.NET project was the source was not possible. After re-working the code, this is now possible along with being able to view the files / folders to be deployed dialogs.

Changelog:

  • Added support for displaying folders / files to include for VS.NET Project Files as the source.
  • Added ability to name your FTP profiles.
  • Added checking to see if Unleash It is currently running during installation / uninstallation.
  • Fixed error when parsing a file mask with an underscore.
  • Fixed the logfile button being enabled after a deployment when that profile isn't using logging.
  • Fixed mis-spelling of "changed" in the logfile for FTP deployment.
  • Fixed directories not being excluded during a VS.NET Project deployment.

So, head on over to http://www.eworldui.net/unleashit to get your latest copy!

Filed under:

Comments

# Søren Gregersen said on September 27, 2004 08:04 AM:

Hi Matt

I upgraded to version 2.1.1 this morning when I got promted, and now I'm unable to deploy my project ( at least using UnleashIt ). It looks like the destination path is incorrect ( maybe an extra {1} or something ).

This occours when my destination is a directory, I haven't tried FTP or Zip File.

# Matt Hawley said on September 27, 2004 09:49 AM:

What is your source?

# Matt Hawley said on September 27, 2004 09:53 AM:

Also, if you re-download Unleash It, I've placed 2.1 back up.

# TrackBack said on September 27, 2004 01:58 PM:
# David said on October 4, 2004 01:15 PM:

Where can I find the 2.1? (2.1.1 or 2.1.1.1(?) doesn't seem to work for me.

Maybe it would be wise to encode the version number into filename of downlad file e.g. UnleashIt211.zip.

# Matt Hawley said on October 4, 2004 01:18 PM:

David, 2.1.1.1 can be downloaded at http://www.eworldui.net/UnleashIt by clicking the image on the top right hand side.

i've thought about encoding the version number, however this means that some people link directly to the file which ultimately leads to people getting older versions. I personally have the setup files for each version >= 2.0 in case someone wishes to have an older version.

# David said on October 5, 2004 09:35 AM:

Sorry, I wasn't clear eoungh. 2.1.1.1 doesn't work for me. Only some files get deployed. Do you know why? Will older version help? I figured that last version has a bug...

# TrackBack said on October 5, 2004 08:14 PM:
# TrackBack said on October 5, 2004 08:33 PM:

This Blog

News

.NET Links

Blogs I Read

Syndication