2
When will GhostDoc Pro support Visual Studio Enterprise 2019 Preview?
Question asked by Danny McNaught - 12/4/2018 at 6:24 PM
Answered
When will GhostDoc Pro support Visual Studio Enterprise 2019 Preview?

18 Replies

Reply to Thread
0
Serge B. Replied
Employee Post
Hi Danny,
 
We have been preparing for the VS 2019 integration changes and working on this currently but we generally don't make our product integration available for Previews of a new VS. 
 
First Beta of the new VS is when we will have this public.
 
Thanks!
Serge Baranovsky
SubMain Software
(800) 936-2134
0
Danny McNaught Replied
Thanks Serge.
0
Zhmayev Yaroslav Replied
Hello Danny, I was waiting for GhostDoc update too and while waiting for an official release I've created an adapted version, it might malfunction etc, because it's not official
0
Danny McNaught Replied
Serge the Visual Studio Enterprise 2019 RC was released yesterday so now when should we see Ghostdoc Pro Support for VS 2019?
0
Jason Alan Smith Replied
Looks like we're past the beta stage with the RC having been released. Any update on when GhostDoc can be installed on this version? I have it installed and it's not showing up in VS 2019. Thanks. ~Jason
0
Work Replied
We are also interested in this, it would be good to know when VS 2019 is out there's no barriers with migrating over. We use Resharper and Ghostdoc heavily and Resharper already has support for 2019 RC. I think it's important there's early visibility of Ghostdoc in major VS updates at least in the RC and day 1 support for the final.
I'm a .NET Dev Director building Episerver solutions on the cloud using VS, Resharper and Ghostdoc
0
Danny McNaught Replied
Not sure why they are waiting but I modified the vsix file and it installs and works on 2091 RC. I use modified rules to create xml comments like:
/// <summary>
/// Gets or sets the test.
/// </summary>
/// <value>The test.</value>
/// <remarks>
/// <para><b>History:</b></para>
/// <list type="table">
/// <listheader>
/// <devName>Developer\Date\Time</devName>
/// <devCompany>Developer Company</devCompany>
/// <devPhone>Developer Phone</devPhone>
/// <devEmail>Developer Email</devEmail>
/// <devMachine>Developer On</devMachine>
/// <description>Description</description>
/// </listheader>
/// <item>
/// <devName>
/// Developer: Danny C. McNaught
/// <para>Date: Tuesday, March 5, 2019</para>
/// <para>Time: 11:21 AM</para>
/// </devName>
/// <devCompany>United States Postal Service</devCompany>
/// <devPhone>#####</devPhone>
/// <devEmail>
/// <a href="mailto:danny.mcnaught@uspsector.com">mailto:danny.mcnaught@uspsector.com</a>
/// <para><a href="mailto:danny.c.mcnaught@usps.gov">mailto:danny.c.mcnaught@usps.gov</a></para>
/// <para><a href="mailto:sfcsarge@outlook.com">mailto:sfcsarge@outlook.com</a></para>
/// </devEmail>
/// <devMachine>AAAAA</devMachine>
/// <description>Created XML Comment</description>
/// </item>
/// <item>
/// <devName>
/// Developer: Danny C. McNaught
/// <para>Date: Tuesday, March 5, 2019</para>
/// <para>Time: 11:21 AM</para>
/// </devName>
/// <devCompany>United States Postal Service</devCompany>
/// <devPhone>####</devPhone>
/// <devEmail>
/// <a href="mailto:danny.mcnaught@uspsector.com">mailto:danny.mcnaught@uspsector.com</a>
/// <para><a href="mailto:danny.c.mcnaught@usps.gov">mailto:danny.c.mcnaught@usps.gov</a></para>
/// <para><a href="mailto:sfcsarge@outlook.com">mailto:sfcsarge@outlook.com</a></para>
/// </devEmail>
/// <devMachine>AAAAAA</devMachine>
/// <description>Created XML Comment</description>
/// </item>
/// </list>
/// </remarks>
string test { get; set; }
0
Danny McNaught Replied
I meant 2019 RC
0
Danny McNaught Replied
It even works using the Editor with the customer comment rule under VS 2019 RC
0
Danny McNaught Replied
I use Comment Remover extension from Mads Kristensen to remove comments during this testing and Comment This, Comment File etc. all work fine.
0
Serge B. Replied
Employee Post Marked As Answer
The GhostDoc v2019 Beta is available for download at -
 
 
This is the version to be used with the Visual Studio 2019.
 
Thanks!
Serge Baranovsky
SubMain Software
(800) 936-2134
0
Danny McNaught Replied
Thanks Serge, works great on VS 2017-2019 installed and works so far with no issues.
0
Kornelis Replied
@Danny McNaught: what did you exactly change in the .vsix-file to make it install on VS2019? I tried doing the same, but it keeps complaining about missing Microsoft.VisualStudio.Component.CoreEditor...
0
Danny McNaught Replied
The have release the GhostDoc v2019 Beta but here is what I change in the 2018 version of the .vsix file.

In manifest.json change "dependencies":{"Microsoft.VisualStudio.Component.CoreEditor":"[15.0,16.0)"}} to "dependencies":{"Microsoft.VisualStudio.Component.CoreEditor":"[15.0,17.0)"}}.

In catalog.json change "Microsoft.VisualStudio.Component.CoreEditor":"[15.0,16.0)"} to "Microsoft.VisualStudio.Component.CoreEditor":"[15.0,17.0)"}

In extension.vsixmanifest change all Version="[15.0, 16.0)" to Version="[15.0, 17.0)"

this states to the vsix install to include all version from 15.0 to 17.00 (which is all version numbers for VS 2019 version 16.#

Note: This is not supported by Submain so you are doing this at your own risk and should uninstall it prior to installing Submain's official Beta/Release versions.
0
Danny McNaught Replied
As I stated earlier the GhostDoc Pro/Enterprise V2019 Beta is working fine from me and I have not found any issues yet. So I would not change V2018 .vsix but install the official Beta.
0
Danny McNaught Replied
Note: Changing the .vsix file like this for other companies extensions works great as well, as long as the version of .vsix is 2.0.
0
Danny McNaught Replied
You can watch the video and Mads Kristensen. give good info and examples of this. https://youtu.be/vcMznDBs6IU
0
Kornelis Replied
You are right. You shouldn't 'hack' the existing vsix if there's an official version from SubMain themselves that supports it. At the time I asked, this beta wasn't available yet.

Reply to Thread