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
Attribute to extract embedded resource to the file-system on startup so can have the advantages of embedded resource, but ensure end deployment is the same as non-embedded resource.
Issues to consider: package upgrades with new resources to replace old, and user cusomised assets.
There could be a parameter to indicate the default action if a file already exists. (a package update may require asset files to be overwritten, but config files not to be overwritten). There could also be an appSetting to prevent overwriting.
If overwriting as default:
Asset files known to be correct for the package version in use, but user cusomised files might get replaced - a work-around could be to set an app setting to prevent overwriting, or use a file naming convention for customisations eg:
PackageResource.js
PackageResource.js.cusom <- if exists would take priority over the PackageResource.js
If not overwriting:
The assets files shouldn't be in source control so no issue, but if they are, then they would need to be deleted first so new ones can be extracted.
The text was updated successfully, but these errors were encountered:
Attribute to extract embedded resource to the file-system on startup so can have the advantages of embedded resource, but ensure end deployment is the same as non-embedded resource.
Issues to consider: package upgrades with new resources to replace old, and user cusomised assets.
There could be a parameter to indicate the default action if a file already exists. (a package update may require asset files to be overwritten, but config files not to be overwritten). There could also be an appSetting to prevent overwriting.
If overwriting as default:
Asset files known to be correct for the package version in use, but user cusomised files might get replaced - a work-around could be to set an app setting to prevent overwriting, or use a file naming convention for customisations eg:
PackageResource.js
PackageResource.js.cusom <- if exists would take priority over the PackageResource.js
If not overwriting:
The assets files shouldn't be in source control so no issue, but if they are, then they would need to be deleted first so new ones can be extracted.
The text was updated successfully, but these errors were encountered: