Fixes documentation referring to how Strawberry Shake uses Roslyn (#6507

)
ChilliCream · Sep 4, 2023 · eadd495 · eadd495
1 parent 7841645
commit eadd495
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/website/src/docs/strawberryshake/v13/get-started/console.md b/website/src/docs/strawberryshake/v13/get-started/console.md
@@ -120,7 +120,7 @@ query GetSessions {
 dotnet build
 ```
 
-With the project compiled you now should see a directory `Generated`. The generated code is just there for the IDE, the actual code was injected directly into roslyn through source generators.
+With the project compiled, you should now see in the directory `./obj/<configuration>/<target-framework>/berry` the generated code that your applications can leverage. For example, if you've run a Debug build for .NET 8, the path would be `./obj/Debug/net8.0/berry`.
 
 ![Visual Studio code showing the generated directory.](../../../shared/berry_console_generated.png)
 

diff --git a/website/src/docs/strawberryshake/v13/get-started/xamarin.md b/website/src/docs/strawberryshake/v13/get-started/xamarin.md
@@ -139,7 +139,7 @@ query GetSessions {
 dotnet build
 ```
 
-With the project compiled you now should see a directory `Generated`. The generated code is just there for the IDE, the actual code was injected directly into roslyn through source generators.
+With the project compiled, you should now see in the directory `./obj/<configuration>/<target-framework>/berry` the generated code that your applications can leverage. For example, if you've run a Debug build for .NET 8, the path would be `./obj/Debug/net8.0/berry`.
 
 ![Visual Studio code showing the generated directory.](../shared/berry_generated.png)