I found myself working on another inherited application this week. As it with all inherited applications, especially ones as old as this one, the processes around deployment were a mess. In fact, most deployments had been done by hand with no standards around the deployment location. How was I supposed to write an upgrade for an application when I didn’t even know where it was installed?

At least the ActiveX DLL’s details were in the registry – retrieving them was a pretty simple two step process; you just need to know the name of one of the classes within your DLL.

Many people have requested the ability to run an SQL file, which holds multiple commands.  As the developer states, this is not really possible as the plugin cannot really deal with multiple result sets and errors.

This would be extremely useful, especially when doing a fresh installation of an application.  All of my application installations install the databases from script, for a number of reasons:

• Easier to do remote DB setup
• Easier to keep code under version control

Initial public release.

This release includes both the header file and an example NSIS file

If you have any questions, comments or improvements please leave a comment or send me an email.

LogicLib extensions for checking Microsoft .NET framework versions and service packs.

"HasDotNet<version>" checks if the specific version of .NET framework is installed.

<version> can be replaced with the following values:
1.0
1.1
2.0
3.0
3.5

"AtLeastDotNetServicePack" checks if the .NET framework has a service pack version at least as specified.

"IsDotNetServicePack" checks if the .NET framework has a service pack version exactly as specified.

I have recently become an avid fan of NSIS, the Nullsoft Installer Script. It is an extremely powerful way of creating installers, as it gives you control over almost every aspect the installer. Coming from a PHP/C#  background, I have also found it fun learning the quirky ways of using NSIS and am still not sure that I am doing things quite right.

This is an alpha release of the project. Please feel free to use modify as you wish

This file contains both the source code, and in the 'bin' folder is the compiled executable.

NOTE: This is an alpha release, please take care when using this application.

A small utility windows application, written in C#, that will split a text file based on a character.

Enter:

• Filepath
• split character
• Output location
• Ouput extension

The application will then split the text up into chunks, saving those chunks as separate files within the output directory. The output filename format is output_{file#}.{extension}.

I recently received a a large text file (many megabytes) which was a concatenation of many different smaller files.  The smaller files where of different size and the separated by a particular character. I did a quick Google search, but almost all of the file splitting applications available split files based on size.

I needed to split a file based on a certain ASCII character.

Once I got the initial data transfer up and running, I needed to place the whole thing into a transaction, I was doing multiple table transfers (with some data manipulation).  I could not have half a database transferred, even if I did throw an error.

I simply threw in an SqlTransaction, and made everything run inside that.

However, I hit an exception when using the SqlCommandBuilder to create the insert command: