Update Dotfuscator Community Documentation for VS 2019 #2964
Conversation
|
|
|
@gmarino-preemptive : Thanks for your contribution! The author, @gewarren, has been notified to review your proposed change. |
| For information about enhancing Dotfuscator, see the [Upgrades page][upgrades]. | ||
|
|
||
| ## Getting started | ||
|
|
||
| To begin using Dotfuscator CE from Visual Studio, type `dotfuscator` into the **Quick Launch** (Ctrl+Q) search bar. | ||
| To begin using Dotfuscator Community from Visual Studio, type `dotfuscator` into the **Quick Launch** (Ctrl+Q) search bar. |
There was a problem hiding this comment.
The search box in VS 2019 is now just the search box (it's not called Quick Launch anymore).
docs/ide/dotfuscator/install.md
Outdated
|
|
||
| You can install Dotfuscator CE from the Visual Studio IDE: | ||
| ## Within Visual Studio 2019 |
There was a problem hiding this comment.
We are sharing files for both VS 2017 and VS 2017. There are ways to make an entire file applicable to just one or the other version, or to just make certain sections of a file applicable to one version. Would it be better to make this version agnostic if there's no difference between VS 2017 and VS 2019? If you want the syntax for making files or zones of files specific to a version, let me know.
There was a problem hiding this comment.
I think it would probably be best to make version-specific zones for the installation section, could you give me an example of the syntax for separating zones of files? Thanks!
There was a problem hiding this comment.
Take a look at this file for an example. Look for the sections surrounded by ::: moniker range="" and ::: moniker-end.
There was a problem hiding this comment.
Great, thanks!
docs/ide/dotfuscator/install.md
Outdated
| * If you instead see, under the *Menus* heading, **PreEmptive Protection - Dotfuscator Community**, then Dotfuscator Community is already installed. Select that option to [get started][get-started]. | ||
|
|
||
| 3. A Visual Studio Installer window will launch, pre-configured to install Dotfuscator Community. | ||
| * **Note:** You may be required to provide administrator credentials to continue. |
There was a problem hiding this comment.
Our note syntax is:
> [!NOTE]
> This is my note...
gmarino-preemptive
force-pushed
the
gmarino/dotfuscator-updates
branch
from
824964f to
c831ee7
Compare
|
@gmarino-preemptive : Thanks for your contribution! The author, @gewarren, has been notified to review your proposed change. |
|
@gewarren - I reviewed the changes in this PR and it seems to be ready to merge. However, since the public repo lacks proofing, staging, and validation tools, we can't tell if the new additions will introduce errors into the articles. To use those tools, the commits in this PR will need to be resubmitted or moved over to the private repo. We can move them and tag you for review / sign off. thanks. |
|
I'm going to merge this now because Dotfuscator needs these to go live today for the VS 2019 release. We can make any necessary fixes after they go live. |
|
Okay @gewarren - makes sense. Can someone check the views after this is published? Just want to make sure the moniker switch is working as intended and there are no layout anomalies. |
These changes update the Dotfuscator Community documentation for the upcoming release of Visual Studio 2019.
Are there any additional steps we will need to take to preserve the existing documentation for Visual Studio 2017?