But now it’s published, I am getting a 500.30 error. Checking the activity logs in the app, I can see a consistent error:
ClientType dotnet-connectionString is not supported by MICROSOFT.WEB/SITES/SLOTS. Supported clientTypes are: dotnet.
I’ve had a look around and cannot find much info on this error or resolution. Has anyone else come across this and/or can suggest a fix?
I’ve also noticed that after creating the publish profile and publishing , my local code now won’t build with multiple errors around:
Build:Cannot find module ‘@umbraco-cms/backoffice/localization-api’ or its corresponding type declarations.
This only happens after publish though. Deleting the ‘lang’ directory in …\obj\Release\net9.0\win-x64\PubTmp\Out\wwwroot\umbraco\backoffice\assets and the .ts file in …\obj\Release\net9.0\win-x64\PubTmp\Out\wwwroot\umbraco\backoffice\packages\extension-types. Allows me to build and run the app locally again.
Ok so the first error about InvalidClientType looks like it was down to the Azure configuration we’d created. That looks ok now, although I need to work out using keyvault for the connection string.
But the second issue still persists in that when I run the publish, the release folder is missing references which breaks my local code. I assume this is being replicated on the WebApp as well which is muddying the water a lot.
The initial error was down to Azure configuration.
The secondary error persists, but have managed to workaround it by adding the following to the .csproj file:
<PropertyGroup Condition="'$(Configuration)'=='Debug'">
<TypeScriptCompileBlocked>true</TypeScriptCompileBlocked>
<!-- OR more specifically: -->
<DefaultItemExcludes>$(DefaultItemExcludes);wwwroot\umbraco\**</DefaultItemExcludes>
</PropertyGroup>