   Visual Studio keeps renaming my files!!
  If I have two instances of visual studio open where there are edits being applied from both, on occasion, visual studio will rename a file to all lower-case characters. This is not such a big deal except that this literally changes the name of the file in my source control package which makes it essentially disappear.Has anyone else experienced this issue and found any good solutions?Thanks ahead of time.   
  You sure it's visual studio doing it? Doesn't rename anything for me. Might be your version control doing it?;  I've had this before, and yeah it can be frustrating.  I think the cause is that the file you are editing is not in the current solution of one of your visual studio instances.  If you add the file to the solution I think it should fix the issue.  Obviously you may have to do a bit of fiddling if you don't want actually want that file compiled into the solution.  Good luck.   ;  _moagstar_: Unfortunately that's not an option. The reason there are two solutions is that one solution contains the engine code and the other the game logic specific code and that can't change. Since the engine is still in heavy development, I can't just export an SDK and work off that, hence, I'll on occasion change engine code from within the game solution (and switch over the to engine solution to compile).What I may try doing is just creating a new all encompassing solution that contains the project files for both the game and engine and see if that alleviates the issue.Thank you for the suggestions.   ;  Look at a solution as being a 'workspace' - lay out the stuff you need to work with each day, remove as needed.The build output is controlled by the projects, not the solution. So have one solution, put the engine AND game projects in it. Or just the ones you need on a particular day.Think it's messy? Delete the solution when you're done. Easy!As far as I know (correct me if I'm wrong!) the only reason to keep solutions around is if you are using the 'project dependencies' feature. I think it's better to explicitly add dependencies in the project settings and treat solution files as disposable.   ;  VS renames crap to whatever casing is in the project file.Just remove the file from the project. Fix the casing in windows. Re-add the file to the project.This is insanely annoying. Especially when working with a case sensitive version control.;  MrBastard: Indeed, I'm with you 100% here. I do use solution level project dependencies but prefer to be explicit with what I link in anyways so can do without.I'm inclined to believe this is an idiosyncrasy of visual studio that can not be easily resolved (and knowing MS will likely never be). An all-inclusive solution sounds like a sure bet at least for now.Thanks again.   ;Quote:Original post by mrbastardLook at a solution as being a 'workspace' - lay out the stuff you need to work with each day, remove as needed.Fortunately I've never had it rename my files without my permission, since I work on a solution containing about 120 projects, with many dependencies, on a daily basis. We also build the entire product on our build machine from building the solution itself.   