Project Environment

Whilst the source code for Kajabity Tools itself does not depend on any particular environment it might be useful to have a quick overview of the different tools I’m using in its development.

The C# code itself is now developed using Visual Studio 2013, which I’ve recently upgraded to. I’ve used older versions in the past and started the project originally using Sharp Develop.

I have a number of Visual Studio plugins to help me with particular aspects of the development:

• Git Source Control Provider – ensured VS was aware of the Source Control aspect of the project and let me add and commit some changes.
• NUnit 3 Test Adapter – helped me to create, execute and debug the NUnit tests in the Kajabity Tools.Test project.

As well as these, I also make use of:

• Git command line – as an alternative to the plugin, I do a lot of the Git stuff through the command line.
• AppVeyor – continuous integration service to build, test, package and deploy Kajabity Tools binaries whenever I commit to the repository.

Testing

For the latest release (v0.4), there are some more NUnit tests and I’ve upgraded to NUnit 3. These tests use a number of sample files for both Java Properties and CSV files (which are copied to the output folder to make it easy for the tests to find them).

The tests run in Visual Studio with the test runner.

You can also test that the code is working correctly using the sample applications.