Project settings saved per user?

[Raoul_S_]

Hi,

I am using Visual Studio 2013 update 4 and IVF package 2015.1.148

I have noticed that some project settings are saved per user, not per project. If I create a new DLL project called "MyDLL", Visual Studio creates a file named MyDLL.vfproj.UserName.user (where UserName is my windows login name). Some settings seem to be written only to that file, not to the MyDLL.vfproj file. One example is the debugging command.

Was this intended? Is there any way to save that setting as part of the project itself and not per user? This is not really convenient when sharing projects between users.

Thank you.

[Steven_L_Intel1]

This is by design in Visual Studio. Debugging options (commands, breakpoints, etc.) are not considered project options but rather user options. I admit that the way this works is a bit mysterious to me - often I can pick up a solution that a customer sends me and I see the debugging command and the breakpoints, and other times they don't come through. I'm going to ask the developers for an explanation of how this works and if there's a way to keep all the options together.

[Raoul_S_]

Thanks, at least I know it's not just some weird thing happening on my machine only.

It does make sense to me to save breakpoints in a different file from compiler settings. Somehow in my own logic the debugging command goes with the compiler settings and not with the breakpoints, but I can easily see how it can be different for others.