| T O P I C R E V I E W |
| ianjirka |
Posted - Nov 01 2015 : 1:45:05 PM
VS 2015 RTM (Version 14.0.23107.0 D14REL)
VA 10.9.2076.0 built 2015.09.15
After upgrading from 2015 RC and .. don't recall the previous VA version I get the below exception when opening the snippets editor (snippets don't work either).
How do I track this down? I'm not sure what the actual path VA is trying to use is constructed from.
Thanks much,
Ian
Type: ArgumentException
Message: Absolute path information is required.
Source: mscorlib
StackTrace: at System.Security.Util.StringExpressionSet.CreateListFromExpressions(String[] str, Boolean needFullPath)
at System.Security.Permissions.FileIOPermission.AddPathList(FileIOPermissionAccess access, AccessControlActions control, String[] pathListOrig, Boolean checkForDuplicates, Boolean needFullPath, Boolean copyPathList)
at System.Security.Permissions.FileIOPermission..ctor(FileIOPermissionAccess access, String path)
at VASnippetEditor.SnippetsManager.ParseTemplateFile(String sTemplateFile, String scope)
|
| 5 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - Nov 03 2015 : 01:58:36 AM
I am glad that fixed the problem  The only downside here is that you will have lost any Snippets you had added. If you had been making / editing snippets, you could try opening the corrupt and replacement .tpl files in a text editor, and copy across anything you want. Just be careful, since you might re-introduce the corruption.
The format is a little odd, but not complex. The main thing to watch for is the use of a "control" character as a separator. |
| ianjirka |
Posted - Nov 02 2015 : 9:54:53 PM
quote:
Originally posted by feline
Thank you for the update. It was worth trying, and at least we now know that is not the problem.
Can you please close the IDE and then open the folder:
%USERPROFILE%\\AppData\\Roaming\\VisualAssist\\Autotext\
and make a backup of all of the files here. You should have 9 *.tpl files, these contain your VA Snippets. Can you now delete these files, and look in:
%USERPROFILE%\\AppData\\Local\\Microsoft\\VisualStudio\\14.0\\Extensions\\ XXX \\Autotext\\Latest\
where XXX is the hashed directory name for the VA install directory. This directory contains the default VA snippets you will get from a new install. Copy across all of the .tpl files, and now load VS2015 again.
Does this make any difference?
Awesome - this did the trick. Thanks much for the quick response! |
| feline |
Posted - Nov 02 2015 : 9:01:55 PM
Thank you for the update. It was worth trying, and at least we now know that is not the problem.
Can you please close the IDE and then open the folder:
%USERPROFILE%\\AppData\\Roaming\\VisualAssist\\Autotext\
and make a backup of all of the files here. You should have 9 *.tpl files, these contain your VA Snippets. Can you now delete these files, and look in:
%USERPROFILE%\\AppData\\Local\\Microsoft\\VisualStudio\\14.0\\Extensions\\ XXX \\Autotext\\Latest\
where XXX is the hashed directory name for the VA install directory. This directory contains the default VA snippets you will get from a new install. Copy across all of the .tpl files, and now load VS2015 again.
Does this make any difference?
I am wondering if you have a problem with your current Snippets, perhaps one of the files has become corrupted somehow. If so this should help.
If this does not make any difference, can you please generate VA logs, and also grab a mini dump while the exception is showing. For the logs, load the IDE and your solution, then turn on VA logging:
VA Options -> Performance -> Enable logging
trigger the exception by opening the VA Snippet editor, and then close the IDE to keep the log files small. Please see this FAQ for details of turning on VA's logging, and sending us the log files
http://docs.wholetomato.com/default.asp?W305
If you are not sure how to grab a mini dump file, this page explains a few methods:
http://docs.wholetomato.com/default.asp?W303
personally I like "procdump", since it is quick and easy if you have the utility on hand.
Zip the files file and attach it to a request for assistance. Please include the TOPIC_ID 12463 so we can match up the files to this problem:
http://www.wholetomato.com/support/contact.asp |
| ianjirka |
Posted - Nov 02 2015 : 8:17:30 PM
I tried this but no luck - behavior is the same. I tried repairing VS 2015 as well.
Is there any tracing I can enable/other info I can provide you?
Thanks much,
Ian
|
| feline |
Posted - Nov 02 2015 : 3:50:36 PM
Odd. We had another user recently who had odd problems after upgrading from VS2015 RC. Uninstalling and reinstalling helped there.
Before trying this, it's best to save out your settings, just in case you need to reimport them later. You can do this via:
VA Options -> Performance -> Export Settings
IDE tools menu -> Import and Export Settings -> Export selected environment settings
Now can you please uninstalling VA, via:
IDE tools menu -> Extensions and Updates...
select Visual Assist and then press Uninstall. This will require an IDE restart.
Next please look in the directory:
%USERPROFILE%\\AppData\\Local\\Microsoft\\VisualStudio\\14.0\\Extensions\
if there are any sub-directories, do any of them contain VA_X.dll? Any subdirectories will have hashed names, so you need to check the contents. You might have one or more install's left over. If so, please delete these Visual Assist install directories.
Now reinstall VA, you can download the installer from this page:
http://www.wholetomato.com/downloads/default.asp
If we are lucky this will fix the problems, and the snippet editor will work now. |
|
|
