Installing Umbraco.Cms 10.5.1 startup.cs contains .AddDeliveryApi() and that's not in v10!
See original GitHub issueWhich Umbraco version are you using? (Please write the exact version, example: 10.1.0)
10.5.1
Bug summary
I Installed a Vanilla 10.5.1 to trigger an upgrade from a V8 site… I used Visual Studio to search for the Umbraco Project template and specified the version as 10.5.1 and added db connection string
Project created successfully
went to run the project and got error:
IUmbracoBuilder does not contain a definition for ‘AddDeliveryApi’ and no accessible extension method ‘AddDeliveryApi’ accepting a first argument of type ‘IUmbracoBuilder’ could be found (are you missing a using directive or an assembly reference?)
services.AddUmbraco(_env, _config) .AddBackOffice() .AddWebsite() .AddDeliveryApi() .AddComposers() .Build();
looking at startup.cs it has the AddDeliveryApi() called… commenting out made everything ok, but just wondered if something got merged back into V10 or something by mistake…
anyway thought I’d raise it in case it were a thing…
Specifics
The contrib branch of V10 doesn’t appear to have the issue.
Steps to reproduce
Yeah install 10.5.1 and try to dot net run it, should get the error above
Expected result / actual result
You’d expect the latest version of v10 series to just work after installing it.
Issue Analytics
- State:
- Created 3 months ago
- Comments:5 (4 by maintainers)
@marcemarc it’s no interruption 😄 it’s a valid point. It would be nice to be backwards compatible in the templates… but it’s a right mess to implement (to say the least).
Thanks @kjac @abjerner - yes enthused by CG I had upgraded to V14 templates on my machine 😃
I have always used the command line and Paul’s script before, I don’t know why I tried it from VS - showing off?
Anyway that makes perfect sense
Even though you type the version you want here, it uses the latest templates as you say…
generally speaking, people will be installing the latest version anyway from the latest templates? I guess the LTS is the only vague element of confusion, but yeah, I won’t do this again! sorry for the interruption!