-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Orchard Core - Incompatible with Remora.Sdk #15479
Comments
Please check the following: |
Thanks for the suggestion, but this is a rather long readme. Are you referring to any section in particular? I can dig into that code more specifically. |
Framework Targets |
For executable projects such as an asp.net core website, the target framework is You can see that here: https://github.com/Remora/Remora.Sdk/blob/4f0e06a411d65f36c6a460064b2a50faaee37961/Remora.Sdk/Sdk/Sdk.props#L11-L17 The defaults are only provided if the property is not set. |
Someone from their project or you will have to investigate why it's not working. |
I don't think there's something that we can do here. Can we close this? |
Describe the bug
As a matter of practice, I tend to use the Remora.Sdk library by @Nihlus. It appears as though this SDK library is incompatible with Orchard. It is responsible for adding several default nuget packages, providing default StyleCop rules, and for Class Library projects, adds tools for nuget package management.
When this SDK is included, Orchard will return a 404 page instead of displaying the Out Of Box initial setup wizard.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The Out Of Box setup wizard should display, allowing you to perform the initial setup of the site. Instead, a 404 status code is returned.
Additional Comments
I'm logging this as an issue just for tracking purposes. Once a solution is found, it will be provided here. If this requires a configuration change, I'll propose a change to the documentation. Otherwise, the appropriate PR will be filed with the appropriate library.
The text was updated successfully, but these errors were encountered: