I often have to integrate applications into pure html websites, maintained with a content creation system. I usually throw the application into a separate folder, and make that folder an application in IIS. I then create a master-page and throw their site’s template in it.

The problem I was having was managing paths to css and images within the template when developing the application using the local file system. I wanted to use all their image resources and the existing scripts and CSS and view all these together when I was developing.

Some of the servers I work on are in the U.S., but I work from Canada and have my PC set to locale en-CA. This locale inverts the month and day in the short date string. For example May 1st 2009 would be written as 5/1/2009 in the US, 1/5/2009 in Canada, as per the locale. SQL Server is usually setup as US as the locale for storing dates regardless of where the server is.

For the last couple of years, I’ve been working with another developer on one project. Once we started working in the same space, of course we started to overwrite each others work. I work from Montreal, Quebec and he works from New Brunswick. We needed a good solution for checking in/out files that was inexpensive and with minimal setup and expertise required. I also wanted to be able to publish the changes immediately, not having to keep to sets of data, updating the version control, then updating the production server.