Before logging an issue, please update to the latest release of Visual Micro from the Downloads Page.

When Logging a Support Issue in the Forum, please ensure you have also:-

  • Enabled vMicro > Compiler > Show Build Properties
  • Re-Compile your program with these settings enabled
 
Save the new Output to a Text File and....
  • Click the Reply button and attach as .txt file OR
  • Click here to Email us with the file attached, and a link to your post
Support requests without the output above may be impossible to answer, so please help us to help you
 
Page Index Toggle Pages: 1 Send TopicPrint
Normal Topic source control and visual micro projects (Read 1500 times)
matthewcheck
Newbies
*
Offline


Posts: 1
Joined: Dec 27th, 2016
source control and visual micro projects
Dec 27th, 2016 at 11:41am
Print Post  
Hi, i'm pretty new to arduino / visual micro development, but I have experience in software development for a several years. Currently myself and a friend of mine are starting a new arduino project and have tried visual micro, which we find pretty much helpful in comparison with the default Arduino IDE. 

What is troubling us is the way of how visual micro handles changes to files. In particular changes to .vcxproj file. The .vcxproj file itself defines AdditionalIncludeLibraries tag, which consists of absolute paths to specific used libraries. This path in most cases is not the same between multiple developers and it includes a re-commit of the .vcxproj file by every developer that participates on the project. 

Are there any guidelines of how to correctly work with source control for projects handled by Visual Micro? Which files are must-have in the source control and which ones are to be ommited from it?
  
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12187
Location: United Kingdom
Joined: Apr 10th, 2010
Re: source control and visual micro projects
Reply #1 - Dec 27th, 2016 at 1:45pm
Print Post  
Hi,

If you are using arduino compatible projects then you do not need to check the .vcxproj into source control

This is because Arduino doesn't need a project. Visual Micro only uses the project to ensure the correct intellisense and as you see the file is updated each time it opens and also each time you add libs etc. If you think about it this has to make sense because you do not set include or tool "paths", they are always automatically recalculated from the current locations of each pc so that the VS intellisense can work.

It turns out that each developer installs libraries and arduino ide on different drives and/or locations. Therefore relative paths will not work across multiple machines and need to be rebuilt for each pc.

If you are working outside the arduino standard, with local libraries, short cuts to shared sources, with code in sub folders other than the \src folder or with global defines that are not configuration specific then you will need the vcxproj in source control.

Once you understand the dynamic nature of arduino paths, if you can suggest a better way to work then feel free to make a suggestion as this is always being reconsidered. 

  
Back to top
IP Logged
 
Page Index Toggle Pages: 1
Send TopicPrint