Forum member

Der-Albert.com

260 posts

Posts by Der-Albert.com

  1. .NET Core 2.0.1, ASP.NET Core 2.0.1 on a Grid Node Server

    Thumbs up. It is now working, without changing anything (besides the update) on the Grid Node Server.

    20 Nov 2017 09:38 UTC

  2. .NET Core 2.0.1, ASP.NET Core 2.0.1 on a Grid Node Server

    Yes, i know the System Account Issue. dotnet build for a ASP.NET Core 2.0.1 project (dotnet new mvc, dotnet run) works on the machine.

    17 Nov 2017 14:08 UTC

  3. .NET Core 2.0.1, ASP.NET Core 2.0.1 on a Grid Node Server

    I forgot to mention, that i installed 3.12.0.13 a part of the reset. But i've installed NCrunch before VS. Would be nice to rerun the init in case of adding or switching VS Versions. I'd set the Env Variable, and it builds not with the same error as before. So, the reset was only a timesink, o…

    17 Nov 2017 11:36 UTC

  4. .NET Core 2.0.1, ASP.NET Core 2.0.1 on a Grid Node Server

    It's getting worse. I reset the Grid Node PC, INstalled .NET SDK, NCrunch, Visual Studio [quote] NCrunch: This project was built on server 'DELL-E-6420' NCrunch was unable to parse this project file because of an unexpected error: Microsoft.Build.Exceptions.InvalidProjectFileException: The d…

    16 Nov 2017 17:56 UTC

  5. .NET Core 2.0.1, ASP.NET Core 2.0.1 on a Grid Node Server

    Now i'm doing a complete reset of the Grid Node Machine. Installing Visual Studio, .NET Core and Grid Node from scratch

    16 Nov 2017 16:26 UTC

  6. .NET Core 2.0.1, ASP.NET Core 2.0.1 on a Grid Node Server

    Hi, i had a more or less running NCrunch Grid Node with 3.12.04 (on Node and Client) building and testing an ASP.NET Core 2.0 projects. Now up upgraded to 2.0.1, nothing works anymore it even does not build. Repro. Optional Update to VS 17 15.4.4 (because of the Templates) File New Pr…

    16 Nov 2017 16:20 UTC

  7. GridNode Server Service loose Credentials after Update

    Hi, just to bring attention to this little problem. If i install an Update to the Grid Node Server, then the entered Credentials for the Service are removed and then the build and running test is not working anymore (at least for .NET Core 2 Projects). As a Workaround i have to reenter the …

    18 Oct 2017 07:43 UTC

  8. Unable to run tests with .NET Core 2.0 referencing .NET Standard 2.0

    Hi Remco, of course .... first thought "Running not as a Service, i switched that to the Local User Account and it worked".... well, lets take a look to be sure. No, is running under local System. WTF. So one of the Upgrade Installs, uninstalls, and reinstalls killed the LogOn Account Data wh…

    08 Sep 2017 08:25 UTC

  9. Unable to run tests with .NET Core 2.0 referencing .NET Standard 2.0

    3.12.1 does not fix this problem. Also, i'm sure .NET Standard 2.0 Builds worked in an earlier version of 3.11 and the same machine. Now we moved all our .NET Core/.NET Standard Projects to 2.0 and i have to run the test locally on my machine instead of the node. which hurts the performance a little…

    08 Sep 2017 07:11 UTC

  10. Unable to run tests with .NET Core 2.0 referencing .NET Standard 2.0

    .NET Core/Standard 2.0 Grid Node Build is totally broken. With 3.11.9/5 it worked before. The NuGet Package Resolution seems broken. I'm getting weird of missing NuGet Packages in my UserProfile, and from the Visual Studio Installation Path. Yes, the errors are technically correct (it is an o…

    08 Sep 2017 06:59 UTC

  11. Installing NCrunch in VS 2017 Preview 3

    [url=https://ncrunch.uservoice.com/forums/245203-feature-requests/suggestions/19682887-support-multiple-visual-studio-2017-installations]https://ncrunch.uservoice.com/forums/245203-feature-requests/suggestions/19682887-support-multiple-visual-studio-2017-installations[/url]

    14 Aug 2017 11:46 UTC

  12. Even the simplest .NET Core project fails to build under NCrunch

    Hi, i had just a similar problem. I installed the NCrunch Grid Node Server on a seperate Machine (to offload the work). Installed was i need, VS 2017.3 Preview 7, .NET Core SDK 1.0.4, .NET Core 2 Preview 2 etc. Made lokal Build of a an dotnet new mvc App, for 1.1 and 2.0. Then switc…

    07 Aug 2017 17:37 UTC

  13. NCrunch runs fine in VS 2017.2 and breaks in VS 2017.3 (preview 3)

    And just for completness, no it don't have testet a .NET Core 2.0 project yet.

    03 Jul 2017 15:45 UTC

  14. NCrunch runs fine in VS 2017.2 and breaks in VS 2017.3 (preview 3)

    Hi, i think i have a nice one ;) I have a .NET Core 1.1 with ASP.NET Core 1.1 project. NCrunch builds and run all tests fine with Visual Studio 2017.2 (latest update) With Visual Studio 2017.3 (preview 3) is breaks totally. In the solution are several .NET Standard Projects (from 1.4 to 1…

    03 Jul 2017 15:42 UTC

  15. Two instances of VS2017 installed, NCrunch only install into one

    [url=https://ncrunch.uservoice.com/forums/245203-feature-requests/suggestions/19682887-support-multiple-visual-studio-2017-installations anyone free to upvote ;)]as you wish ... a uservoice entry[/url]

    21 Jun 2017 09:41 UTC

  16. Two instances of VS2017 installed, NCrunch only install into one

    Also to think about, there is a 3.10.2 Preview Version of NCrunch, which has a workaround for the multiple marker problem (have this allday). But i will not test this before the final release, because to much hassle to update.

    20 Jun 2017 15:45 UTC

  17. Two instances of VS2017 installed, NCrunch only install into one

    I don't think that there are many problems with the VSIX Installer. Because the manual deployment is simply Copy & Paste, Unlocking Files, starting devenv. So nothing special. From that Side i can't imagine problems for that. Now you are putting the unhandy work of manuell installation to every …

    20 Jun 2017 15:40 UTC

  18. Two instances of VS2017 installed, NCrunch only install into one

    Maybe i overlook this in a other thread, why you are not using a vsix for the installation? This should solve these kind of problems.

    19 Jun 2017 09:27 UTC

  19. Manual Installation improvement

    1) I think unblocking works only file per file, not sure about this 2) But there are different Filetypes so unblocking all is not possible (this is was i first tried) 3) the directory structure complicates this, because it has to be done in every directory A PowerShell Skript would be nice. But…

    18 May 2017 05:50 UTC

  20. Manual Installation improvement

    Yes, the PowerShell must probably also unlocked bevor running. also it must run as Administrator (which should be checked in the skript). But unblocking one file is easy, unblocking dozens is work.

    16 May 2017 13:29 UTC