Home/ Questions/Q 6157543
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-23T20:48:15+00:00

I work with the same Visual Studio projects on multiple computers (work/home) using Dropbox

  • 0

I work with the same Visual Studio projects on multiple computers (work/home) using Dropbox to sync between the two. Because VS creates some extra large files, I used to remove the following before uploading to Dropbox:

  • Files = .pdb, sdf, .ilk .exe .tmp
  • Folders = ipch/, Release/, Debug/, GeneratedFiles/

Everything worked fine in the past, however, some problems have now risen.
I receive the following errors:

Moc'ing CodeInterface.h...
1>  The system cannot find the path specified.
1>  Moc'ing ThreadWorker.h...
1>  The system cannot find the path specified.
1>  Rcc'ing StreamAnalyser.qrc...
1>  The system cannot find the path specified.
1>C:\Program Files\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets(151,5): error MSB6006: "cmd.exe" exited with code 3.

So, I think I may have to create a new Visual Studio project and import the classes manually. So my question are:

  • Best practices for working with projects on different computers?
  • What files can be deleted (for uploading to Dropbox)?
  • Does Visual Studio have some sort of ‘global settings’ (or something similar to ‘workspace’ used with Eclipse)? How do I set these settings to prevent trouble when working on different computers?

Thanks!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I am not familiar with dropbox so I can’t speak for what you do currently

    What I like to do is to use a distributed versioning system (I use git) to look after the source code only. I use a .gitignore file to not version any object code and visual studio project files and the like. I can then clone these projects (with their versioning) easily across to any computer I like – including test branches that I might idly play with when coming home on the train on my laptop.

    In my experience visual studio project files are a pain because different versions do not play nicely with eachother (1 computer has vs2005 and another has vs2008). To overcome this problem I like to use cmake as my build system (I include these in my git repository too). Cmake is a ‘meta-build system’, in that it generates the visual studio, or eclipse, or autotools make files for you, and then you do the native build in VS or Eclipse or with make.

    Using these two packages together means that you can copy properly versioned controlled source code between any computer (including linux, mac and windows) and then build the source code natively on that computer, using whatever IDE you have installed on that computer.

    • 0