Started seeing an odd issue this week, where my local environment stops after Umbraco calls FswChanged in Core.Manifest.ManifestWatcher. Typically happens straight after a build, before the site starts.
Builds also seem a lot slower than last week, the only environment changes are a Windows update to 2004, and updating VS to 2019 Community v.latest.
ManifestWatcher does what it says on the box - watches for changes to package.manifest files in /AppPlugins. Nothing is changing in AppPlugins as part of the build, yet something is causing the FswChanged method to fire, resulting in the shutdown.
Anyone have any ideas where to look or what to poke? AI event is here
Exception causing IIS shutdown - Umbraco.Core.Manifest.ManifestWatcher.FswChanged
Started seeing an odd issue this week, where my local environment stops after Umbraco calls FswChanged in Core.Manifest.ManifestWatcher. Typically happens straight after a build, before the site starts.
Builds also seem a lot slower than last week, the only environment changes are a Windows update to 2004, and updating VS to 2019 Community v.latest.
ManifestWatcher does what it says on the box - watches for changes to package.manifest files in /AppPlugins. Nothing is changing in AppPlugins as part of the build, yet something is causing the FswChanged method to fire, resulting in the shutdown.
Anyone have any ideas where to look or what to poke? AI event is here
N
is working on a reply...