| Author |
 Topic  |
|
|
.oisyn
Tomato Guru
162 Posts |
 Posted - Jul 13 2009 : 7:09:46 PM
|
Is there any way I can unregister the Visual Assist addin for VS 2010? Because it's not working properly (and I don't expect it to), but even worse, it crashes a lot, making testing the new features of VS 2010 pretty undoable for me. Simply disabling VAX from the menu doesn't work.
Uninstalling VAX altogether is not an option because I still want to use it in VS 2008 :) |
Edited by - .oisyn on Jul 13 2009 7:10:23 PM |
|
|
sean
Whole Tomato Software
USA
2817 Posts |
Posted - Jul 14 2009 : 12:24:30 AM
|
There is no released version of Visual Assist that runs in VS2010. What indications do you have that it is registered for VS2010?
|
 |
|
|
.oisyn
Tomato Guru
162 Posts |
Posted - Jul 14 2009 : 05:03:06 AM
|
The fact that it has the VA X icon in the VS 2010 splash screen, the Visual Assist X menu in the menu bar, the VAX toolbar, and the VAX refactoring context menu. Do you want a screenshot? :)
It even has separate settings in the registry for 2010 (under HKCU/Software/Whole Tomato/VAX/VANet10). I'm on the latest build btw (1727). On my work PC, where I also have VS 2005, 2008 and 2010 beta 1 installed, but with VAX 1724, it doesn't integrate into 2010. |
Edited by - .oisyn on Jul 14 2009 05:06:21 AM |
|
|
|
feline
Whole Tomato Software
United Kingdom
18942 Posts |
Posted - Jul 14 2009 : 10:49:48 AM
|
Are any of the VA commands in the menu ever enabled?
If you had VA working in VS2008 / VS2005 before you installed VS2010 I am wondering if VS2010 simply imported your IDE settings, including the VAssistX menu.
When the IDE crashes is there any sign of VA in the call stack? |
zen is the art of being at one with the two'ness |
|
|
|
sean
Whole Tomato Software
USA
2817 Posts |
Posted - Jul 14 2009 : 1:06:56 PM
|
We'll have to look into this. Not clear how this happened.
Here is a registry script you can run that SHOULD remove VA from VS2010. After running the script, you might need to run "devenv /setup" on the vs2010 version only.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\10.0\\AutoLoadPackages\\{ADFC4E64-0397-11D1-9F4E-00A0C911004F}]
"{44630D46-96B5-488C-8DF9-26E21DB8C1A3}"=-
[HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\10.0\\AutoLoadPackages\\{F1536EF8-92EC-443C-9ED7-FDADF150DA82}]
"{44630D46-96B5-488C-8DF9-26E21DB8C1A3}"=-
[HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\10.0\\Menus]
"{44630D46-96B5-488C-8DF9-26E21DB8C1A3}"=-
[-HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\10.0\\InstalledProducts\\Visual Assist X]
[-HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\10.0\\Packages\\{44630D46-96B5-488C-8DF9-26E21DB8C1A3}]
[-HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\10.0\\Text Editor\\External Markers\\{44C8950D-0CA8-43EA-9B82-0760C1D67520}]
[-HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\10.0\\Text Editor\\External Markers\\{552BAC5B-09E7-4996-B965-DBC642645D16}]
[-HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\10.0\\Text Editor\\External Markers\\{565E4AB5-1F86-463C-852E-011F3421F99F}]
[-HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\10.0\\Text Editor\\External Markers\\{B7763794-9CFD-4C82-A236-A6B8D510216E}]
[-HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\10.0\\Text Editor\\External Markers\\{B7A24D49-CAD8-4436-A764-9C47418A237C}]
[-HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\10.0\\Text Editor\\External Markers\\{C6AD9332-2008-4557-AD30-503B64F56E9B}]
[-HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\10.0\\Text Editor\\External Markers\\{DB587E06-DA42-4318-9CC9-F55D704C5E1C}]
[-HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\10.0\\Text Editor\\External Markers\\{FD9BFB5D-438C-4B25-A9A8-FA2774B2FE5E}]
[-HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\10.0\\ToolWindows\\{32A6260A-0121-4878-95E5-80D2F08EA4CB}]
[-HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\10.0\\ToolWindows\\{6BF43C00-192E-4279-9DD1-C19A4C0AB983}]
[-HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\10.0\\ToolWindows\\{872017FE-B99B-44DF-9F38-F7A581288AA7}]
[-HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\10.0\\ToolWindows\\{8E5C1D1A-8A91-4406-AA56-5BF27C97D63C}]
[-HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\10.0\\ToolWindows\\{B8E0BB07-1A6D-4198-91D6-C3F40B30470A}]
|
|
|
|
sean
Whole Tomato Software
USA
2817 Posts |
Posted - Jul 14 2009 : 1:11:09 PM
|
I should also note that VA can't be active in VS2010 - it looks like the UI has been improperly setup, but no commands should execute - for example the VA option dialog will not display, etc.
As far as the vs2010 crashes are concerned, I don't hold much hope that removing the VA UI elements will have any effect on the stability of 2010b1 (unless VA is appearing in the callstack of the crashes). |
Edited by - sean on Jul 14 2009 1:28:02 PM |
|
|
|
.oisyn
Tomato Guru
162 Posts |
Posted - Jul 15 2009 : 05:52:09 AM
|
quote:
for example the VA option dialog will not display, etc.
It does actually. And when I delete the VANet10 key from the registry and restart the IDE, VAX will recreate the key. I'll try to create a crash log and some screenshots. I'm not talking about UFO's here ;) |
Edited by - .oisyn on Jul 15 2009 05:53:43 AM |
|
|
|
.oisyn
Tomato Guru
162 Posts |
Posted - Jul 15 2009 : 06:15:40 AM
|
Splash screen:
VAX options dialog spawned from within VS 2010
And data from "copy info" button
quote:
VA_X.dll file version 10.5.1727.0 built 2009.06.12
Licensed to:
VA X: *********** (1-user license) Support ends 2010.05.22
DevEnv.exe version 10.0.20506.1
msenv.dll version 10.0.20506.1
Font: Courier New 13(Pixels)
Comctl32.dll version 6.0.3790.3959
Windows Server 2003 5.2 Build 3790 S
2 processors (x86-64;
WOW64)
Platform: Win32
Stable Includes:
C:\\Program Files (x86)\\Microsoft Visual Studio 10.0\\VC\\include;
C:\\Program Files (x86)\\Microsoft Visual Studio 10.0\\VC\\atlmfc\\include;
C:\\Program Files (x86)\\Microsoft SDKs\\Windows\\v7.0A\\include;
C:\\Program Files (x86)\\Microsoft Visual Studio 10.0\\Common7\\IDE\\include;
Other Includes:
Stable Source Directories:
C:\\Program Files (x86)\\Microsoft Visual Studio 10.0\\VC\\atlmfc\\src\\mfc;
C:\\Program Files (x86)\\Microsoft Visual Studio 10.0\\VC\\atlmfc\\src\\mfcm;
C:\\Program Files (x86)\\Microsoft Visual Studio 10.0\\VC\\atlmfc\\src\\atl;
C:\\Program Files (x86)\\Microsoft Visual Studio 10.0\\VC\\crt\\src;
The crashes do not seem to be inside VAX, but it will occur whenever I issue a VAX command (such as goto definition or find references)
(this is just one of the crashes, I've also seen them in ntdll.dll and such, but they are all Access Violations from Microsoft.VisualStudio.OLE.Interop) |
Edited by - .oisyn on Jul 15 2009 06:25:53 AM |
|
|
|
.oisyn
Tomato Guru
162 Posts |
Posted - Jul 15 2009 : 06:27:29 AM
|
| Btw, thanks for the registry script. I'll delay running it for now so I can provide you with additional data if you need it as to how this might have happened. |
Edited by - .oisyn on Jul 15 2009 06:27:52 AM |
|
|
|
sean
Whole Tomato Software
USA
2817 Posts |
Posted - Jul 15 2009 : 2:01:17 PM
|
We've tracked down the problem. case=29669
This problem occurs due to a branching error in December 2008. It occurs if you have installed build 1711 and subsequently install build 1727 (without having uninstalled VA).
Running the registry script will prevent VS2010 from loading VA.
Sorry about that. You can expect full VS2010 support from us - but not in 1727.
|
Edited by - sean on Jul 15 2009 8:32:40 PM |
|
|
| |
Topic |
|
VAX and VS 2010 Beta 1
