| Author |
 Topic  |
|
|
JefferyS
Senior Member
USA
32 Posts |
 Posted - Oct 05 2009 : 01:17:33 AM
|
Using VS 2008 sp1 on Vista Ultimate 64bit
First my braces ( { [ etc disappear in my asp.net C# code behind page when the cursor is inside the braces. It may just be set to a black color but I went through the VS options for colors and didn't find any thing that was set wrong. The braces are actually set to yellow. The VAX colors are not enabled.
Second, a little while back I reported that an option in the VS options was being changed, it had been fixed up to 1736 but 1738 caused it to change again. It unchecked "Insert attribute value quotes when typing".
Options/Text Editor/HTML/Format/
Thanks,
JefferyS
|
|
|
Nobodo
Tomato Guru
126 Posts |
Posted - Oct 05 2009 : 11:01:27 AM
|
Jeffry, I saw exactly the same thing you are seeing on the braces, but for me it was when I upgraded to 1736. I found that I had to actually go into the VS color settings and change 'Brace Matching (Highight)', 'Brace Matching (Rectangle)', and 'VA X Brace Matching'. For me at least, there appears to be some type of interaction among these 3 settings that started with 1736 but did not appear before that.
Hope that helps!
Mark. |
 |
|
|
JefferyS
Senior Member
USA
32 Posts |
Posted - Oct 05 2009 : 12:01:19 PM
|
Thanks for the reply Nobodo, but that didn't work. I changed my background color and the braces are showing as black, I've changed the colors in visual studio and vax for them but it didn't help. If I disable the coloring of the braces in VAX they will show up like normal.
Sometimes I get a message fro VAX: "Visual Studio has not completed initializing some Visual Assist X features. Color changes made in the Visual Assist X Options dialog may not take effect until you restart Visual Studio to complete initialization."
I even opened a small project before changing the colors so I'm not sure why it is taking so long to initialize.
JefferyS
|
|
|
|
feline
Whole Tomato Software
United Kingdom
19024 Posts |
Posted - Oct 05 2009 : 1:49:04 PM
|
I have seen the error message you mention, but only once. I think this happens when VA needs to restart the IDE to successfully add its items to the IDE's list of items in the fonts and colors list. But that should only require a single IDE restart.
So far I cannot reproduce the problem with the IDE HTML formatting option being unticked when installing VA 1738.
I am also not seeing any problems with bracket highlighting in a C# ASP web application project.
Can you please export your VA and IDE settings and send them to me:
VA Options -> Performance -> Export Settings
IDE tools menu -> Import and Export Settings -> Export selected environment settings
I can then import them here and see if I can reproduce the problem. It is possible the two effects you are seeing are interconnected.
Please submit the files via the form:
http://www.wholetomato.com/support/contact.asp
including this thread ID or URL in the description, so we can match it up. |
zen is the art of being at one with the two'ness |
|
|
|
sean
Whole Tomato Software
USA
2817 Posts |
|
|
JefferyS
Senior Member
USA
32 Posts |
|
|
feline
Whole Tomato Software
United Kingdom
19024 Posts |
Posted - Oct 06 2009 : 5:39:21 PM
|
I have your settings, thank you for these. I have applied these to VS2008 on a Vista 64bit test system. I then created a new default C# ASP.NET web application project. When I open the file "Default.aspx.designer.cs" this is what I am seeing, note the highlighted and non highlighted bracket:
I am not sure why the highlighted backet is italic, is this what you are expecting on your system? This is a test machine so it has an interesting history. |
zen is the art of being at one with the two'ness |
|
|
|
JefferyS
Senior Member
USA
32 Posts |
Posted - Oct 07 2009 : 12:40:34 AM
|
Except for being italic that is what I was seeing before installing 1738. Today I uninstalled and reinstalled 1738, reset all of visual studio back to default settings, uninstalled and installed the last general release I think 1727, and still not working correctly. The braces stay black and do not change color when the cursor is between the braces.
I had though the VS 2008 had highlighted the braces so I uninstalled VAX. But that didn't work either. From what I have read online the Brace Matching(Highlight) doesn't do what it says. It seams to only work for html & asp.net tags, maybe a few other things.
I found a Sara Ford's Weblog and she says it's for "Customizing the Automatic Delimiter Highlighting". But then I found on msdn.microsoft.com a page that say in the Text Editor/General options is Automatic Brace Matching, but the only thing in the options is Automatic delimiter Highlighting, It seams there is some confusion on this.
Continuing a few hours later...
I think I may have the problem. I had a windows 7 rtm test computer that had vs2008 team system loaded on it. I loaded VAX 1738 and it seam to work just fine so I started going through the registry and found that in HKEY_CURRENT_USER\\Software\\Microsoft\\VisualStudio\\9.0\\FontAndColors\\{A27B4E24-A735-4D1D-B8E7-9716E1E3D8E0} there were no entries for VAX on my computer. So I exported from the windows 7 and imported that registry key on my computer and it started working correctly, sort of. It seams what ever happened that VAX is not updating the above key. If I manually change a color in the registry It will change in visual studio.
I don't know if this helps and I'm not sure why its not working correctly. I don't know what to do next. Should I uninstall vax and visual studio and reinstall? It's a real pain to get everything back to what it was. Any thoughts, maybe now would be a good time to move to Windows 7.
Thanks,
JefferyS
|
|
|
|
feline
Whole Tomato Software
United Kingdom
19024 Posts |
Posted - Oct 07 2009 : 3:39:53 PM
|
Before we try that, can you try a quick and simple test. Make sure all instances of the IDE are closed, and then run regedit and delete the registry key:
HKEY_CURRENT_USER\\Software\\Microsoft\\VisualStudio\\9.0\\FontAndColors\\Cache\
this key will be rebuild by the IDE. Does this help?
It almost sounds like the IDE, or perhaps VA, has no idea what the colours are for highlighting matching brackets, so no highlighting is taking place. If so this might help. |
zen is the art of being at one with the two'ness |
|
|
|
JefferyS
Senior Member
USA
32 Posts |
Posted - Oct 08 2009 : 10:46:22 AM
|
That didn't fix the problem.
But I think I managed to fix it. Not really a fix, this is a strange deal. I thought maybe one of my add-on's was conflicting with VAX. So I disabled all but VAX and some VS debugger thing from starting up. I restarted VS and was able to get VAX to work correctly. It put the VAX entries in the Font and color section of the registry(had deleted the ones I put in manually) and was able to change colors to the braces. Didn't even get that error message about having to restart VS. So one by one I enabled the add-on's (about 6 of them) and kept changing the braces color. Got to the last one and I thought this must be the one. I enabled it to start up. Restarted VS and test it out. VAX worked just fine. I was able to change a lot of color settings and it would save them. Never got the "you will have to restart VS" messages. Changed the colors multiple times without restarting VS. I couldn't get it to fail.
So now I have my VS setting all back before the problem(imported them) and all my add-on's are enabled and VAX seams to be working just fine now. Go figure.
I have no clue what could have gone wrong. Maybe it was just a fluke that when I installed 1738 something got messed up. The installation went just fine so I don't know. I'm just glad it's working.
Thanks,
JefferyS
|
|
|
|
feline
Whole Tomato Software
United Kingdom
19024 Posts |
Posted - Oct 08 2009 : 1:23:40 PM
|
Very occasionally I have seen a conflict between VA and the ResOrg IDE plugin. This particular conflict is fixed by uninstalling both plugin's and then reinstalling ResOrg first, and then reinstalling VA second.
It sounds like something slightly similar is happening here, where the order of plugins matters. At a wild guess one of the other plugin's was blocking or overwriting VA's registry changes. When that other plugin was disabled VA was able to make the required changes correctly, fixing your problem. |
zen is the art of being at one with the two'ness |
|
|
|
support
Whole Tomato Software
5566 Posts |
Posted - Jan 31 2010 : 1:37:19 PM
|
| build 1810 contains a workaround for case=31894 |
Whole Tomato Software, Inc. |
|
|
| |
Topic |
|
I have two problems after upgrading to 1738
