Whole Tomato Software Forums

Whole Tomato Software Forums

All Forums

Visual Assist

Technical Support

VS 2013: Exception when opening text files

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

Screensize:

UserName:

Password:

Format:

Message:

Forum code is on.
Html is off.

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

T O P I C R E V I E W
SvenR	Posted - Oct 30 2013 : 05:27:35 AM On Visual Studio 2013 RTM/Windows 8.1 with VA 10.8.2001 the IDE shows an message box with an exception warning in an extension when the first file is opened in the editor. It's a fresh install with VAX only. Activity.xml shows the following entries: System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt. bei t.TextViewCreated(IWpfTextView textView) bei Microsoft.VisualStudio.Text.Editor.Implementation.WpfTextView.<>c__DisplayClassc.<BindContentTypeSpecificAssets>b__9() bei Microsoft.VisualStudio.Text.Utilities.GuardedOperations.CallExtensionPoint(Object errorSource, Action call) The color 'Popup' in category 'de7b1121-99a4-4708-aedf-15f40c9b332f' does not exist. Maybe it's worth to mention that the file is first colored by VA before the message box comes up.
8 L A T E S T R E P L I E S (Newest First)
sean	Posted - Nov 18 2013 : 3:12:16 PM case=78151 is fixed in build 2007
SvenR	Posted - Nov 01 2013 : 02:20:00 AM Great, thank you!
accord	Posted - Oct 31 2013 : 5:14:30 PM Good spot! I was able to reproduce the problem using non-default installation dir, so I have put in a bug report for this: case=78151 Everything works as expected when using default installation dir. Again, good job isolation the problem!
SvenR	Posted - Oct 31 2013 : 08:37:38 AM I have run some more tests. 1) On VM1 (VS 2013 RTM/Windows 8.1) I have deinstalled/reinstalled VA. After the first restart of Visual Studio VA's syntax coloring works. Next restart - exception warning. VS 2013 is installed in E:\\Visual Studio.12. 2) On VM2 (VS 2013 RTM/Windows 7) no problems with VA. In opposite to VM1 VS 2013 is installed in standard installation path. 3) If I install VS 2013 on VM1 in standard installation path VA seems to work. I took a snapshot before installing VS 2013, so the only difference between 1 and 3 is the installation path.
SvenR	Posted - Oct 30 2013 : 4:06:54 PM Sorry for choosing the wrong words. With 'crash' I meant the message box with the exception warning. --------------------------- Microsoft Visual Studio --------------------------- Eine Ausnahme ist aufgetreten. Dies ist m+?glicherweise auf eine Erweiterung zur++ckzuf++hren. (An exception has occurred. This may be due to an extension.) Weitere Informationen erhalten Sie, wenn Sie die Datei "C:\\Users\\Sven\\AppData\\Roaming\\Microsoft\\VisualStudio\\12.0\\ActivityLog.xml" ++berpr++fen. --------------------------- OK --------------------------- VS 2013 is still working after the message box, but the syntax coloring by VA is not available.
accord	Posted - Oct 30 2013 : 3:15:39 PM ah It also crashes. Exceptions not always cause crash. Can you please save out a minidump of the crash and send it in? http://docs.wholetomato.com?W303 You can send in the file using the following form: http://www.wholetomato.com/support/contact.asp Please paste the URL of this topic to the description field so we can match it up.
SvenR	Posted - Oct 30 2013 : 1:49:22 PM I have deleted the 12.0 directories, but it still crashes. I also can't see any error in VA's log files. Is there anything else that I can do to figure it out? I'm using a German version of VS 2013, maybe there are some language dependent things?
accord	Posted - Oct 30 2013 : 12:51:27 PM We have seen similar issues in the past. I'm not sure if the problem is with the VS extension cache this time, but it is possible. Can you please try deleting the cache to see if it fixes the issue? Close Visual Studio and then delete all files including sub directories: C:\\Users\\<username>\\AppData\\Local\\Microsoft\\VisualStudio\\11.0\\ComponentModelCache\\* and all .cache files in the following directory and its subdirectories: C:\\Users\\<username>\\AppData\\Local\\Microsoft\\VisualStudio\\11.0\\Extensions\\*.cache Visual Studio will rebuild those files when it starts up, and it hopefully resolves your problem.

Snitz Forums 2000