| T O P I C R E V I E W |
| devlyn811 |
Posted - Mar 15 2016 : 4:30:36 PM
Hello,
I've been a licensed user of Visual Assist with Visual Studio 2013 for about a year and a half, without any issue.
Last nite, Visual Studio would not open any of my projects, providing only 'Waiting for operation to complete' error, on which there is no help anywhere.
I reinstalled VS and VA and the same thing happened. At the time I didn't know it was VA causing the issue. I repeatedly re-installed VS and was able to open projects, until I installed VA.
I couldn't believe it could possibly be VA, so I upgraded my OS to Windows 10, reinstalled VS and opened my projects without issue. Then I installed VA and the problem occurs again.
I've tried this exact sequence now 3 times and I can confirm that everything is fine, until I install VA and VS hangs.
Any ideas on what could be happening here. I'm a little desperate here, I work on a huge project and absolutely rely on VA to get my work done.
Thanks for any help you could provide. |
| 6 L A T E S T R E P L I E S (Newest First) |
| devlyn811 |
Posted - Mar 17 2016 : 4:02:46 PM
Thanks!
Thanks for all you help - I definitely appreciate it! |
| sean |
Posted - Mar 17 2016 : 3:29:12 PM
That's due to a new feature in VS2015. See details and workaround here:
http://forums.wholetomato.com/forum/topic.asp?TOPIC_ID=12407
http://docs.wholetomato.com/default.asp?W426
|
| devlyn811 |
Posted - Mar 17 2016 : 2:19:24 PM
No, I did not install update 5. That could have been the problem. Since I moved to 2015, I probably won't install anymore versions of 2013.
However, with 2105 I am having a strange issue, but not super major. For some reason, somehow, Visual Assist is automatically installing version 2089, which I don't have a license for. The max license I can use is 2068.
Reinstalling 2068 works, but for some reason, 2089 is somehow self installing, even though I have disabled 'Check for updates'.
Is there anyway to disable the apparent automatic update? |
| accord |
Posted - Mar 16 2016 : 5:03:31 PM
Strange, problems like this are unexpected with VS2013, but I'm glad that installing VS2015 has helped. When you used VS2013, did you also install update 5? |
| devlyn811 |
Posted - Mar 15 2016 : 9:17:21 PM
Hello and thanks for the reply.
I ended up installing VS2015 and VA and everything seems to be working at this point 
It took a bit of effort to make the conversion, and I still have a bit of work to do to finalize the conversion, but with VS2015 in place, I have no plans to revert back to VS2013.
If I end up with the same issue, I'll reply back to this post with the information you requested.
Thanks again! |
| accord |
Posted - Mar 15 2016 : 6:51:41 PM
Sorry to hear this.
Which Visual Assist build are you using? If it's not the latest, can you please install it from here?
http://www.wholetomato.com/downloads/default.asp
Does it make any difference?
Did you do something that might have triggered this problem? e.g. Installing a newer version of VA?
Is Visual Assist the only extension you install when it happens?
Can you please capture a minidump of the hang? It may help us seeing what is happening:
http://docs.wholetomato.com/default.asp?W303
Can you also please turn on VA logging before you open the project and send the log files in? This KB article describes how to turn on logging and where you can collect them:
http://support.wholetomato.com/default.asp?W305
You can send the files in via this form:
http://www.wholetomato.com/support/contact.asp
Please paste the URL of this topic to the Your Request field so we can match it up.
Does it happen if you create a clean new project?
Which programming language are you using? |
|
|
