How Addons are handled in load balanced env.:
Some thoughts on how dev env & TFS may look like:
Regarding the update: the web.config should not be updated by Add-Ons (at least it is not recommended and Add-Ons provided by EPiServer don't do this), so you don't need to do anything about web.config. According to your environment description, AppData is going to be synced automatically with DFS which is fine. Database changes will be applied when one of the servers get updated - this is Ok as well. The only thing remaining is modulesbin folder content - it need to be synced between servers manually after the update was installed on one of the servers.
How will AddOn store updates work in a clustered environment?
As far as we've understood the AddOn store updates can change your
- AppData folder
- Modulesbin folder
We have two web servers hosting and they have their AppData and modulesbin locally, AppData and VPP being synced between the two using DFS.
This is pretty standard from what I've seen. When our WEB1 runs an AddOn store update it will change the AppData (which DFS syncs over to WEB2) and it will change the modulesbin on WEB1, web.config on WEB1, and also the database (shared with WEB2).
Multiple questions rise from this
1) The web.config comes from TFS with each deploy, so we need to sync the AddOn-store update from production with what's in TFS somehow?
2) AppData, modulesbin, web.config and database needs to be upgraded in one go, when it's run on web1, it can't be done on web2? the database will already think the addon-store update has been run?
3) What should be stored in TFS?
4) What should be included with each deploy?
All help straightning out our misunderstandings here is very welcomed :)