The problem can be reproduced very easily in my case (VA 1559, VS 2005 SP1 running on XP SP2 box): 1. Create new plain Win32 project and name it for example "proj" 2. Add to that project files named "proj.test.h" and "proj.test.cpp"
That's all. Now pressing ALT-O in either "proj.test.h" or "proj.test.cpp" would suggest me both "proj.h" and "proj.cpp" instead of silently switching to correct file. This is how it looks on my machine (I've also provided the file tree of the project for your reference):
- -
What is interesting is that for "proj.h" and "proj.cpp" ALT-O works properly and if I remove dot (.) from problematic file names (i.e. rename them to "projtest.h" and "projtest.cpp") everything also works as expected, without any problems and wiered suggestions.
I am seeing the same effect here. Thank you for the clear description.
case=8177
This only happens if there are files in the solution that match the first section of the problem file name, the section before the first dot. If the file names are more unique then alt-o works correctly on files with two dots in their names.
Is there some reason why you are using file names with two dots in them for you code?
No-no, there are no strong reasons for that. I just like long file names consisting of more than one word to look like that, with a dot separator between words. But with the same success I just can use capital letters for file name, like ProjFile.cpp, and it's really acceptable for me.
I accidently found this strange behavior of VA and decided it might be useful to report it.
That makes sense Personally I use underscores in file names as separators. This works well, and avoids any possible problems due to confusion with multiple dots in file names.
ALT-O problems with specific file name
Posted - Aug 12 2007 : 10:34:15 AM
- 
- 
Personally I use underscores in file names as separators. This works well, and avoids any possible problems due to confusion with multiple dots in file names.