Store settings outside asset folder

[Christian Oeing]

Since the package contains a settings asset, when updating it could happen that the current settings are overwritten without noticing. I think a better approach would be to not include it in the package itself, and create the asset automatically if it doesn't exist when the package is imported (say with a method somewhere using "InitializeOnLoadMethodAttribute").

Also, since the asset is inside the folder of the plugin, if when updating we first delete the root folder the settings would also be lost. To avoid that, my personal opinion is that it would be better to create the settings asset outside the plugin folder, even though it's not so "clean".

[Christian Oeing]

It was already possible to have the data bind settings somewhere outside. It had to be inside a Resources folder to be loaded during runtime and it should either be the only one or be named “Data Bind Settings”, so data bind knows which settings file to take.

Nonetheless I removed the settings file from the repository and will not include it in future versions. It is anyway created if none is found, so it should be fine.

[Christian Oeing]

Removing milestone: 1.21 (automated comment)