Update for UseArtifactsOutput

ionide · Feb 12, 2024 · d3a0d66 · d3a0d66
1 parent f449797
commit d3a0d66
Show file tree

Hide file tree

Showing 5 changed files with 13 additions and 13 deletions.
diff --git a/build.fsx b/build.fsx
@@ -28,7 +28,7 @@ pipeline "Build" {
     }
     stage "sample" {
         run
-            "dotnet run --project src/FSharp.Analyzers.Cli/FSharp.Analyzers.Cli.fsproj -- --project ./samples/OptionAnalyzer/OptionAnalyzer.fsproj --analyzers-path ./samples/OptionAnalyzer/bin/Release --verbosity d"
+            "dotnet run --project src/FSharp.Analyzers.Cli/FSharp.Analyzers.Cli.fsproj -- --project ./samples/OptionAnalyzer/OptionAnalyzer.fsproj --analyzers-path ./artifacts/bin/OptionAnalyzer/release --verbosity d"
     }
     stage "docs" { run "dotnet fsdocs build --properties Configuration=Release --eval --clean --strict" }
     runIfOnlySpecified false

diff --git a/docs/content/Dual Analyzer.fsx b/docs/content/Dual Analyzer.fsx
@@ -12,8 +12,8 @@ With a little orchestration it is possible to easily write two analyzer function
 *)
 
 (*** hide ***)
-#r "../../src/FSharp.Analyzers.Cli/bin/Release/net6.0/FSharp.Analyzers.SDK.dll"
-#r "../../src/FSharp.Analyzers.Cli/bin/Release/net6.0/FSharp.Compiler.Service.dll"
+#r "../../artifacts/bin/FSharp.Analyzers.SDK/release/FSharp.Analyzers.SDK.dll"
+#r "../../artifacts/bin/FSharp.Analyzers.Cli/release/FSharp.Compiler.Service.dll"
 (** *)
 
 open FSharp.Analyzers.SDK

diff --git a/docs/content/Getting Started Writing.fsx b/docs/content/Getting Started Writing.fsx
@@ -60,8 +60,8 @@ In the following example we will be
 *)
 
 (*** hide ***)
-#r "../../src/FSharp.Analyzers.Cli/bin/Release/net6.0/FSharp.Analyzers.SDK.dll"
-#r "../../src/FSharp.Analyzers.Cli/bin/Release/net6.0/FSharp.Compiler.Service.dll"
+#r "../../artifacts/bin/FSharp.Analyzers.SDK/release/FSharp.Analyzers.SDK.dll"
+#r "../../artifacts/bin/FSharp.Analyzers.Cli/release/FSharp.Compiler.Service.dll"
 (** *)
 open FSharp.Analyzers.SDK
 

diff --git a/docs/content/Programmatic access.fsx b/docs/content/Programmatic access.fsx
@@ -13,9 +13,9 @@ The `Client` needs to know what type of analyzer you intend to load: *console* o
 *)
 
 (*** hide ***)
-#r "../../src/FSharp.Analyzers.Cli/bin/Release/net6.0/FSharp.Analyzers.SDK.dll"
-#r "../../src/FSharp.Analyzers.Cli/bin/Release/net6.0/FSharp.Compiler.Service.dll"
-#r "../../src/FSharp.Analyzers.Cli/bin/Release/net6.0/Microsoft.Extensions.Logging.Abstractions.dll"
+#r "../../artifacts/bin/FSharp.Analyzers.SDK/release/FSharp.Analyzers.SDK.dll"
+#r "../../artifacts/bin/FSharp.Analyzers.Cli/release/FSharp.Compiler.Service.dll"
+#r "../../artifacts/bin/FSharp.Analyzers.Cli/release/Microsoft.Extensions.Logging.Abstractions.dll"
 (** *)
 
 open FSharp.Analyzers.SDK

diff --git a/docs/content/Unit Testing.fsx b/docs/content/Unit Testing.fsx
@@ -17,11 +17,11 @@ For a complete example of an unit testing project, take a look at [`OptionAnalyz
 *)
 
 (*** hide ***)
-#r "../../src/FSharp.Analyzers.SDK.Testing/bin/Release/net6.0/FSharp.Analyzers.SDK.dll"
-#r "../../src/FSharp.Analyzers.SDK.Testing/bin/Release/net6.0/FSharp.Analyzers.SDK.Testing.dll"
-#r "../../src/FSharp.Analyzers.Cli/bin/Release/net6.0/FSharp.Compiler.Service.dll"
-#r "../../samples/OptionAnalyzer.Test/bin/Release/net6.0/nunit.framework.dll"
-#r "../../samples/OptionAnalyzer.Test/bin/Release/net6.0/OptionAnalyzer.dll"
+#r "../../artifacts/bin/FSharp.Analyzers.Cli/release/FSharp.Compiler.Service.dll"
+#r "../../artifacts/bin/FSharp.Analyzers.SDK/release/FSharp.Analyzers.SDK.dll"
+#r "../../artifacts/bin/FSharp.Analyzers.SDK.Testing/release/FSharp.Analyzers.SDK.Testing.dll"
+#r "../../artifacts/bin/OptionAnalyzer.Test/release/nunit.framework.dll"
+#r "../../artifacts/bin/OptionAnalyzer.Test/release/OptionAnalyzer.dll"
 (** *)
 
 open FSharp.Compiler.CodeAnalysis