Hi Remco,
i know, it's the first Version of .net core project support, but it seems quite slow, even when it is only the new project type in an ASP.NET Core on .net 4.6 Solution.
Any Ideas how to improve the experience over time, or is this done and not possible.
Best Regards
Albert
Build/Test Issues
Any Plans to optimize ASP.NET, .NET Core Experience?
Started by Der-Albert.com on 5,296 views
Remco NCrunch Developer
#9984
16 Mar 2017 23:12 UTC
Hi Albert,
If you haven't already, I recommend giving the new version (v3.6) a spin. This included several changes to improve performance around synchronisation of .NET Core codebases.
That aside, can you share any more details about performance issues your experiencing? Which actions seem unusually slow?
If you haven't already, I recommend giving the new version (v3.6) a spin. This included several changes to improve performance around synchronisation of .NET Core codebases.
That aside, can you share any more details about performance issues your experiencing? Which actions seem unusually slow?
No was still on 3.5, with 3.6 i have that problem http://forum.ncrunch.net/yaf_postst2072_NCrunch--Core-1-0-1-and-BadImageFormatException.aspx
Remco NCrunch Developer
#10054
20 Mar 2017 22:18 UTC
Ok, I'll try to help troubleshoot the assembly referencing issue in the other thread. When we get you up and running, I'll be interested to learn more about the performance of v3.6 on your system and whether there are any specific areas that need work.
With 3.6/7 it is faster than 3.5, feeling not as fast yet as in normal C# Assemblies, but now i can feel the progress. before that it takes ages even to build the projects.
Remco NCrunch Developer
#10115
24 Mar 2017 08:34 UTC
Der-Albert.com wrote:With 3.6/7 it is faster than 3.5, feeling not as fast yet as in normal C# Assemblies, but now i can feel the progress. before that it takes ages even to build the projects.
If you're able to highlight any areas you feel seem to be significantly slower, I can try to learn more about why this might be the case.
Turning on the track engine performance setting would be very useful for this. You can then see the individual steps NCrunch is taking in pursuit of test execution. If you get any traces that seem longer than they should be, you can also export them and upload them to the contact form on this website, or email them to me.
Post a reply
Log in to reply.