Skip to main content

Strawberry Shake–Access to the path ‘obj\\berry’ is denied

When trying to build a C# project in Visual Studio 2022 v17.5, I got compiler errors. This was strange because the only thing that has changed was the Visual Studio version.  Here is the exact error I got:

In this project I was using the Strawberry Shake GraphQL client. This client uses a custom GraphQL compiler build action and it was exactly this step that failed.

The quick fix

Let me first explain a quick fix. This problem is indeed related to the Visual Studio version which seems to became more strict on what is allowed and what not.  To get rid of the error, restart your Visual Studio instance and run it under Administrator privileges.

Updating to Strawberry Shake 13

Unfortunately before I arrived at the quick fix above I took the long path and started an update to Strawberry Shake v13. This turned to be more work than I had expected.

Let me walk you through the steps:

  • Remove the package references to StrawberryShake.CodeGeneration.CSharp.Analyzers and StrawberryShake.Transport.Http and replace it with the StrawberryShake.Server package:

dotnet add package StrawberryShake.Server

  • Update the StrawberryShake CLI tools:

dotnet tool install StrawberryShake.Tools –local

Tool 'strawberryshake.tools' was successfully updated from version '12.0.1' to version '13.0.5' (manifest file C:\projects\Example\.config\dotnet-tools.json).

  • Remove the custom build action for your GraphQL files. This is now done through C# source generators:

  • Now something where I lost a lot of time on, the latest version only works for .NET 6 or higher. Unfortunately you don't get any error message but the code is not generated. So check that your project is using at least .NET Core 6:

That's it!

Labels:

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more