Comments by Hermanito72 (Top 4 by date)

Okay, so when I have the three projects, and I create a full build, it should create two EXE's and one DLL?
For simplicity of installation however, I think they would like to get a commandline tool that is just the EXE, and doesn't need to also have a separate DLL file. Is this possible as well?

Also, thanks for editing my incorrectly posted followup to OriginalGriff, I now think I understand the posting and replying system...

SAKryukov, thanks for your elaborate answer.

I will surely look into your commandline parameters library, that way I don't need to reinvent that part :-)

I totally agree on your point of view on version control. Unfortunately I tend to agree that I work with moderate idiots (I won't go as far as qualifying them as extreme :-))
The company does have proper development procedures and source control (Visual Studio Ultimate clients on Visual Studio Team Foundation Server), but the tool I am creating is not deemed important enough to give me a license to VS Ultimate. So I have to make do with the Express version.

About subversion: you are right that it is open source, but there are many implementations that are also freeware, of course there are also commercial implementations. But anyway, it is not trusted, and they will not install it just for me.