Skip to content

Commit d2166e3

Browse files
committed
chore: remove commented part
1 parent ff1cf98 commit d2166e3

File tree

1 file changed

+0
-3
lines changed
  • doc/articles/contributing/Documentation

1 file changed

+0
-3
lines changed

doc/articles/contributing/Documentation/docfx.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -148,9 +148,6 @@ To run DocFX locally and check the resulting html:
148148
1. Open the `Uno.UI-Tools.slnf` solution filter in the `src` folder with Visual Studio.
149149
2. Edit the properties of the `Uno.UwpSyncGenerator` project. Under the 'Debug' tab, set Application arguments to "doc".
150150
3. Set `Uno.UwpSyncGenerator` as startup project and run it. It may fail to generate the full implemented views content; if so, it should still nonetheless generate stubs so that DocFX can run successfully.
151-
<!-- 4. Navigate to `%USERPROFILE%\.nuget\packages\docfx.console`. If you don't see the DocFX package in your NuGet cache, go back to ``Uno.UI-Tools.slnf`, right-click on the solution and choose 'Restore NuGet Packages.' UNDONE: DocFx.console is depreciated and not longer available, see more Information to this here: https://github.com/dotnet/docfx/issues/9100
152-
5. Open the latest DocFX version and open the `tools` folder. UNDONE: tools\DocFx.exe is now nested in .dotnet folder and available throught `dotnet tool`
153-
6. Open a Powershell window in the `tools` folder. UNDONE: Terminal in the IDE is enough -->
154151
4. Open a Terminal at the Root Directory of your locally cloned Uno Repository.
155152
5. Install docfx globally: `dotnet tool install -g docfx`
156153
6. Run the following command: `docfx build doc/docfx.json` and attach any nested foldername you want by adding `-o your-nested-output-path`, default: `_site`

0 commit comments

Comments
 (0)