VS2017 15.7.4 - Visual Studio still loading the project
Problem reported by Andrey Sploshnov - August 5, 2018 at 12:34 AM
Resolved
I have VS2017 Community Edition and GhostDoc Pro 2018.1.18150 RC. I get the error message above every time I press Ctrl+Shift+D. I have read the topic about the same problem with VS2017 15.6 and I can confirm that this problem is still exists with the latest released version of GhostDoc Pro and latest beta version available. Log file is attached: GhostDoc Pro.log
 
Thank you in advance.
There is no fate but what we make for ourselves

8 Replies

Reply to Thread
0
Misha Zhutov Replied
Employee Post
Hello,

Thank you for reporting that.
I found in the log file that you loaded C++ project and it was not loaded by GhostDoc. What kind of project are you working with? What C++ file did you try to document (.h or .cpp)?
0
Andrey Sploshnov Replied
Yeah, you're right. It's a C++ project loaded via VisualGDB extension for VS2017 (https://visualgdb.com/download/). And I've tried to comment header file (.h). Actually I see the save behavior when I'm trying to comment .cpp file too.

I will try the "clean" C++ project (without any third-party extensions) later today when I get home.
There is no fate but what we make for ourselves
0
Serge B. Replied
Employee Post
Hi Andrey, please download the latest version of the GhostDoc - I was informed it includes fix for the issue you reported. Thanks!
Serge Baranovsky
SubMain Software
(800) 936-2134
0
Joe Joe Replied
I am getting the same problem with:
 
- Visual Studio 2017 Pro Version 15.7.5
- GhostDoc Community 5.9.18070.0 
- A solution with a single C# .NET Standard 2.0 project
 
0
Misha Zhutov Replied
Employee Post
Please download and install the latest v5.9.18240 from https://submain.com/download/
0
Andy Newlands Replied
I'm having this same issue with VS Pro 2017 (15.8.7) using GhostDoc Community GhostDoc.v2018.1.18330
I have tried uninstall/reinstall but problem persists.
0
Serge B. Replied
Employee Post
Hi Andy,

Please make sure you don't have an older version installed as MSI - https://support.submain.com/kb/a53/troubleshooting-vsix-installation-issues.aspx

If that is not the case, please email us the Log file to support at submain dot com

Thanks!
Serge Baranovsky
SubMain Software
(800) 936-2134
0
Andy Newlands Replied
Thanks, Serge. That did the trick - uninstall msi via Control Panel and re-install vsix.

Reply to Thread