| T O P I C R E V I E W |
| jjlucsy |
Posted - Apr 01 2005 : 10:33:33 AM
In a C# file, if I use:
string x=@"
{#";
it will fail to parse beyond that line and fail to show any context beyond that point.
This sequence is the minimum needed to observe the problem. There can be text between the { and # and it will still fail. I was constructing CSS styles in code and is causing a small amount of grief.
Various Info:
VA_X.dll file version 10.1.1293.0
VAOpsWin.dll version 1.2.0.4
DevEnv.exe version 7.10.3077.0
msenv.dll version 7.10.3077.0
Font: Arial Monospaced 13(Pixels)
Comctl32.dll version 5.82.2900.2180
WindowsNT 5.1 Build 2600 Service Pack 2
Single processor
|
| 4 L A T E S T R E P L I E S (Newest First) |
| support |
Posted - Jan 17 2006 : 9:03:16 PM
Fixed in 1440. |
| feline |
Posted - Apr 04 2005 : 2:36:26 PM
*ah* i got the impression this was effecting more things than just the alt_m list.
i am glad you were able to work around this easily enough  |
| jjlucsy |
Posted - Apr 01 2005 : 2:44:23 PM
Yes, the alt-m list. Sorry. I worked around it by using a different character and replacing it later. I was just reporting it so it can be fixed, not that I couldn't work with or around it. Thanks. |
| feline |
Posted - Apr 01 2005 : 2:38:47 PM
placing this string into a C# file breaks the alt_m list. no functions below this string are shown in this list.
case=551
as a work around can you use "\\n" in a non literal string? for me this fixes the problem.
using your string the VA context and definition fields still update correctly for me when i sit in functions further down the file. your post reads as if these don't work for you. i am using .NET 2003 with VA 1299.
can you confirm that they do break? what other problems are you seeing? it is possible we need a more complex example to see all of the problems. |
