Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
User name:
Password:
Save Password
Forgot your password?

 All Forums
 Visual Assist
 Technical Support
 VS2013 ASCX & ASPX files
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

thodgson
Junior Member

USA
14 Posts

Posted - Dec 30 2013 :  2:57:58 PM  Show Profile  Reply with Quote
In Visual Studio 2013 can see the VA X dropdown region and method lists in .cs and .vb files but not in .ascx and .aspx files.

This is not an issue with VS 2012.

I have the latest version of VA X installed (as of today).

Tim Hodgson
VP Software Development
ExclamationSoft
http://www.exclamationsoft.com

accord
Whole Tomato Software

United Kingdom
3282 Posts

Posted - Jan 01 2014 :  11:16:58 AM  Show Profile  Reply with Quote
I think that the following link will help with that:

http://docs.wholetomato.com/default.asp?W326
Go to Top of Page

thodgson
Junior Member

USA
14 Posts

Posted - Mar 14 2014 :  2:44:02 PM  Show Profile  Reply with Quote
Changed the value from 01 to 00 and it had no effect.

Tim Hodgson
VP Software Development
ExclamationSoft
http://www.exclamationsoft.com
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
18100 Posts

Posted - Mar 17 2014 :  1:57:36 PM  Show Profile  Reply with Quote
This should have worked for you, I have just double checked it with VS2013, VA 2029 and Windows 7 64bit and a .ASPX file.

Can you please try this again, making sure all instances of the devenv.exe process have closed before editing the registry. If an IDE instance is open when you make the edit, VA will save out its current settings on exit, overwriting any changes you may have made.

zen is the art of being at one with the two'ness
Go to Top of Page

thodgson
Junior Member

USA
14 Posts

Posted - Apr 04 2014 :  08:11:06 AM  Show Profile  Reply with Quote
I have closed all instances of Visual Studio, and the recommended registry change does not fix the problem.

I uninstalled Visual Assist, and then opened Visual Studio 2013. To my surprise, Visual Assist prompted me to enter a license key...didn't I just uninstall the software?
The _EXTENSION_ for Visual Studio was still installed. I uninstalled the extension, and then installed the latest version of Visual Assist.
Next, I opened Visual Studio 2013, entered my license key when prompted, and then edited a file.

Still does not work in Visual Studio 2013. In fact, it doesn't work at all. The two extra drop downs for files are missing, Ctrl-M doesn't do anything, VA Outline is completely blank. Visual Assist is definitely enabled, just not doing anything.

BTW, works fine, in Visual Studio 2012 on the same machine, with .cs files...but not .vb files.

Tim Hodgson
VP Software Development
ExclamationSoft
http://www.exclamationsoft.com
Go to Top of Page

thodgson
Junior Member

USA
14 Posts

Posted - Apr 04 2014 :  2:02:55 PM  Show Profile  Reply with Quote
Figured it out:
1. Close Visual Studio (kill any devenv.exe running)
2. Uninstall Visual Assist through "Programs and Features"
3. (Optional) Run registry cleaner.
4. Open Visual Studio. If Visual Assist prompts to enter license info, remove the extension: Tools -> Extensions and Updates
5. Close Visual Studio (kill any devenv.exe running)
6. Install Visual Assist
7. Edit the registry: HKCU \\ Software \\ Whole Tomato \\ Visual Assist X \\ <IDE spec> \\RestrictVaToPrimaryFileTypes set to 00 (Default value is 01)
8. Start Visual Studio

My conditions are:
Visual Studio 6.0, 2012, and 2013

Tim Hodgson
VP Software Development
ExclamationSoft
http://www.exclamationsoft.com
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
18100 Posts

Posted - Apr 10 2014 :  4:41:02 PM  Show Profile  Reply with Quote
Sorry for the problems you had here, but I am glad you got this working in the end. I am not sure what happened here, this should have worked without the need to uninstall. I have never had to reinstall to get registry key settings to be picked up and work.

One thing I can explain, for VS2010 and above Microsoft have changed how IDE extensions work. So uninstalling Visual Assist from the Windows Control Panel only effects VS2008 and earlier. For VS2010 and above you need to uninstall Visual Assist from within each IDE individually. This is partly because IDE extensions in VS2010 and above are installed on a user by user basis, they are no longer installed for all users in one go.

zen is the art of being at one with the two'ness
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
© 2021 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000