Introduction

I wrote this utility when I found myself having to repeatedly edit files for a Web site and then use an FTP client to upload the changes. Since I was spending my time editing images, I had to switch between multiple programs and then perform multiple steps to get the changed files uploaded. This made me want a simpler way.

FtpPublisher removes the need to manually use an FTP client or have another program that you use to publish with FTP. It will support any number of files, from various local locations to be synchronized to the remote site.

Using FtpPublisher

FtpPublisher has two modes, a design and an execution mode. As it sounds like, design mode lets you set your configuration while execution mode will take the configuration and perform the date testing and uploading.

Once your FTP connection information has been entered, FtpPublisher will retrieve the site's folder hierarchy. Each remote folder can contain a list of files that will be synchronized. This configuration can be saved into an XML file, which FtpPublisher takes as a command line argument to run in its execution mode.

To further increase the efficiency of the application, it can create a file association with its own file type. This is done by running the InstallUtil on the executable. If this is done, uploading your changes to an FTP site is as simple as double clicking the configuration file and watching it work.

The Code

FTP

All FTP functions come from edtFTPnet. I didn't use .NET 2.0's FtpWebRequest because on my initial examination, I was blind and didn't see a way for it to run in passive mode. I later looked again and realized I just hadn't scrolled down far enough, but the application was finished by then.

File Synchronization

Every file entry in the configuration contains a path and a DateTime stamp for when that file was uploaded last. It decides to upload if the file has been modified since it last wrote the stamp. I chose this method instead of getting the DateTime from the FTP because I wanted these local files to be the master copies.

if (File.GetLastWriteTime(item.Path) > item.LastUpload)

Thread Synchronization with Anonymous Methods

The execution mode has its own UI. To keep that UI responsive, I have a BackgroundWorker do all the main work on a separate thread. I couldn't use its built in progress report functionality because it performs multiple types of progress updating. To simplify my life, I originally used anonymous methods inside a Control Invoke call.

progressBarMain.Invoke((MethodInvoker)delegate() { });

As I was coding, I wondered if there was another way to ensure the updates were run on the correct thread. This is where SynchronizationContext comes in. It is a class designed to handle the details of which thread to perform on.

It works by getting a reference to the current thread when the Current property is accessed.

SynchronizationContext context = SynchronizationContext.Current;

Then, inside the background thread, a call to its Send method will perform the work.

context.Send(delegate(object state) { }, null);

Installer

Setting up file associations is an easy thing to do, but some people might not know the details of how it's done. So here is an example:

ok, never mind.i think i'll skip this app, i dont understand at all how it works and its too buggy.took me 15 minutes to figure out you have to click "OK" to get the directory list, change it to something more accurate like "CONNECT".why cant i attach master local-directory to a master remote-directory on the server and sync instead of selecting 400 files manually.