I added a new setting in bundles.config in v1.1 called ignoreCompilationDebug, set this to false, restart your application. Now Optimus will obey compilation debug = true in the same way as asp.net bundling does normally and output each file individually making it easier to see issues and is live to changes. Set compilation debug to back to false and bundling will be back.
Not quite the same as clearing the cache when a file is updated but probably better for development as you see which file is doing what.
Optimus not detecting changes to css files
I don't know if it's by design, or I'm doing it wrong, but Optimus doesn't detect changes to css files (maybe js files too), until I reboot the site.
Should I set debug=true while developing, or am I missing something?
It would be nice if it happened automatically :)
/Bo
Yeah true, feature request ;)
Hi Bo,
I added a new setting in bundles.config in v1.1 called ignoreCompilationDebug, set this to false, restart your application. Now Optimus will obey compilation debug = true in the same way as asp.net bundling does normally and output each file individually making it easier to see issues and is live to changes. Set compilation debug to back to false and bundling will be back.
Not quite the same as clearing the cache when a file is updated but probably better for development as you see which file is doing what.
Jeavon
Hi Jeavon
Thanks, thats will be enough. It's probably faster than bundling each time
/Bo
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.