Forum member
fsdschmidt
24 posts
Posts by fsdschmidt
-
Solution Filter
Ok, thanks for your fast reply. The advantage of this limitation is that I can see if my changes effects the whole unfiltered solution and if tests runs on grid node it's ok. :)
26 Feb 2021 06:57 UTC
-
Solution Filter
Hi, we have larger solutions and I use the solution filter feature (slnf) of Visual Studio for better performance. All works fine but seemingly NCrunch ignores the filtered solution, builds and tests all projects. Are solution filter unsupported? Regards, Micha
25 Feb 2021 13:27 UTC
-
ASP.NET Core Build
The problem has gone. I've just updated to the current server and client version of NCrunch and now everything is fine! Thanks for your support. Regards, Micha
21 Aug 2019 12:01 UTC
-
ASP.NET Core Build
Thanks for your suggestion. I tried different PropertyGroups, also inside of the first imported props file. Unfortunately it has no effect, same build error.
21 Aug 2019 06:04 UTC
-
ASP.NET Core Build
Hi Remco, how could I completely deactivate TypeScript under NCrunch? I could not find any setting for TypeScript. The grid node is our build server which builds the same projects and afterwards does the same tests. The service user for grid node and build service is also identical. The grid n…
20 Aug 2019 13:56 UTC
-
ASP.NET Core Build
Hi, our two ASP.NET Core projects won't build at our grid node. Locally all is fine but at our build server we get the following error: NCrunch: This project was built on server '...' ..\..\..\..\..\..\..\Program Files (x86)\Microsoft SDKs\TypeScript\3.5\build\Microsoft.TypeScript.targets (21…
20 Aug 2019 06:35 UTC
-
VS 2017 and VS SDK
Hi Remco, thanks for your fast support. Disabling VS SDK tools did the trick for us too. Now all is fine with VS 2017 and VS SDK. Micha
09 Jun 2017 08:09 UTC
-
VS 2017 and VS SDK
Hi! we build and tested our solution successfully with VS 2015. Now, we switched to VS 2017 and have some trouble with VS SDK tools. We suspect MSBuild could not find the CreatePkgDef.exe, because if we start the tool manually from command line all is fine. Do you have any ideas? Creating inte…
07 Jun 2017 09:50 UTC
-
Inconsistent compiler results
Yes the workaround works for us. Now all is fine, thanks for your great support!
02 Mar 2017 05:21 UTC
-
Inconsistent compiler results
Ok was a bunch of work, but now I have a simple example test project with only one little test and it produces the error: using System.Collections.Generic; using Microsoft.VisualStudio.TestTools.UnitTesting; namespace UnitTestProject1 { [TestClass] public class UnitTest1 { …
01 Mar 2017 14:53 UTC
-
Inconsistent compiler results
Yes both machines use x64 processors, my local machine is a Windows 7 VM on a MacBook Pro with i7, but I don't think this matters and I am using the machine for years. We have 22 projects in this solution and the different IL hash is only processed for our single project with unit tests. Here ar…
01 Mar 2017 06:53 UTC
-
Inconsistent compiler results
No we do not use the log4net library in this project. Actually we have only one developer machine and one server machine in the grid, it´s only to get the load from developer machine. I´ve just realised that the warning only occurs if I enable the server and the local machine in the Distributed Proc…
28 Feb 2017 13:16 UTC
-
Inconsistent compiler results
Faster than expected the problem returns on another branch of the same project. Now I dumped both assemblies on the same machine and the only differences are the MVID and Image base comment. I do not find any coherence when the problem occurs. Yesterday it was consistent the whole day, today the…
28 Feb 2017 10:15 UTC
-
Inconsistent compiler results
Oh good idea to use the ildasm from one machine to reduce ildasm specific differences. Unfortunately today all is fine, but I´m sure the problem will return and then I will get a new dump.
28 Feb 2017 07:56 UTC
-
Inconsistent compiler results
On my local machine the IL comments are in english, on the grid build machine the comments are german. For example: // Copyright (c) Microsoft Corporation. All rights reserved. vs. // Copyright (c) Microsoft Corporation. Alle Rechte vorbehalten. Could the language mix be a problem for …
27 Feb 2017 13:13 UTC
-
Inconsistent compiler results
Hi Remco, now my problem is back and I compared the IL-dumps. The differences existing only inside of IL comments and are mostly based on different cultures. But also the reported MVID and image base are different: // MVID: {FC9438AD-BD3A-4041-823C-CE76E499400C} // Image base: 0x00D80000 l…
27 Feb 2017 10:30 UTC
-
Inconsistent compiler results
Hi Remco, thanks for your quick response! Now I know how to investigate the problem but interestingly the problem is gone. If it returns I will look at it. Regards, Micha
22 Feb 2017 10:02 UTC
-
Inconsistent compiler results
Hi, NCrunch reports "Compiler results are not consistent between machines in the grid" but only for our test project, all other projects are fine. We have VS 2015 Update 3 installed locally and on grid server. How could we analyse what is going wrong? Regards, Michael
21 Feb 2017 09:56 UTC
-
Solution without metrics
So I´ve found the problem and now NCrunch works normal. In this solution we set the PdbFile property for all projects to custom paths: <PropertyGroup> <PdbFile>$(PATHVAR)..\Symbols\$(AssemblyName).pdb</PdbFile> </PropertyGroup> But unfortunately VS writes the symbol in addition also to the …
04 Jul 2016 13:36 UTC
-
Solution without metrics
The new test project is a good approach, the metrics are fine for this project. But when I reference one of the other assemblies and test through real code, I see no metrics and no markers inside our business logic. But the calling test has still markers! I will compare the project files from both t…
01 Jul 2016 11:34 UTC