Plugin update

1. Version Notes

With every new update, I try to make plugin better. For example, adding new features, improving stability, usability and code base structure. When the new version is available, you can find out what’s new in the version  reading version notes.

 

Sometimes in order to implement a new feature or improve code structure I have to change some of the plugin files / folders or method names.Of course, it will be described in the version notes. But if you just click  on the "Update" in the Asset Store, you may get duplicated or conflicted files.

After the new plugin version is downloaded and unpacked to your project, the settings window will be opened automatically in the Inspector view. It for some reason it wasn’t opened after you imported the plugin, go to: WindowGoogle Mobile AdEdit Settings

 

And just press the Update button. If the installation is completed successfully, you will see message as on the picture below.

How to update

It's also a good practise to remove the old plugin version completely before the update. You can do this using the plugin editor window as showed on the screenshot bellow.

Settings File Location

Plugins Settings file is located at:

Assets/Extensions/StansAssetsConfig/Resources

This folder remains unharmed by the plugin removal tool. In case you want to transfer setting to the another project, you can just copy  / paste files from this folder from one project to another.

I case you want manually remove and reinstall this plugin, or even if you also have another Stan's Assets plugins inside your project, you can just remove the following folders:

  • All folders under: Assets/Extensions/ except Assets/Extensions/StansAssetsConfig
  • Assets/Plugins/StansAssets
  • Assets/Plugins/ -  You can remove the whole folder, in case you do not have any other plugins inside your project, or your own files inside the Plugins folder. And if you do, remove  files that are only related to the plugin you want to remove.  This step can be unclear, we are defiantly trying to use understandable naming convention for our files, so it should be easy to determine what files / folder are related to plugin you trying to remove. But that's why we strongly recommend the plugin removal tool usage, since it will be definitely safe for other product you have inside your project.