You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This will not be an easy upgrade since it is only available from .NET 9. But I'm writing it so we don't forget.
The new .MapStaticAssets handles the caching for us, so once we upgrade our JS importing, we will not need to have query versioning for JS files, eg, "./utilities.js?v=1.7.1.0";.
I have tested it on a small project, and the new import mechanism also works for import done by the JS side.
Having a query version doesn't play well with the new .MapStaticAssets:
Meaning at some point we will have to remove all traces of query versions.
This will probably have to be done in the distant future after we remove the .NET 8 LTS version. And not before .NET 9 LTS comes out. So, for now, it is just a nice feature to have.
The text was updated successfully, but these errors were encountered:
This will not be an easy upgrade since it is only available from .NET 9. But I'm writing it so we don't forget.
The new
.MapStaticAssets
handles the caching for us, so once we upgrade our JS importing, we will not need to have query versioning for JS files, eg,"./utilities.js?v=1.7.1.0";.
References
I have tested it on a small project, and the new import mechanism also works for import done by the JS side.
Having a query version doesn't play well with the new
.MapStaticAssets
:Meaning at some point we will have to remove all traces of query versions.
This will probably have to be done in the distant future after we remove the .NET 8 LTS version. And not before .NET 9 LTS comes out. So, for now, it is just a nice feature to have.
The text was updated successfully, but these errors were encountered: