Author |
Topic |
|
SvenC
Tomato Guru
Germany
339 Posts |
Posted - Mar 03 2005 : 08:46:21 AM
|
Hi,
I have VC++ 2003 solutions where it does make a difference if I open up the sln file from the Windows Explorer or from VS2003 through File->Open Solution.
By double clicking on the sln file from Windows Explorer the enhanced syntax coloring does not work. Disabling/Enabling VAX does not change anything. I tried to rebuild the symbols, I deleted the ncb file nothing changes. Opening the very same solution from VS2003 through File->Open Solution gives me the expected enhanced syntax coloring.
This does not happen for every project. Currently I can reproduce this only for Win32 dll projects (Windows installer custom action dlls to be precise). ATL/COM projects behave normally no matter how I open them.
I use VAX 1293 in VS.NET 2003 on Windows Server 2003.
Any ideas?
SvenC |
|
WannabeeDeveloper
Tomato Guru
Germany
775 Posts |
Posted - Mar 03 2005 : 09:06:31 AM
|
Weird.
Could you provide a small project that shows this behaviour?
Please mail it to [email protected]
|
|
|
|
SvenC
Tomato Guru
Germany
339 Posts |
Posted - Mar 03 2005 : 12:29:26 PM
|
Just sent the sample solution. Hope it behaves just like on my machine... |
|
|
WannabeeDeveloper
Tomato Guru
Germany
775 Posts |
Posted - Mar 03 2005 : 2:51:41 PM
|
At first, I noticed that it took a huge amount of time to load the solution (first time only). After loading (and VAX parsing all my include-folders, cause "it was time again"), HyMsiExec.cpp is opened automagically.
It is enhanced-colored on my system when I doubleclick the solution.
I cross-checked it with opening the file through the meu-command (File -> Open...), which is also colored right from the start.
BUT (and now comes the weirdness), when I open the solution from within the IDE, I cannot get the "Show local symbols in BOLD" to work, no matter what I try...
case=522 |
|
|
|
SvenC
Tomato Guru
Germany
339 Posts |
Posted - Mar 04 2005 : 3:35:52 PM
|
I did some more testing and it seems that only solutions under my path D:\\projects\\setups\\ do show this behaviour. "setups" is the import part of the path.
I copied a solution to D:\\temp and enhanced syntax coloring worked no matter how I opened the solution. So D:\\projetcs\\setups\\HypMsiExec\\HypMsiExec.sln fails to use enhanced syntax coloring when opened through double clicking the sln file. But it works when it is double clicked from D:\\temp\\HypMsiExec\\HypMsiExec.sln
Strange, isn't it? |
|
|
patria
Junior Member
20 Posts |
Posted - Mar 15 2005 : 12:46:14 AM
|
I also have such a strange behavior.
Whenever the full path name of the solution file (sln) contains "setup" string, syntax coloring is gone.
"c:\\dev\\src\\setuphlp\\setuphlp.sln", for example. If I change the path to "c:\\dev\\src\\other\\setuphlp.sln", then it works fine.
|
|
|
WannabeeDeveloper
Tomato Guru
Germany
775 Posts |
Posted - Mar 15 2005 : 05:05:17 AM
|
Yup, confirmed behaviour.
"Setup" somewhere in the Path kills Syntax Coloring. |
|
|
|
hensz
Senior Member
Germany
26 Posts |
Posted - Apr 18 2005 : 05:00:17 AM
|
quote: Originally posted by patria
Whenever the full path name of the solution file (sln) contains "setup" string, syntax coloring is gone. If I change the path to "c:\\dev\\src\\other\\setuphlp.sln", then it works fine.
Not here! Only after I renamed my solution so that its name didn't contain 'setup' the problem is gone. Is this a bug in VAX or in Visual Studio?
CU, Hensz |
|
|
WannabeeDeveloper
Tomato Guru
Germany
775 Posts |
Posted - Apr 18 2005 : 05:44:33 AM
|
quote: Originally posted by hensz Is this a bug in VAX or in Visual Studio?
Since we assigned a case for it and it deals with Enhanced Syntax Coloring (= a VAX Feature only), it is a VAX Bug... well, at least I am sure that it is... |
|
|
|
geguman
Starting Member
Korea
1 Posts |
Posted - May 31 2005 : 07:55:50 AM
|
I could solve this problem by changing foreground letter color to customized color( set to same color with fixed color you choose )
tool -> option -> environment -> font&color
Sorry for my poor english. I'm korean. I guess there is nobody understood. I hope my reply help you.
bye~ |
|
|
WannabeeDeveloper
Tomato Guru
Germany
775 Posts |
Posted - May 31 2005 : 08:06:41 AM
|
We already have a fix in the works, should be within the next build ( > 1409). |
|
|
|
|
Topic |
|