The 'ExmplPositionCtrlPID.sln_BACK' contains the Visual Studio project.
But it must not be used in this directory.
This is because the IDE creates a lot of Megabyte files which are only temporary.
This files should not be merged with the sources.
It's a problem of MS Visual Studio with wide acceptance of most users. 

copy the content of this directory to
.../IDE/$CMPN/IDE_MSC/* beside '.../src/$CMPN/IDE_MSC...
or better copy as hard link using '+spawn....bat' to work with Visual Studio in the IDE directory.
The '*.sln_BACK' is / should be stored as '.../IDE/$CMPN/IDE_MSC/*.sln'

The reason is: do never merge sources and objects in the same folder tree. 
The Visual Studio project creates its outputs (artefacts) beside the projekt directory.
Think about fast zip copy and such. Do not create trash in the src folder!
Thats why it should not be used on this position.

copy, maybe adapt and use '+clean_mkLink_build.bat' to work if possible on a RAM disk.

After changes the content of the project file may be necessary to synchronized 
with this '*.sln_BACK' as well as the '*.vcxproj' and '*.vcxproj.filter'
by copying its content, if the hard link is broken.

Information: 
A hard linked file is only one file on your hard disk, which is referred by more as one directory entries.
This is a concept given also on old UNIX systems, any time available on Linux, and introduced 
in Windows beginning with Windows-XP, but rarely documented. It is supported by MS Visual Studio 
and also Codeblocks, but often ordinary text editors break the hard link. 
Because there working approach were designed in times of DOS and older Windows versions.
Hard links were not broken on working approaches for files: __open - read - modify/write - close__. 
But text editors works often in the working approach __open - read - close__ and later
__open - write (create new) - close__. This creates a new file, non related to the original
and hence breaks the hard link.
