Versions of Target Framework in VS2017 vs. versions of NET Framework is registry
up vote
-1
down vote
favorite
VS2017 has the option Target Framework (project Properties, tab Application) where the default version is set to "NET Framework 4.5.2", the highest is "NET Framework 4.6.1". The registry has similar versions at KEY_LOCAL_MACHINESOFTWAREMicrosoftNET Framework SetupNDP but the list is shorter and the version 4.5.2 is not even included. The regedit.exe on my Windows 10 shows v4FullRelease = 461808, and v4FullVersion = 4.7.03056.
Why is "NET Framework 4.5.2" not listed in the registry? Where does VS2017 take the list of versions from?
c# visual-studio
asked Nov 10 at 18:16
Benny
1
|
show 1 more comment
up vote
-1
down vote
favorite
VS2017 has the option Target Framework (project Properties, tab Application) where the default version is set to "NET Framework 4.5.2", the highest is "NET Framework 4.6.1". The registry has similar versions at KEY_LOCAL_MACHINESOFTWAREMicrosoftNET Framework SetupNDP but the list is shorter and the version 4.5.2 is not even included. The regedit.exe on my Windows 10 shows v4FullRelease = 461808, and v4FullVersion = 4.7.03056.
Why is "NET Framework 4.5.2" not listed in the registry? Where does VS2017 take the list of versions from?
c# visual-studio
asked Nov 10 at 18:16
Benny
1
Ask yourself three smaller questions: 1) what is target framework, 2) what is NDP keys, and 3) what's the relationship between the two. You can easily find previous threads on SO for them. Then the answers for you last questions are super clear, that .NET Framework 4.5.2 shouldn't be there, and VS relies on Developer Pack.
– Lex Li
Nov 10 at 19:38
I revised one of my blog posts, so now it contains enough hints, blog.lextudio.com/…
– Lex Li
Nov 10 at 20:06
the other threads do not address the question. Your link also does not get to the point. If "NET Framework 4.5.2" is bound by Developer Pack meaning it has to be installed then what is the purpose of the registry key which is supposed to reflect the installed versions?
– Benny
Nov 11 at 4:22
Why cannot you distinguish compile-time and runtime? Target frameworks are for compile-time while installed SKUs are for runtime.
– Lex Li
Nov 11 at 4:32
Apparently, when you compile, the referenced assemblies like mscorlib.dll are taken from path tied to Target Framework, so they are used during runtime. The installed Framework as seen in registry has the value for InstallPath which also includes the same assemblies like mscorlib.dll. So the question is when these assemblies (non-CLR) from InstallPath are used?
– Benny
Nov 11 at 18:32
|
show 1 more comment
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
VS2017 has the option Target Framework (project Properties, tab Application) where the default version is set to "NET Framework 4.5.2", the highest is "NET Framework 4.6.1". The registry has similar versions at KEY_LOCAL_MACHINESOFTWAREMicrosoftNET Framework SetupNDP but the list is shorter and the version 4.5.2 is not even included. The regedit.exe on my Windows 10 shows v4FullRelease = 461808, and v4FullVersion = 4.7.03056.
Why is "NET Framework 4.5.2" not listed in the registry? Where does VS2017 take the list of versions from?
c# visual-studio
asked Nov 10 at 18:16
Benny
1
VS2017 has the option Target Framework (project Properties, tab Application) where the default version is set to "NET Framework 4.5.2", the highest is "NET Framework 4.6.1". The registry has similar versions at KEY_LOCAL_MACHINESOFTWAREMicrosoftNET Framework SetupNDP but the list is shorter and the version 4.5.2 is not even included. The regedit.exe on my Windows 10 shows v4FullRelease = 461808, and v4FullVersion = 4.7.03056.
Why is "NET Framework 4.5.2" not listed in the registry? Where does VS2017 take the list of versions from?
c# visual-studio
c# visual-studio
asked Nov 10 at 18:16
Benny
1
asked Nov 10 at 18:16
Benny
1
asked Nov 10 at 18:16
Benny
1
asked Nov 10 at 18:16
Benny
1
asked Nov 10 at 18:16
Benny
1
1
Ask yourself three smaller questions: 1) what is target framework, 2) what is NDP keys, and 3) what's the relationship between the two. You can easily find previous threads on SO for them. Then the answers for you last questions are super clear, that .NET Framework 4.5.2 shouldn't be there, and VS relies on Developer Pack.
– Lex Li
Nov 10 at 19:38
I revised one of my blog posts, so now it contains enough hints, blog.lextudio.com/…
– Lex Li
Nov 10 at 20:06
the other threads do not address the question. Your link also does not get to the point. If "NET Framework 4.5.2" is bound by Developer Pack meaning it has to be installed then what is the purpose of the registry key which is supposed to reflect the installed versions?
– Benny
Nov 11 at 4:22
Why cannot you distinguish compile-time and runtime? Target frameworks are for compile-time while installed SKUs are for runtime.
– Lex Li
Nov 11 at 4:32
Apparently, when you compile, the referenced assemblies like mscorlib.dll are taken from path tied to Target Framework, so they are used during runtime. The installed Framework as seen in registry has the value for InstallPath which also includes the same assemblies like mscorlib.dll. So the question is when these assemblies (non-CLR) from InstallPath are used?
– Benny
Nov 11 at 18:32
|
show 1 more comment
Ask yourself three smaller questions: 1) what is target framework, 2) what is NDP keys, and 3) what's the relationship between the two. You can easily find previous threads on SO for them. Then the answers for you last questions are super clear, that .NET Framework 4.5.2 shouldn't be there, and VS relies on Developer Pack.
– Lex Li
Nov 10 at 19:38
I revised one of my blog posts, so now it contains enough hints, blog.lextudio.com/…
– Lex Li
Nov 10 at 20:06
the other threads do not address the question. Your link also does not get to the point. If "NET Framework 4.5.2" is bound by Developer Pack meaning it has to be installed then what is the purpose of the registry key which is supposed to reflect the installed versions?
– Benny
Nov 11 at 4:22
Why cannot you distinguish compile-time and runtime? Target frameworks are for compile-time while installed SKUs are for runtime.
– Lex Li
Nov 11 at 4:32
Apparently, when you compile, the referenced assemblies like mscorlib.dll are taken from path tied to Target Framework, so they are used during runtime. The installed Framework as seen in registry has the value for InstallPath which also includes the same assemblies like mscorlib.dll. So the question is when these assemblies (non-CLR) from InstallPath are used?
– Benny
Nov 11 at 18:32
Ask yourself three smaller questions: 1) what is target framework, 2) what is NDP keys, and 3) what's the relationship between the two. You can easily find previous threads on SO for them. Then the answers for you last questions are super clear, that .NET Framework 4.5.2 shouldn't be there, and VS relies on Developer Pack.
– Lex Li
Nov 10 at 19:38
Ask yourself three smaller questions: 1) what is target framework, 2) what is NDP keys, and 3) what's the relationship between the two. You can easily find previous threads on SO for them. Then the answers for you last questions are super clear, that .NET Framework 4.5.2 shouldn't be there, and VS relies on Developer Pack.
– Lex Li
Nov 10 at 19:38
I revised one of my blog posts, so now it contains enough hints, blog.lextudio.com/…
– Lex Li
Nov 10 at 20:06
I revised one of my blog posts, so now it contains enough hints, blog.lextudio.com/…
– Lex Li
Nov 10 at 20:06
the other threads do not address the question. Your link also does not get to the point. If "NET Framework 4.5.2" is bound by Developer Pack meaning it has to be installed then what is the purpose of the registry key which is supposed to reflect the installed versions?
– Benny
Nov 11 at 4:22
the other threads do not address the question. Your link also does not get to the point. If "NET Framework 4.5.2" is bound by Developer Pack meaning it has to be installed then what is the purpose of the registry key which is supposed to reflect the installed versions?
– Benny
Nov 11 at 4:22
Why cannot you distinguish compile-time and runtime? Target frameworks are for compile-time while installed SKUs are for runtime.
– Lex Li
Nov 11 at 4:32
Why cannot you distinguish compile-time and runtime? Target frameworks are for compile-time while installed SKUs are for runtime.
– Lex Li
Nov 11 at 4:32
Apparently, when you compile, the referenced assemblies like mscorlib.dll are taken from path tied to Target Framework, so they are used during runtime. The installed Framework as seen in registry has the value for InstallPath which also includes the same assemblies like mscorlib.dll. So the question is when these assemblies (non-CLR) from InstallPath are used?
– Benny
Nov 11 at 18:32
Apparently, when you compile, the referenced assemblies like mscorlib.dll are taken from path tied to Target Framework, so they are used during runtime. The installed Framework as seen in registry has the value for InstallPath which also includes the same assemblies like mscorlib.dll. So the question is when these assemblies (non-CLR) from InstallPath are used?
– Benny
Nov 11 at 18:32
|
show 1 more comment
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53242004%2fversions-of-target-framework-in-vs2017-vs-versions-of-net-framework-is-registry%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Ask yourself three smaller questions: 1) what is target framework, 2) what is NDP keys, and 3) what's the relationship between the two. You can easily find previous threads on SO for them. Then the answers for you last questions are super clear, that .NET Framework 4.5.2 shouldn't be there, and VS relies on Developer Pack.
– Lex Li
Nov 10 at 19:38
I revised one of my blog posts, so now it contains enough hints, blog.lextudio.com/…
– Lex Li
Nov 10 at 20:06
the other threads do not address the question. Your link also does not get to the point. If "NET Framework 4.5.2" is bound by Developer Pack meaning it has to be installed then what is the purpose of the registry key which is supposed to reflect the installed versions?
– Benny
Nov 11 at 4:22
Why cannot you distinguish compile-time and runtime? Target frameworks are for compile-time while installed SKUs are for runtime.
– Lex Li
Nov 11 at 4:32
Apparently, when you compile, the referenced assemblies like mscorlib.dll are taken from path tied to Target Framework, so they are used during runtime. The installed Framework as seen in registry has the value for InstallPath which also includes the same assemblies like mscorlib.dll. So the question is when these assemblies (non-CLR) from InstallPath are used?
– Benny
Nov 11 at 18:32