Whole Tomato Software Forums

Whole Tomato Software Forums

All Forums

Visual Assist

Technical Support

Visual Studio Exception

You must be registered to post a reply.
Click here to register.

Screensize:

UserName:

Password:

Format:

Message:

Forum code is on.
Html is off.

[quote][i]Originally posted by Curtis[/i]
[br]I am getting a Visual Studio Exception, the one that asks if you want to send information to Microsoft before continuing on. It happens whenever Visual Assist X attempts to autocomplete (after hitting the Tab key) for a member that is not in scope.

To repeat it, say you have a class declared as follows:

[code]NamespaceMember.ScopingMember.ClassMember
{
    int SomeField;
    string SomeMethod();
}

NamespaceMember.ScopingMember.ClassMember MyVariable;[/code]
[list][*]Then, after you've been working with the NamespaceMember.ScopingMember.ClassMember combination for awhile, letting VAX build up its (cache?), you type "ScopingMember." <note the "." and no "NamespaceMember".[/*][*]VAX will offer "ClassMember" in a list.[/*][*]If you highlight "ClassMember" and hit TAB (or ENTER), Visual Studio will throw an exception.[/*][/list]

This has happened to me countless times and i just figured out how to make it happen.

Here's the VAX info:
-------------------------------
VA_X.dll file version 10.3.1532.0  built 2006.08.10
VAOpsWin.dll version 1.3.3.6
VATE.dll version 1.0.5.8
DevEnv.exe version 8.0.50727.42
msenv.dll version 8.0.50727.42
Font: Courier New 13(Pixels)
Comctl32.dll version 6.0.2900.2180
Windows XP 5.1 Build 2600 Service Pack 2
2 processors
-----------------------------

And one other thing: in the Visual Assist X Options window, the "License" and "About" tree nodes are crossed. The "License" information is in the "About" area and vice versa.

Curtis
[/quote]

Check to include your profile signature.
Check to subscribe to this topic.

T O P I C R E V I E W
Curtis	Posted - Sep 11 2006 : 11:15:24 AM I am getting a Visual Studio Exception, the one that asks if you want to send information to Microsoft before continuing on. It happens whenever Visual Assist X attempts to autocomplete (after hitting the Tab key) for a member that is not in scope. To repeat it, say you have a class declared as follows: NamespaceMember.ScopingMember.ClassMember { int SomeField; string SomeMethod(); } NamespaceMember.ScopingMember.ClassMember MyVariable; Then, after you've been working with the NamespaceMember.ScopingMember.ClassMember combination for awhile, letting VAX build up its (cache?), you type "ScopingMember." <note the "." and no "NamespaceMember". VAX will offer "ClassMember" in a list. If you highlight "ClassMember" and hit TAB (or ENTER), Visual Studio will throw an exception. This has happened to me countless times and i just figured out how to make it happen. Here's the VAX info: ------------------------------- VA_X.dll file version 10.3.1532.0 built 2006.08.10 VAOpsWin.dll version 1.3.3.6 VATE.dll version 1.0.5.8 DevEnv.exe version 8.0.50727.42 msenv.dll version 8.0.50727.42 Font: Courier New 13(Pixels) Comctl32.dll version 6.0.2900.2180 Windows XP 5.1 Build 2600 Service Pack 2 2 processors ----------------------------- And one other thing: in the Visual Assist X Options window, the "License" and "About" tree nodes are crossed. The "License" information is in the "About" area and vice versa. Curtis
2 L A T E S T R E P L I E S (Newest First)
feline	Posted - Sep 17 2006 : 12:20:16 PM i am not quite sure what you are doing with your code. is this C++ or C# ? assuming this is C++ for the moment, i can see the header file having: namespace feline { class chocolate { int SomeField; string SomeMethod(); } } and the cpp file having: static void testThings() { feline::chocolate foo; foo.\| } but where does your item "ScopingMember" come from? are you using a namespace inside a namespace? do you have a sample piece of code that causes this exception that you can post?
jpizzi	Posted - Sep 11 2006 : 11:18:34 PM Your note about the "About" and "License" dialogs being reversed is interesting. I can see how you think they are reversed, but this is the way they are intended to be. I think I will suggest that one or the other be renamed. case=2470

Snitz Forums 2000