Missing CONTRIBUTION.md about g-cli HOT 3 CLOSED

Hi Hoffiz,

Sure that makes sense. I keep meaning to work on a template contribution guide for my LabVIEW projects anyway so I will get to it ASAP.

There will be a problem trying to use the cloned version for real use and you should use the VIPM. The reason is the VIPM will install to vi.lib which is where all dependent packages will look for it. The structures are different since this repository also contains source for the C# application.

LV version is 2011.

from g-cli.

Resolved with version 2.0

from g-cli.

Thanks @JamesMc86. I appreciate the reply and no rush.

I need to clean the documentation a bit but I think I come up with a pretty clean setup for contributing to the 2 major players needed for LabVIEW continuous integration. LabVIEW-CLI C#/VIs and the DCAF common steps.

VBOX machine, using VS 2017 Community and LV 2017 I'm able to rebuild your exe, I added the bin/debug to the path and tested a few dummy modifications. The only drawback is that I pushed the source to 2017 although I could revert it,.... but for now I will leave the source in 2017.

from g-cli.