Author |
Topic |
|
tokamak
New Member
3 Posts |
Posted - Jul 05 2006 : 4:22:49 PM
|
System.SystemException: unsupported shell type at VANetObj.Class1.SetShell(String shellType) at VANetObj.Class1.Main(String[] args)
I am starting to get this exception on a regular basis now (this also affects previous builds). Can't get any information of "shellType" though, since the registers are all gone after the exception was thrown.
Any ideas?
|
|
feline
Whole Tomato Software
United Kingdom
19021 Posts |
Posted - Jul 06 2006 : 5:55:30 PM
|
which IDE are you using? when does this happen? when you load the IDE? when you quit the IDE? do you have any other plugin's installed, or a localised IDE or OS? |
zen is the art of being at one with the two'ness |
|
|
tokamak
New Member
3 Posts |
Posted - Jul 06 2006 : 9:14:23 PM
|
quote: Originally posted by feline
which IDE are you using? when does this happen? when you load the IDE? when you quit the IDE? do you have any other plugin's installed, or a localised IDE or OS?
Usually happens right after opening a C# .NET solution.
Both OS and VS are US versions.
Visual Studio Info:
quote: Microsoft Visual Studio 2005 Version 8.0.50727.42 Installed Edition: Enterprise
Installed Products:
Microsoft Visual C# 2005 Microsoft Visual C++ 2005 Microsoft Visual Studio Tools for the Microsoft Office System Microsoft Visual Studio 2005 Team Edition for Software Architects Microsoft Visual Studio 2005 Team Edition for Software Developers Microsoft Visual Studio 2005 Team Edition for Software Testers DirectX extensions for Visual Studio .NET Visual Assist X
VA Info:quote:
VA_X.dll file version 10.3.1528.0 built 2006.06.30 VAOpsWin.dll version 1.3.3.3 VATE.dll version 1.0.5.7 DevEnv.exe version 8.0.50727.42 msenv.dll version 8.0.50727.42 Comctl32.dll version 6.0.2900.2180 Windows XP 5.1 Build 2600 Service Pack 2 4 processors
|
|
|
feline
Whole Tomato Software
United Kingdom
19021 Posts |
Posted - Jul 08 2006 : 2:43:51 PM
|
does the problem go away if you use the registry to stop VA loading on startup:
HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\8.0\\Addins\\VAssistNET.Connect8\ Change LoadBehavior from 1 to 0 to prevent VA from loading.
unfortunately you cannot use VS2005 to do this, hence the registry key.
in the installed products list you have "DirectX extensions for Visual Studio .NET", is this an IDE plugin?
IDE tools menu -> Add-in Manager -> list of available add-ins
the only other thing that stands out is the fact you are using VS2005 enterprise, but that should not cause a problem.
you say it also effected previous builds, is that only the 15xx builds, or did you get this problem before? |
zen is the art of being at one with the two'ness |
|
|
Admin
Whole Tomato Software
USA
74 Posts |
Posted - Jul 10 2006 : 12:07:10 PM
|
You might try build 1530 since it has fixes for a few exceptions. Not sure at all if they apply to you. Worth a try.
Otherwise, feline suggestion to isolate add-ins is a good one. |
|
|
tokamak
New Member
3 Posts |
Posted - Aug 10 2006 : 3:50:18 PM
|
I finally got around to reducing the issue down to this. Create a new .cs file outside VS2005 and paste the following line:
quote: using ("a ")
Save it and double-click the file to load it into VS.
When initially loading the .cs file or modifying/saving it, the exception will occur. I verified it on two separate installations going from 1531 all the way back to at least 1446.
Hope this helps.
|
|
|
sean
Whole Tomato Software
USA
2817 Posts |
Posted - Aug 11 2006 : 12:48:17 AM
|
case=1035
this should be fixed but we've had some build script problems so the fix hasn't made it out yet... it should be in 1532. |
Edited by - sean on Aug 11 2006 01:13:10 AM |
|
|
|
Topic |
|