| Author |
 Topic  |
|
|
tidhar
New Member
8 Posts |
 Posted - Apr 17 2005 : 08:49:13 AM
|
Hi,
I recently installed Visual Assist X and I can't access the Options menu.
I'm using Windows NT SP5, Visual Studio 6 SP 4, VA X (don't know the build number since I can't open the Options menu).
I also have WndTabs V3.20 Add-in installed. The WndTabs About menu shows that it detected Visual Assist v6.0.0.1201
I tried both from the toolbar button and from a keyboard shortcut.
Whenever I press the button (or keyboard shortcut) something flickers in the IDE but the Options don't open. |
|
|
WannabeeDeveloper
Tomato Guru
Germany
775 Posts |
Posted - Apr 17 2005 : 11:44:17 AM
|
quote:
Originally posted by tidhar
Visual Assist v6.0.0.1201
Is it 1201 or 1301?
Try to disable WndTabs and see if Visual Assist then works correctly...
Lots of users use both VAX and WndTabs without problems... as long as they use the latest Build of WndTabs...
|
 |
 |
|
|
SvenC
Tomato Guru
Germany
339 Posts |
Posted - Apr 17 2005 : 2:27:28 PM
|
So v6.0.0 is correct?
It seems that tidhar is talking about VA6 not VAX which would be 10.1.0.xxxx
Bye,
SvenC |
|
|
|
tidhar
New Member
8 Posts |
Posted - Apr 17 2005 : 3:26:16 PM
|
It's definitly VAX, it's just WndTabs that detects VA 6.0.0...
I'll try to disable WndTabs and see if it helps. |
|
|
|
tidhar
New Member
8 Posts |
Posted - Apr 18 2005 : 03:18:29 AM
|
Well, I downloaded build 1301, disabled WndTabs, disabled almost all other Add-ins (except ClearCase) and it still doesn't work.
I tried it with and without a workspace open.
The system requirements doesn't show Windows NT as a supported OS, but it says that any version of Windows other then 98 is supported.
It might be because I'm using SP5 and not SP6, many programs require SP6.
I guess until I upgrade to SP6 (or XP) I'll have to live without the Options menu. |
|
|
|
feline
Whole Tomato Software
United Kingdom
19020 Posts |
Posted - Apr 18 2005 : 3:11:48 PM
|
can you try disabling ClearCase and see if this makes a difference?
i don't recognize this one, and a quick google is throwing up an Eclipse plugin as the best guess. |
zen is the art of being at one with the two'ness |
|
|
|
tidhar
New Member
8 Posts |
Posted - Apr 19 2005 : 02:56:55 AM
|
No luck with disabling ClearCase as well.
(If you meant that you don't recognize ClearCase, it's a Source Control tool from Rational Software, similar to SourceSafe - but better :)
I also have BoundsChecker installed, but I haven't tried to uninstall it yet. |
|
|
|
support
Whole Tomato Software
5566 Posts |
Posted - Apr 19 2005 : 2:42:29 PM
|
Our options DLL fails to load. It's not compatible with NT 4. This is the reason NT 4 is not listed in our supported platforms.
The workaround is to install the latest build of VA X then replace its options DLL with the one from our build 1246. While you do not get the latest tweaks to our UI, you can still run without trouble. (We have several other users in this situation.)
Get build 1246 of our options DLL from:
http://www.wholetomato.com/downloads/VAOpsWin1246.dll
Remove "1246" from the basename when you move it to your VA X installation directory.
case=508 |
|
|
|
tidhar
New Member
8 Posts |
Posted - Apr 25 2005 : 04:08:24 AM
|
The new DLL works, I can now open the Options menu.
Thanks. |
|
|
|
Racey
Senior Member
USA
25 Posts |
Posted - Apr 25 2005 : 10:13:41 AM
|
I've been using the work around for several months now. It's not a 100% solution to using VAX on NT, but it's close enough. tidhar, you may see some of the quirks in the form of Visual Studio's Output window disappearing if you have it floating on your display (that is, not docked). If this happens, don't panic. Just click on the screen and it will reappear. I think some other popup menus are affected as well, such as with WndTabs tab controls. I find this a minor annoyance compared to the benefits of VAX.  |
|
|
|
tidhar
New Member
8 Posts |
Posted - Apr 25 2005 : 10:17:42 AM
|
I always work with the output window docked, so that's not a problem.
I did see some popup windows that didn't show up until I clicked on the screen, and I guessed it was because of VA.
We'll probably be upgrading to XP sometime in the not so distant future (I hope ) so we won't have to use the workaround. |
|
|
| |
Topic |
|
Topic Locked
