On Fri, Jan 20, 2012 at 9:17 AM, Robert Dailey wrote:
> Any thoughts on this guys? Here are my ideas for this:
>
> For VS8 and VS9:
>
> CMake will only generate the my_project.vcproj.user files. Visual Studio
> will NOT use these unless you delete your *other* user file, which is in
> the format
Any thoughts on this guys? Here are my ideas for this:
For VS8 and VS9:
CMake will only generate the my_project.vcproj.user files. Visual Studio
will NOT use these unless you delete your *other* user file, which is in
the format of: my_project.vcproj.COMPUTER.USER.user. If the user wishes to
have
I would be fine with that if the generation of these files would only
happen if either they weren't present or you manually forced them to be
created. Folks are just used to modifying them in the VS IDE, and it would
be too easy for users to make a change in the IDE and then have CMake
overwrite t
Or you could just change the properties as normal in the VS options dialog,
until you find settings that work and you want to keep. Then update the
cache variables or whatnot in CMake, so next time you generate you will
have them.
There is nothing preventing you from using the normal method of cha
On Wed, Jan 11, 2012 at 8:41 AM, David Cole wrote:
> I'm sure there are a handful of interested parties on this topic.
>
> One concern I would have is that if we start to generate this, we
> might clobber stuff that users go in and edit by hand in the Visual
> Studio UI. It's a minor concern, but
For VS8-VS9, this won't be a big issue since Visual Studio does not use the
.user file directly, instead it copies it and creates a DOMAIN.USER.user
file instead. For VS10, however, it does not do this, so when we edit the
.user file it will use that file directly. I think VS10 is the only version
In light of the current topic about copying 3rd Party DLLs into the build
directory on Visual Studio one suggestion was to create this type of file. With
that in mind I am now interested in this feature. Would make a nice addition
and help those of us who do 32/64 dev all on the same machine whe
I'm sure there are a handful of interested parties on this topic.
One concern I would have is that if we start to generate this, we
might clobber stuff that users go in and edit by hand in the Visual
Studio UI. It's a minor concern, but if I do go in and add a
"PATH=1;2;3;4" to the environment, th
I guess I have failed to strike the interest of anyone on this?
-
Robert Dailey
On Mon, Jan 9, 2012 at 5:58 PM, Robert Dailey wrote:
> there are .user files generated by newer versions of Visual Studio (since
> 2005 I believe) that contain per-machine or per-workspace information. For
there are .user files generated by newer versions of Visual Studio (since
2005 I believe) that contain per-machine or per-workspace information. For
all intents and purposes these are temporary files that are not checked
into version control.
The normal file naming convention for these are:
proje
10 matches
Mail list logo
