I'm a new smutje and cooking in a german project 'c't-Notfall-Windows 2017' ( heise.de/-3467556 ).
There I have post many helpful reply for other people and found & fix some issues.
Sorry, you are not allowed to post external links. --> Then with detours ;-)
I'm new here, but did not swim in the sausage broth to you, please switch off the restrictions.
Since version 010 of this DotNet.script
added support for Win10.
In our project was implemented v.021 (2016.09.02).
Some guy's post, that the project damage the BuildHost, like stop working security software and else other.
To analyze whether the BuildHost is affected by the bug, we use this CMD command (x86-systems, only the first command):
reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup" /s /f ":\\"
reg query "HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\NET Framework Setup" /s /f ":\\"
If the reply of commands contains wrong value begins with:X:\Windows\...X:\Program Files\...X:\Program Files (x86)\...
...your system is affected by the bug.Scripts to analysis and repair the BuildHost
, I published at ( heise.de/forum/p-29737317/ ) or. ( pastebin.com/eA1HD5wD )
Yesterday I analyzed a LOG and DotNet.script v.021 & latest v.026 from ( win10se.cwcodes.net/projectindex.php ).
The result: Only Win-10 x86+x64 by evaluated '%CopyMode%=4.0' (DotNet 2.0/3.0/3.5/4.5) is affected.
Today I have fixed that reason up to version 027 and run a build successfully.
@ ChrisR & Lancelot
If there is anybody working at version 027 at time, it's recommended to get my v.027 or take over the changes!
Please verify, test and publish the new version on your server.
Größe: 556672 Bytes (0 MB)
Cooking with german ingredients, simply delicious ;-)