So long as you do a "move" on the files, and the
check-in shows as a rename/move, then everything
should just work. When the other devs do a Get
Latest it will move their file keeping their
pending changes in tact.
What you want to avoid is TFS detecting it as a
delete+add instead of a move.
It's most likely coming from the conversion
because there is nothing in VRML that would imply
it's lower resolution than OBJ, it's a very good
Try converting using AOPT instead; it's a
commandline utility, which is useful for
aopt -i from.obj -e to.wrl
You need to have a "release branch" in your source
control tool and a release build. You merge your
code to the release branch so that it's the same
version and then you rebuild the source tree using
the desired version #.
By default, NCrunch will always start as disabled
for a solution before it is explicitly turned on
from the top menu.
You can toggle Ncrunch on and off from the by
selecting Enable from the NCrunch Visual Studio
There is also a global configuration file that has
many config settings that you can use.
Common Properties -> References
Link Library Dependencies in Linker or Librarian
section. This assumes that Project Dependencies
have been setup.
#pragma comment(lib...) is playing some role
While it's not very clearly stated you can in fact
use relative paths for the target location path
(at least for File System publish). You'll have to
play with it a little to get the right relative
reference to the target. For example,
A relative location of ".Release" will create:
That said... I do not think that you really should