Home

If you're interested in working with the Georadix.NET source code, here are some things to consider.

Testing

Each project in the solution has a matching one for unit tests. To run these tests, simply install the xUnit.net runner for Visual Studio 2012 and 2013 extension.

We try to keep code coverage at 100%. If you have a version of Visual Studio that supports it, open the Test > Test Settings > Select Test Settings File window and select the CodeCoverage.runsettings file located in the Solution Items folder.

Development Certificate

This library uses X.509-based digital signatures. In order to run the tests, you will need to create a self-signed certificate. To do so, run the Developer Command Prompt as Administrator and execute the following command:

makecert -r -pe -n "CN=Georadix Development" -ss trustedpeople -sr currentuser -sky signature -eku 1.3.6.1.5.5.7.3.1 -len 2048 -m 60

Local NuGet Feed

If you make code changes and want to test the updated NuGet packages without first committing to the repository, do the following:

1. In Visual Studio go to Tools > NuGet Package Manager > Package Manager Settings.
2. Select the Package Sources node and click the Add button.
3. Give it a name (e.g. Local Georadix.NET) and set the Source to the LocalNuGetFeed folder in the repository on your local machine.
4. Update your local copy of the CommonAssemblyInfo.cs file by manually setting the version to a number greater than the current package version you are using in the other project.

When you build Georadix.NET, it automatically creates NuGet packages and stores them in the LocalNuGetFeed folder. You can therefore open the Manage NuGet Packages for Solution menu in your other project, select your local Georadix.NET feed, and see the newly created packages. Once you are done testing in this way however, you must revert your changes and delete the package cache in order to get the updated packages from the original feed.