I'm using VS2017 on a solution that contains only 4.6.1 projects. Since v3.6 nCrunch indicates that one of the applications is using 4.6.2 and the corresponding framework should be installed:
[img=http://i.imgur.com/CqGus8N.png]Dialogue[/img]
http://imgur.com/CqGus8N
I was in a hurry, so I just installed the framework (had to reboot) and now it works.
Remco NCrunch Developer
#10044
20 Mar 2017 09:35 UTC
Hi,
Thanks for sharing this problem.
This is caused by NCrunch failing to correctly detect the versions of .NET stored on your system. I thinks that .NET v4.6.2 is installed, though based on the error you've shown, this doesn't look to be the case.
Would you be able to check something for me in your registry? I need to know the value of the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full\Release
Installing .NET v4.6.2 will solve this problem. The problem is not related to the version of the framework you are using for your projects (NCrunch will still use v4.6.1 for these projects). This is coming from the engine host itself.
Thanks for sharing this problem.
This is caused by NCrunch failing to correctly detect the versions of .NET stored on your system. I thinks that .NET v4.6.2 is installed, though based on the error you've shown, this doesn't look to be the case.
Would you be able to check something for me in your registry? I need to know the value of the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full\Release
Installing .NET v4.6.2 will solve this problem. The problem is not related to the version of the framework you are using for your projects (NCrunch will still use v4.6.1 for these projects). This is coming from the engine host itself.
Remco NCrunch Developer
#10045
20 Mar 2017 09:41 UTC
Atreyu wrote:I was in a hurry, so I just installed the framework (had to reboot) and now it works.
Thanks, don't worry about retrieving the version number then. It looks like the v4.6.2 detection change introduced in NCrunch v3.6 was made based on misleading information. I guess I'll need to roll this back. Thanks for bringing it to my attention.
The registry value is (now)
The version paths are
60636
The version paths are
v4
Client
1033
1043
Full
1033
1043
v4.0
ClientI had the same problem - I have VS 2017 RTM installed but it didn't detect 4.6.2 installed. It worked after installing the redist and rebooting, though.
Post a reply
Log in to reply.