| T O P I C R E V I E W |
| Harald |
Posted - Jan 11 2006 : 11:55:00 AM
VA_X.dll file version 10.2.1438.0 built 2005.12.16
Licensed to:
VA X: x@x (1-user license) Support ends 2006.11.26
VA.NET 7.1:
VAOpsWin.dll version 1.3.1.9
VATE.dll version 1.0.4.11
DevEnv.exe version 8.0.50727.42
msenv.dll version 8.0.50727.42
Font: Letter Gothic MT 15(Pixels)
Comctl32.dll version 6.0.2900.2180
WindowsNT 5.1 Build 2600 Service Pack 2
2 processors
Platform: Win32
Stable Includes:
C:\\DirectX SDK\\Include;
C:\\Libs\\Intel\\IPP\\include;
C:\\Libs\\FreeImage\\Dist;
C:\\ActiveProjects\\MyLib;
C:\\Program Files\\Microsoft Visual Studio 8\\VC\\include;
C:\\Program Files\\Microsoft Visual Studio 8\\VC\\atlmfc\\include;
C:\\Program Files\\Microsoft Visual Studio 8\\VC\\PlatformSDK\\include;
C:\\Program Files\\Microsoft Visual Studio 8\\SDK\\v2.0\\include;
Library Includes:
C:\\Program Files\\Microsoft Visual Studio 8\\VC\\atlmfc\\src\\mfc;
C:\\Program Files\\Microsoft Visual Studio 8\\VC\\atlmfc\\src\\mfcm;
C:\\Program Files\\Microsoft Visual Studio 8\\VC\\atlmfc\\src\\atl;
C:\\Program Files\\Microsoft Visual Studio 8\\VC\\crt\\src;
Microsoft Visual Studio 2005, english version
Version 8.0.50727.42 (RTM.050727-4200)
Microsoft .NET Framework
Version 2.0.50727
i'm currently working on a C# project. when i stopped yesterday, VAX was working like a charme. today it doesn't. i haven't changed any settings. autotext and suggestions won't work. syntax coloring still does. i can call up autotext explicitly and then it works but it is not offered while i type.
left the ide and restarted of course but no change.
as a test i switched to an old C++ project and VAX works fine.
switched back to the C# project - still won't work.
that's really all i can say. i realize it ain't much in terms of a description but i am really puzzled. i am sure i did not touch any settings, neither in VS nor in VAX. i just started the ide and saw the problem...
just did some more checking:
problem only occurs with the main cs file i'm working on (of course - murphy) but not in other cs files of the same project.
seems VAX lost the info for that file. when i click on a method VAX doesn't display any info in it's toolbar, also no methods are available to choose from in the VAX drop-list. VS drop-list works fine.
initiated a re-parsing in the VAX options. even restarted computer - didn't help.
can i manually delete some VAX files or otherwise force a re-parsing?
|
| 5 L A T E S T R E P L I E S (Newest First) |
| support |
Posted - Jan 17 2006 : 9:03:32 PM
Fixed in 1440. |
| support |
Posted - Jan 11 2006 : 5:24:34 PM
We can reproduce the problem and will get a fix soon.
Thank you for your detective work.
case==551 |
| Harald |
Posted - Jan 11 2006 : 4:36:46 PM
i had two @"" type strings in the code:
@"C:\\temp\\"
this one was right at the beginning of the class, assigned to a variable.
@"C:\\M\\n\\csi5.txt"
this one was in the last third of the file at the beginning of a method.
i just verified that the first one throws the VAX parser off.
the second one apparently didn't do any harm as VAX worked fine with the code that came after it.
changing the first one to "C:\\\\temp\\\\" fixed the problem.
here are the first lines in the source file, up to the troublemaker:
using System;
using System.Collections;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Text;
using System.IO;
using System.Windows.Forms;
namespace Renamer
{
public partial class Form1 : Form
{
private string m_Folder = @"C:\\temp\\";
|
| feline |
Posted - Jan 11 2006 : 3:37:47 PM
can you post the literal string that broke VA? the only case i know of is the C# literal string:
string x=@"
{#";
and in this case all that breaks is the alt-m list. even then, the alt-m list still lists functions that are before this point.
this is a known bug that is in our list of things to fix, but if i understand you correctly is a lot less serious than the problem you have encountered.
i agree, what you are seeing should be fixed soon, but first we need to reproduce it. |
| Harald |
Posted - Jan 11 2006 : 3:12:31 PM
just found the cause of the problem:
i had a @"..." string in the code that apparently confuses the VAX parser.
i replaced all @"" strings with standard "" strings et voila: problem disappeared.
this should be fixed asap.
|
