U4-2462 - Does the app_plugins manager monitor file changes?

Created by Per Ploug 04 Jul 2013, 12:40:50 Updated by Shannon Deminick 24 Jul 2014, 22:01:04

Relates to: U4-5312

If I built a property editor .js file, I need to hit the web.config file for it register properly


Shannon Deminick 05 Jul 2013, 04:18:34

Yup you will have to restart the app pool, it would be quite difficult to add property editors in real time since everything is loaded and registered on startup with the resolvers and after startup the resolvers are 'frozen' which means they cannot be modified. I think there would be adverse affects if we were to change these collections at runtime and there would be an overhead for monitoring these files when they really only change once in a while. Also, we always restart the app pool when we install packages which is where these things will normally come from.

I'm going to change this to a feature request and change the priority as I don't believe that it should really be implemented but happy to discuss.

Shannon Deminick 05 Jul 2013, 04:21:36

The one thing we could do instead of modifying collections at runtime is monitor the manifest files and restart the app pool when they change just like a .config file? But again, there will be file monitoring overhead for things that only ever change during development so I don't think it is worth the overhead. I also need to implement the 'auto' manifest idea that generates one based on the js files found... but that would only be able to be generated if the app pool recycles.

Robert Stocks 03 Sep 2013, 14:07:16

could you enable the file monitoring (and auto restart) only when debug="true" that would avoid the overhead on a live site but provide the fast development turnaround on a dev site.

Shannon Deminick 04 Sep 2013, 01:34:35

It can be done, we running in full trust only for v7 so putting file system watchers on is ok and I like the idea of only having this done when in debug mode... ace idea.

Sebastiaan Janssen 24 Feb 2014, 09:05:12

With the updates already done in 7.1 to avoid the browser cache issues I'll leave this issue open for now but not assigned to v7.1.0. Shannon can determine if it's still going to be implemented.

Shannon Deminick 08 Jun 2014, 17:02:28

the package.manifest file is now being watched, the app is restarted when they are changed. Now need to look at css/js files and ensuring that we cache bust properly

Mark van Schaik 06 Jul 2014, 20:08:22

having issues with umbraco and firebug, only after creating a property editor (even after then removing the files etc) - see here for more info http://our.umbraco.org/forum/umbraco-7/developing-umbraco-7-packages/54235-Problem-creating-property-editors-too-much-recursion

Priority: Task - Pri 1

Type: Feature (request)

State: Fixed

Assignee: Shannon Deminick

Difficulty: Normal


Backwards Compatible: True

Fix Submitted:

Affected versions: 7.0.0

Due in version: 7.1.5


Story Points: