I recently had to install a small client application to several computers around the office. The installation process involved copying the files from a cd to a specific folder, no installer or anything like that. However, I had to create the application shortcuts by hand and although not hard, I had the idea to automate the process as a learning experience.

Instead of creating a batch file I decided to go use a windows scripting file or wsf to use it as learning opportunity. A wsf allows you to use any number of scripting languages as well as xml elements to define some of the actions you want to execute. It also allows you to separate different actions into jobs, something that might be helpful but I found it rather awkward because you cannot execute a second job after you finish with the first one.

I am not an expert on this area or know enough to recommend when to use or not use a .wsf file . However, I am glad that I took a few minutes to pick this up find out more about Microsoft’s Windows Scripting Host.

My .wsf file basically creates a new shortcut under the programs in the start menu and also creates one on the desktop. The most complex piece of logic involves checking weather or not a folder already exists to create the new shortcut in the start menu. You can read over it and put it together yourself without any trouble.