I tried the new dnx-watch web, it didn't do anything when changing files. Found a package called nodemon, which will watch the tree and restart dnx web just fine. This is doing what I assume dnx-watch web will eventually do, but when dnx web is restarted, its slow as molasses. Just as slow as when the dnx web call is on first run. Has anyone found a friendly and fast way to develop with this new stack. This is RC 1 and there is no real developer friendly workflow. Please tell me I'm just missing step X. Thanks!
*Workflow clarity: I primarily work on front-end files, namely less, JS and cshtml views. I use gulp to process these changes via watch and perform injections of the resulting outputs, so in the end, I'm only changing static files moreorless. Having to restart dnx web each time for this is painfully slow.
If you are working only on *.js/*.css/*.cshtml, then you do not need to restart DNX.
You could just have your gulp:min task and be on your merry way (if you even need it). I would definitely add another task to do bower install/npm install when their respective file change however. That would help you a lot.
If you want to restart DNX, I would only restart it when a cs file change.
UPDATE about the removal of design time cshtml compilation
Alright... so... I went to http://github.com/aspnet/dnx and looked for the relevant bugs for you. There was bugs that mentioned that cshtml wouldn't work when updated and the fix was to include an IFileWatcher. This was all fine and pretty until about beta5 where it was removed and postponed to beta8, then rc1, backlog, rc1, rc2.
So... the final answer? It ain't working right now but they know they have to deliver it. So... that's it.
It's broken at the moment.