A statistical update

When you take over someone else's code and have the intention of improving it, it is typical to see the code size deflate and then inflate again.

The last time I posted about the statistics and analysis of the code, I showed how Manager had shrunk heavily compared with the earlier version (v1.6). At the time, we had the tough job of going through all the code refining and improving it where it could be. Naturally, we found wasted code that was then stripped out. This brought the code back to a basic, but highly optimized level.

Once we start implementing new features, or simply improving the old, the code starts to grow again.
Therefore, I thought I'd post the code statistics based on where we are now compared to September 2011.

EISNet v1.7 (September 2011)

Code Lines: 10,761 (62.75%)
Comment Lines: 1,706 (9.95%)
Blank Lines: 4,681 (27.30%)
Modules: 5
Classes: 1
Forms: 28

EISNet v1.7 (January 2012)

Code Lines: 13,443 (61.24%)
Comment Lines: 2,510 (11.43%)
Blank Lines: 6,000 (27.33%)
Modules: 5
Classes: 1
Forms: 26
User Controls: 2

It is important to note that as of the January version, the source code includes Package Manager (previously known as Applications) and Archivist tools.

If you include into Septembers Manager source, the old Applications and Archivist modules, the total lines of code would be 36,587. This is now down to 13,443 and is all in one application. That's 36.7% of the original size.

Finishing Package Manager

Package Manager is virtually feature complete, although I stress that this is pretty much like for like when compared to the previous version known as 'Applications'.

We have now added the ability to import LNK files - a feature that did already exist, but the code has been re-written. More importantly, you can now import a REG file directly. This means if you have a Registry Fragment file with 100's of settings, you can now import the whole lot with one click. This will hopefully make creating packages a lot more easier.

We have added two new fields into the Package Manager. Each package can now have a version number stored separately and also a description. These will help maintain a good Package repository, but will also be used in future EISNet releases.

As another change to Packages, the definition between an MSI package and a command line package has been completely removed. Each package contains a Package file, regardless of it's type. EISNet is now more intelligent on how it handles each one.

The final addition is the Arguments field. This has been added so each package can have specific arguments attached to it when it launches. This may include arguments for MSI files also. So if you want a silent MSI install, you specify /Q or /QB. This was previously only possible by setting the package as a command line, and then use the MSIExec.exe tool to launch the installation.

Below is a screenshot of the Package Properties window which has changed since my last post.

Package properties

Introducing Package Manager

Welcome to 2012 and a happy new year!

This year is looking to be extremely exciting for EISNet and this post is to give you an update on the progress over the past few weeks.

Almost all of the work recently has been purely on what you may know as 'Applications'. This separate tool allows you to create software packages and shortcuts that are then assigned to computers and users from within Manager. Our goal since taking on this project is to reduce the number of separate tools and merge everything into EISNet Manager.

For EISNet v1.7, the term 'Applications' is no more. We will be using a more relevant term called 'Packages' and as a result, Manager now has a tool integrated called 'Package Manager'.

Although the functionality has not greatly changed, the interface has. In addition, the code behind it has been completely re-written to a modern standard, which allows us multiple options in the future.

EISNet Package Manager

The window is made up of 3 panes. The left side contains the list of available packages. When you select a package, the two panels on the right hand side show you the Shortcuts and Registry settings for the selected package.

Creating and editing a package

Creating a new package has not changed. You can however now assign an icon for the package, to make it prettier in the respective package lists. We also plan to make the chosen icon appear on the clients when installing.

Editing a shortcut

Renaming a start menu folder

Each package can have many shortcuts attached to them. Commonly this will be the shortcuts seen by the end users in the start menu and desktop. You can now edit the shortcut location directly when editing a shortcut. You can also create, edit and delete the start menu folders directly and all on the fly.

Exporting a package

A new feature we have decided to implement is the ability to import and export packages from EISNet. This really is as simple as it sounds. You select one (or more) packages and select 'Export' from the context menu. Each package is then exported into a compressed EIP file. This single file can then be imported elsewhere, which will prove useful for roaming technicians in schools. Each exported file contains all required files, shortcuts and registry settings.

I'm sure you'll agree the changes made are an exciting update. We are all working hard to get this released on time.