It is very useful, but the price after the trial ends is way to steep. I'm not going to hand out 30 bucks when I am only coding free stuff. There should exist an open source license or something which is free/very cheap.
This is one of those tools where you don't think it offers much - until you start using it. Then you can't live without it! One useful side-effect of it is that you're virtually always up to date and no longer have to perform Save All every few seconds in case Visual Studio crashes. Even if you have build errors it will at least have already saved your files.
A very useful tool. The continuous build is my favorite feature. Never having to wait for the error list to update or for the application to compile when I'm ready to run it is incredible. I'll definitely be picking up a license.
Not bad, except the continuous saving dramatically slows my typing ability, so I had to disable that option. At least the compile upon manual saving is an option. Also, it crashed Visual Studio when I created a RIA service method with an unsupported parameter by mistake (it was a generic list type). The work-around was to use the VS build system to see what was going on.
[Edit] One other thing: When editing a Silverlight page, the auto save, or even when I continually Ctrl-S save, causes a build, and the visual designer keeps erring out until I'm done, interrupting my typing and ability to click controls to jump around (because errors clear the designer). If this extension could some how run in the background without interrupting my typing during auto save (a setting to run slower?), or not auto-build while editing a XAML file (while it's focused) I'll give it more stars. ;)
[Edit] Sorry, but now there's a new compiler issue ... I'll post it in the Q and A.
This is such an awesome tool, i guarantee you wont be able to live without it, it is so much beautiful a productive to see your errors in error window immediately and not wait for whole project to compile.
it is also very intelligent as it only compiles needed files, so unchanged files wont be touched, and that is another reason to speed up your work flow.
support is also great, even it is still Beta, Alex from Red-gate answered my concerns immediately, and he keeps updating it regularly. this is one of my best tools in my arsenal from now on, I cant live without it.
Not sure why it's saying that - I do see the same; but if I install it directly in the visual studio extensions manager from the gallery the version in the eventual manifest is correct at .1585.
Does this seem to be causing you a specific problem?
Unfortunately .NET Demon doesn't play nice with the Code Rush Unit Test runner. The latter won't wait for the build to finish and report "Build failed". Seems to me that it can potentially be something to do with how .NET Demon replaces the build system.
Is there something you can do about it? I have also raised the issue on the CodeRush issue tracker at http://www.devexpress.com/Support/Center/Question/Details/Q474943
Hi i am having a problem with the latest version of .NET Demon, I will try to walk through the issue i am having..
The Auto refresh works for me as long as i have focus for a particular '.cshtml' file. Once i tab into a '.css' file '.NET Demon' would only recognize the changes made to the '.css' file. From that point any changes to the '.cshtml' file does not trigger a auto refresh. This is really frustrating because the only reason i bought this for the auto refresh feature.
I love the tool, but it doesn't seem to be trigger project file save. When I add a file and edit it - it builds in the background, but quite often it won't save the project file so I have to manually do a Save All.
I was looking into this and you're right--from what I've tested so far, if you add or remove of references when only "save continuously" is enabled, the changes do not get saved. I've logged a bug for this with reference NEP-693--so sorry for the inconvenience but thank you for bringing it to our attention!
I changed the generic constraints on an interface, saved the file and got no compile errors regarding implementations not using the same constraint.
When I try to load the page in IIS, I get a compile error then. Easily fixed but would be nice to get this error in the IDE instead of when it is compiled by ASP.NET?
public interface IMyInterface
public void DoStuff<T>(Guid id) where T : class;
public class MyClass : IMyInterface
public void DoStuff<T>(Guid id) where T : MySubType
Not sure why, but recently have been noticing a lot more deadlocks in VS 2012.. the dreaded "Microsoft Visual studio is busy". But its busy doing nothing at all. Finally got around to attaching another visual studio to the first one to ahve a look at the call stack and lo and behold..
> mscorlib.dll!System.Threading.Monitor.Wait(object obj, int millisecondsTimeout, bool exitContext) + 0x6a bytes
mscorlib.dll!System.Threading.Monitor.Wait(object obj, int millisecondsTimeout) + 0x28 bytes
mscorlib.dll!System.Threading.ManualResetEventSlim.Wait(int millisecondsTimeout, System.Threading.CancellationToken cancellationToken) + 0x397 bytes
mscorlib.dll!System.Threading.Tasks.Task.SpinThenBlockingWait(int millisecondsTimeout, System.Threading.CancellationToken cancellationToken) + 0xdb bytes
mscorlib.dll!System.Threading.Tasks.Task.InternalWait(int millisecondsTimeout, System.Threading.CancellationToken cancellationToken) + 0x1f5 bytes
mscorlib.dll!System.Threading.Tasks.Task.Wait(int millisecondsTimeout, System.Threading.CancellationToken cancellationToken) + 0x8d bytes
mscorlib.dll!System.Threading.Tasks.Task.Wait() + 0x36 bytes
RedGate.Neptune.Core.dll!RedGate.Neptune.Utils.TaskUtil.WaitForResult<RedGate.Neptune.WorkerControl.BuildJob>(System.Threading.Tasks.Task<RedGate.Neptune.WorkerControl.BuildJob> task) + 0x4f bytes
RedGate.Neptune.Core.dll!#MB2b.#TGec.#y2.#EGFc() + 0x8d bytes
RedGate.Neptune.Utils.dll!RedGate.Neptune.Utils.ErrorCatching.DoWithHandling(System.Action todo) + 0x71 bytes
RedGate.Neptune.Core.dll!#MB2b.#TGec.#AGFc() + 0xbc bytes
System.ServiceModel.dll!System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(object instance, object inputs, out object outputs) + 0x907 bytes
It seems that changing the Configuration from Debug To Release doesn't trigger a rebuild of projects that are not built for the Release Configuration. Is this right?
Or are I'm missing a setting.
Thanks in advance Thomas Stocker
Would be cool as a feature, because sometimes I switch from Debug to Release and it would be cool if the Compiler resynchronizes, but for me this isn't so important because I work 99% in Debug Mode, but I have to remember when I switch the Configuration to make a recompile, because else some strange behaviours can occur..
we are using RazorGenerator a lot to create embedded Helpers, the biggest problem is that we have to do manual Build when we modify the cshtml.file so that modifications can be added to assembly, this is very crucial, thanks alot in advanced.