Great tool to decrease build time in a two orders of magnitude. However, it often does not properly decide what projects in solution should be build, especially in case of a multi-language solution and unit test projects.
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.
Sorry - must have missed this comment. We're always happy to give free licenses for working on open source projects. Just email email@example.com with details of the project and we'll sort one out for you.
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.
Are you supporting silverlight projects too? I have a project which builds perfectly in VS2013 but with .NET Demon extension shows the following error:
(file: C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\WebApplications\Microsoft.WebApplication.targets)
view error screenshot: http://1drv.ms/1i91RfM
Could you provide some hint how to resolve this issue?
Thank you in advance!
Sincerely, David Molnar
Thanks for your post!
I think this issue is related to my post below (.NET Demon builds may fail for projects upgraded to VS 2013). Could you kindly check your project files for anything pointing to the old msbuild path (the new path is in program files) or an older visual studio version?
For more details on the VS upgrade issue, please see here (under 'MSBuild’s New Binaries Location'): http://blogs.msdn.com/b/visualstudio/archive/2013/07/24/msbuild-is-now-part-of-visual-studio.aspx
Msbuild paths have changed in Visual Studio 2013 and this may cause some problems for .NET Demon if you have files that still point to older versions of VS or to the old msbuild path.
For example, you may see the error:
The task factory "CodeTaskFactory" could not be loaded from the assembly "C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Microsoft.Build.Tasks.v12.0.dll".
Could not load file or assembly 'file:///C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Microsoft.Build.Tasks.v12.0.dll' or one of its dependencies. The system cannot find the file specified. xxx\.nuget\NuGet.targets
This error happens when a .nuget package restore file points to the wrong MSBuild tools path. In this case, removing your restore files (particularly Nuget.config and Nuget.targets) from your solution and file system, and then re-enabling package restore should resolve it.
Similar errors can occur if you have either the PlatformToolset or VisualStudioVersion properties set to an older version, but changing their values to “v12.0” should help.
I have a problem with Solution time loading when using .NET Demon with VS2012, though I see no impact when using VS2010. I tried to disable every extension I have but came up, that .NET Demon is a reason.
Is it a known issue? What can I try to do with that?
Hi, sorry for not answering for so long (been on vacs).
I investigated VS Activity Log and unfortunately found nothing fishy, because log is not appended by anything during this slow part of solution loading. If you wish to inspect it, please give me your e-mail so I can send it to you.
I'm also wondering if .NET Demon log can help. But problem there is circular log rewriting (10 pieces of 100Kb) and 1Mb seems not enough to write everything there in 1 log sequence w/o losing tail. Is there a way to increase log file size for .NET Demon? So I could also send Demon's log to you for investigation
Sorry for the delay!
Please do send in your activity and .NET Demon log files (you should actually have multiple files -- all of the text documents in %userprofile%\AppData\Local\Red Gate\Neptune )to us in an email to firstname.lastname@example.org with "Ticket #13290" as the subject.
See near bottom of http://www.devexpress.com/Support/Center/Question/Details/Q457976.
With Save Continuously enabled Add Parameter stops working. The call site doesn't get updated. So my workaround is to disable save until after I've applied the operation. Maybe CodeRush can provide a workaround. I've only just posted the update to my question in the CodeRush support forum.
The latest update should work with VS2013. If you get a build error mentioning NuGet.targets, just get the latest version of that file (which doesn't include the problematic "SetEnvironmentVariable" task).
Neither the RedGate Support or Forums have the .NET Demon product as a choice. Is this product supported?
The Feedback page has had no response for ages to the many great suggestions placed there. Also, no beta or anything for VS2013.
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