Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EmbeddedResourceExtractAttribute #2

Open
Hendy opened this issue Jul 5, 2018 · 0 comments
Open

EmbeddedResourceExtractAttribute #2

Hendy opened this issue Jul 5, 2018 · 0 comments

Comments

@Hendy
Copy link
Owner

Hendy commented Jul 5, 2018

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant