Skip to content

Fix upgrade behavior for asp.net runtime in hosting bundle #36382

Closed
@wtgodbe

Description

@wtgodbe

The hosting bundle currently includes the .net runtime bundle, and the asp.net runtime .msi's. This means if you install Hosting bundle version x.y.0, then .net runtime version x.y.1 & asp.net runtime version x.y.1, the .net runtime will remove the x.y.0 version installed by the hosting bundle, but the asp.net runtime will not. We should consider including the asp.net runtime bundle, rather than the .msi's, in the hosting bundle. We should also think of a way to allow Microsft Update (MU) to push out updates for the hosting bundle (today it sends out the individual runtime bundles). The current problem is that there's no way to know what options the user selected when first installing the hosting bundle, when we push out an automatic update for it.

CC @joeloff @jamshedd

Metadata

Metadata

Assignees

Labels

area-networkingIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsfeature-installersIncludes: Installers

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions