This project is read-only.

Upgrade the project to Visual Studio 2013 goal

Jan 31, 2015 at 12:10 PM
Edited Feb 2, 2015 at 9:14 PM
I will start converting this project to Visual Studio 2013. The impetus behind this is to reduce barriers of getting involved in this project by making it easier for everyone (including me) to simply "get the latest version".

A broad outline of the tasks to work towards this goal include:
  1. Upgrade solution and projects to VS2013.
    The release of Visual Studio Community 2013 provides a good and available development and testing platform. Upgrading the solution and projects to VS2013 will help make it easier for people to be involved in the project.
  2. Remove the setup project.
    The setup project is no longer supported by VS2013. Alternatives may need to be investigated.
  3. Replace the Ascend GradientPanel control with standard Panel.
    The installation requirement of the Ascend GradientPanel control is an initial barrier to developers and testers. It is easily replaced by the standard Panel control.
  4. Replace Scintilla code with DLL references.
    The ScintillaNET code unnecessarily complicates the project and should ultimately be replaced by a Scintilla nuget package.
    Unfortunately, there is no Scintilla nuget package, so references to Scintilla DLLs will replace the code. The installation of the DLLs is a little awkward and should be documented or automated.
  5. Upgrade cleanup.
    There are a few small tasks to complete the upgrade to Visual Studio 2013:
    • Delete one of the duplicate control instantiation of PrincipalForm.btnCompareTableData otherwise the form will not editable in Visual Studio.
    • Delete upgrade file UpgradeLog.htm which was checked in only as a historical reference.
    • Delete empty test template files which are not supported by VS2013.
The final state of the project after carrying out these tasks should be a fully editable and compilable solution in VS2013.

Edit: Added step 5. Upgrade cleanup.
Jan 31, 2015 at 10:29 PM
Awesome, especially how you're communicating everything so well!

Here's the issue for anyone who wants to follow along:
Feb 5, 2015 at 5:10 PM
I have been using past-tense style commit messages. However today I learned that it is a widely accepted style to use present-tense imperative-style commit messages. See A Note About Git Commit Messages and Should I use past or present tense in git commit messages?.

I shall change my commit messages style.