Issues with AppDomainLifetimeCacheBuster

[shropgov-neil]

I'm using Umbraco 11 with the "AppDomain" setting, which, from tracing the code through Umbraco, seems to just hand off cachebusting to AppDomainLifetimeCacheBuster.

However, no matter what, the cachebuster value is permenantly "v1", and does not change on app restart - this makes the cachebuster useless as, while the internal caches are rebuilt, the browser continues to load it's locally cached version.

Is this an issue your end, or are Umbraco doing something behind the scenes to cause this issue?

[Shazwazza]

The AppDomainLifetimeCacheBuster implementation is very simple: https://github.com/Shazwazza/Smidge/blob/develop/src/Smidge.Core/Cache/AppDomainLifetimeCacheBuster.cs

It generates a one time value of the current datetime ticks

If "v1" is being used, then the cache buster is not actually being set to this cache buster type. Are you referring to assets in the back office of Umbraco or when you are using Smidge on the front-end? And where/how are you setting this cache buster value?

[shropgov-neil]

I thought as much - I'm guessing this is an issue with Umbraco's implementation then.
I'm not setting a version value at all, I just set "CacheBuster": "AppDomain" in appsettings.json, as per their documentation.

This should, in theory, use your AppDomainLifetime class, as per here;
https://github.com/umbraco/Umbraco-CMS/blob/contrib/src/Umbraco.Web.Common/RuntimeMinification/SmidgeRuntimeMinifier.cs#L79

This is on the front end, using SmidgeHelper.Create[Css/JS]Bundle, and the Smidge tag helpers.

[shropgov-neil]

Turns out Umbraco doesn't set the DefaultBundleOptions, it only sets WithEnvironmentOptions() on the explicit bundles created for the back office. I ended up manually configuring the SmidgeOptions with same config for use on the front end.
umbraco/Umbraco-CMS#15165