-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
umbraco/config/lang missing on dotnet publish --no-build #11662
Comments
|
FWIW the csproj for 9.0.0 and 9.01 looked like this
whereas in 9.1.0 it looks like this (when using the dotnet new template):
I know that you mentioned that these should not be necessary anymore, but if I add them back in, in a 9.1.0 project (both the items under the PropertyGroup at the top and the ItemGroup) then it works as expected on Umbraco Cloud. |
Yep that's how it used to work, it may be that adding to the content item is the fix but should be applied in targets files instead of polluting the csproj, however that will cause us issues with duplicates for those upgrading from 9.0.0 (as their csproj will also add to content item). Will come up with something. |
But if I add those elements back in I don't get 'duplicate property' errors. Just tested it on two different 9.1.0 projects. |
If you content include in csproj (e.g. those upgrading from 9.0.0), and we add in static assets.targets for 9.1.1 you would get errors, came up in the iterations that led us to where we are now. Some history here #11211 |
* Ensure Umbraco static assets included when publish --no-build Closes #11662 * Bump version to 9.1.1
Which exact Umbraco version are you using? For example: 9.0.1 - don't just write v9
9.1.0
Bug summary
See title.
Workaround
don't
--no-build
when publishing, you can even skip thedotnet build
step and justdotnet publish
as long as--no-build
is not present (9.1.0+)Specifics
No response
Steps to reproduce
Create a new umbraco 9.1.0 project
Expected result / actual result
lang dir created and populated
This item has been added to our backlog AB#15174
The text was updated successfully, but these errors were encountered: