Problem when using a RuntimeIdentifier (win-x64)
Closed this issue · 4 comments
We would like to implement BlazorWasmAntivirusProtection because of problems at one of our customers, but adding the nuget packages the build steps are not executed.
After some trial and error we found out that the problem is caused by the runtime identifier we use to build our project. Removing <RuntimeIdentifier>win-x64</RuntimeIdentifier> from our server csproj makes the build step to be executed.
We have the feeling that the extra folder in the bin folder for the runtimeidentifier is the cause, but we don't know where in the package this is a problem.
So building the project without the runtimeidentifier gives the following path:
Server\bin\Release\net7.0\publish\wwwroot\_framework
With runtime identifier it becomes:
Server\bin\Release\net7.0\win-x64\publish\wwwroot\_framework
Is this something that can be fixed in the next version?
I'm having trouble putting my finger on it....
Is there any way how to debug this package? I tried referencing the projects instead of using the nuget package, but that does not seem to work?
I cannot reproduce it. I added <RuntimeIdentifier>win-x64</RuntimeIdentifier> to my project and it worked fine:
What error are you getting? Did you add the package to both Server and Client projects?
Yes, but now I see I had the wrong version on one of the projects. Also our build in Azure DevOps is quite complicated. I just found out how to get it running there by simplifying stuff. So sorry for this issue. The problem was not the runtimeidentifier.
Got it to work on our development environment today! Thanks for a great package @stavroskasidis !!