-
Notifications
You must be signed in to change notification settings - Fork 60
Building the code
While I try to resolve issues and add features, I do not have the time to do everything, so I provide a guide here how you could build AxoCover and fix issues and add features yourself.
- Working knowledge of C#
- XAML/WPF experience is useful - used by Visual Studio UI
- AxoCover has a little C++ code, but you will probably not touch it
This is what I use. Different versions might also work:
- Visual Studio 2017 - you can use Community for this project, during setup please select: .Net Desktop Development, Desktop Development with C++, Visual Studio Extension Development
- Visual C++ 2012 Build Tools - scroll down for Visual Studio 2012 then sign in with your Microsoft Account, then select Visual Studio 2012 Express for Desktop. Install with default settings, no need to start it or register (free) etc. We only need it to install the build tools for C++.
Why so many old/odd requirements? To be compatible with Visual Studio 2012+ upwards.
Fork project on GitHub with the fork button, then using your favorite git client:
git clone https://github.com/_username_/AxoCover
Go to the source directory open AxoCover.sln and build.
Debugging / starting AxoCover project might fail at first, because of environment differences. To overcome this please open project settings, go to Debug, select Start external program, and point it to your Visual Studio installation, e.g. C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\devenv.exe. This installation can be a different version than what is used to build AxoCover, so you can build your VS2012 Pro based issue from VS2017 Community.
Also you can set the command line arguments to /rootsuffix Exp, this allows to you to experiment without messing up your production setup of Visual Studio.