New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot find compilation library location for package 'Microsoft.Win32.Registry' #1156
Comments
I know an expert about these kind of things, he lives in France near Valence ... |
I just figured out that OrchardCore.Cms.Web.csproj has these options:
|
Yes, we precompile views so when publishing we don't need to output compile time assemblies in the |
Needs documentation to explain which properties to add in .csproj when you use OC.Targets nuget package or else it won't work when it is deployed on IIS. |
As a reminder.
|
I set this up
however still throws the same error. I'm currently on VS 2017 15.5.5 |
This will be included inthe csproj when you create a Cms.Web application using the dotnet new template
|
So, maybe better to re-add this line in the
|
Hmm, maybe something to add to the documentation A module needs to use the razor sdk to have its razor views precompiled.
But, for the precompilation to be effective you also need in each module project file.
|
Thank you for the explanations @jtkech . I migrated my OC website to the latest version and I was wondering what to change: and then which package use: |
As it is in the current And if you want all your modules views to be precompiled, don't forget to add to each module a direct reference to Otherwise you will have razor compilation at runtime and then you will need the
|
@agriffard for infos So, i'm working on a PR that will be ready for tomorrow
So at this point it will just be by default.
|
Following suggestions from various links (couple displayed below) - toddams/RazorLight#203 - OrchardCMS/OrchardCore#1156
I tried all the above advices, but I still got the following error:
This is my csproj file: <Project Sdk="Microsoft.NET.Sdk.Web"> <PropertyGroup> <ItemGroup> <ItemGroup> </Project> I ran out of ideas |
When running an Orchard Core instance within an Azure environment, when a custom theme is enabled an exception prevents the front end from being accessible. Below is a snipprt of the logged exception. ``` System.InvalidOperationException: Cannot find compilation library location for package 'Microsoft.NETCore.App' ``` To fix this issue (discussed here - OrchardCMS/OrchardCore#1156) a couple of properties need to be added to the csproj for the main site project.
When running an Orchard Core instance within an Azure environment, when a custom theme is enabled an exception prevents the front end from being accessible. Below is a snipprt of the logged exception. ``` System.InvalidOperationException: Cannot find compilation library location for package 'Microsoft.NETCore.App' ``` To fix this issue (discussed here - OrchardCMS/OrchardCore#1156) a couple of properties need to be added to the csproj for the main site project. Fixes #3.
When running an Orchard Core instance within an Azure environment, when a custom theme is enabled an exception prevents the front end from being accessible. Below is a snipprt of the logged exception. ``` System.InvalidOperationException: Cannot find compilation library location for package 'Microsoft.NETCore.App' ``` To fix this issue (discussed here - OrchardCMS/OrchardCore#1156) a couple of properties need to be added to the csproj for the main site project. Fixes #3.
I published an OC application on a server and hosted it on IIS and I had this error:
Cannot find compilation library location for package 'Microsoft.Win32.Registry'
I don't know what is the exact reason but I managed to fix it by adding this in my .csproj :
<MvcRazorExcludeRefAssembliesFromPublish>false</MvcRazorExcludeRefAssembliesFromPublish>
See https://github.com/dotnet/core-setup/issues/2113 for more explanations
The text was updated successfully, but these errors were encountered: