| T O P I C R E V I E W |
| horeaper |
Posted - Oct 24 2017 : 06:24:38 AM
This is quite a complex problem so bear with me a little :)
I use VA along side with Resharper on VS2017. At first I noticed that Resharper was unable to parse any source code which has reference to nuget packages (ONLY in a .net standard 2.0 project. The good old .net framework DLL project works fine). I reported this issue to Resharper's team, the link is here: https://youtrack.jetbrains.com/issue/RSRP-464676#comment=27-2466124
Then one day, out of nowhere, it works! I was in the middle of upgrading my VisualAssist, a bug came up, I have to fix it ASAP, so I lanuched my project without VA installed, and Resharper was able to parse the source file correctly. That got me thinking...
I reinstalled the lastest (2237) VA, and re-opened my project, the problem came back. So I disabled VA through menu (not by extension manager), and tells Resharper to reanalyze everything. Problem gone. But after I re-enabled VA, VA starts to act a little strangely. For example, sometime it works fine, sometimes it unable to parse certain source files, the VA's navigation bar will not show properly (as the attachment image shows), almost as if certain resources was locked by some other application, and VA was stalled (dead-locked) on retrieving such resources.
And I was unable to open VA's option window when this problem happens, Visual Studio will crash when I tried to do so.
I think that "certain resources" might be nuget packages, or something depends on those packages. Since I know nothing about how extension works, I can only guess.
After I restarted visual studio (leave VA enabled), the Resharper's parsing problem will come back, but VA will works fine. Basically means: I can't get both of them working properly at the same time.
I know this might not be VA's problem, but for people who uses both extensions together (that's everyone in my company, which is, sadly, almost everyone I know :( ), this problem is kinda annoying.
I have also reported the same issue to Resharper's team, followed by the link https://youtrack.jetbrains.com/issue/RSRP-464676#comment=27-2495327
PS. I'm currently using VS 15.4.0 with Resharper 2017.2.2 and VisualAssist 2237 on Windows 10 x64
PS2. Also tried VA 2231, same problem.
|
| 7 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - Oct 30 2017 : 07:21:09 AM
The navigation bar problem not happening under Windows 8.1 makes sense if this is the problem triggered by the Windows 10 Fall update, since this is a Windows 10 specific problem.
Any further clues to help us pin down what is going on here would be useful, especially if there is evidence that VA is a factor. |
| horeaper |
Posted - Oct 30 2017 : 02:47:13 AM
quote:
Originally posted by accord
When VA is parsing, it looks like this:
If VA is successfully disabled, you shouldn't get thoses.
What type of parsing errors are you getting? A dialog, a log, or something else?
The parsing error I mentioned in post "Oct 29 2017" are not related to VA. |
| accord |
Posted - Oct 29 2017 : 11:03:09 AM
When VA is parsing, it looks like this:
If VA is successfully disabled, you shouldn't get thoses.
What type of parsing errors are you getting? A dialog, a log, or something else? |
| horeaper |
Posted - Oct 29 2017 : 05:26:06 AM
It's pretty hard to reproduce, generally you need VS2017 with .net framework + .net core 2.0 workbench (C++ is not needed), and create an .net standard 2.0 project, add some nuget packages, which in my case is MongoDB and YamlDotNet, and use them. The problem may happen, depends on how complex the project are. For the commerical project I'm working with, it's 100% guaranteed to happen.
But hold on, something weird has happened. I tried the "disable VA and let resharper reanalyze" on a freshly installed Windows 8.1 x64 VM (with a VS extension setup identical to my host Windows 10), but those parsing errors are still there. I even tried disable VA through the VS extension manager, no use. Maybe this problem has nothing to do with VA, maybe it's not a resource conflict at all. I think I'll need to investigate a little further, gonna get back to you once I have more information, sorry for the inconvenience!
BTW the "navigation bar gone haywire" never happened under Windows 8.1, VA works perfectly fine. |
| feline |
Posted - Oct 28 2017 : 07:47:05 AM
How should I set about setting up a test for this problem?
It looks like I need a .NET standard 2.0 solution, but in C#, C++ or both?
Do I need to add one or more Nuget packages? Is it enough to simply add Nuget packages to the solution, or do I have to try actually using them as well?
If I am understanding correctly, it takes a bit of time for this problem to start happening, so I want to make sure I am trying out the right test situation. |
| horeaper |
Posted - Oct 26 2017 : 02:09:48 AM
The problem "unable to cooperate with Resharper well under .net standard 2.0" happens both before and after I installed the Fall Creators Update.
For the "unable to open Visual Assist option dialog" problem, it might related to that "CreateWindow()" bug.
|
| feline |
Posted - Oct 24 2017 : 09:50:43 AM
Are you running the Windows 10 Fall Creators Update? Either the final release of this, or from the preview ring?
In the System Information screen for Windows 10, the Fall Creators Update is reporting Build 16299.
I ask because there is currently a known problem with VA and the IDE under this version of Windows, and one of the symptoms is that the VA navigation bar is not shown some of the time, and this is often followed by an IDE crash.
So it's possible this is going on here as well, either on its own, or related to some other problem. |
|
|
