2 Answers
No idea if this is still an issue for you or not. I just had the problem this morning & couldn’t figure it out. Tried closing studio & reopening it "as an admin" & that resolved the issue. It looks like the v17.5.x releases have added extra security 🤷♀️
1
-
1
I updated strawberry shake 12 to 13 and it removed the issue. Also able to get rid of auto generated models and few dependencies of strawberry shake.
– Hash_DewMar 21 at 12:07
This is a problem when using v12 of StrawberryShake with later versions of VS2022. I can be worked around by adding the following line to a PropertyGroup in your .csproj file
<StrawberryShake_State>$(MSBuildProjectExtensionsPath)berry</StrawberryShake_State>
This has been fixed in v13, and is no longer necessary.
I should mention there are however other issues in v13, that’s not present in v12 with regards to the client. So I would urge you to have a look at the Github Issues list before upgrading to fix this minor issue.