Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.3.X
Votes
0
Found in
Issue ID
1110736
Regression
No
VSCode needs to target 4.7.2 instead of 4.5
https://github.com/Unity-Technologies/vscode-unity-debug/issues/115
https://forum.unity.com/threads/unable-to-locate-net-framework-4-5.554395/
With the targetframework version set in the csproj file as v4.5 it will give this error message in VSCode:
The reference assemblies for framework ".NETFramework,Version=v4.5" were not found. To resolve this, install the SDK or Targeting Pack for this framework version or retarget your application to a version of the framework for which you have the SDK or Targeting Pack installed. Note that assemblies will be resolved from the Global Assembly Cache (GAC) and will be used in place of reference assemblies. Therefore your assembly may not be correctly targeted for the framework you intend.
To resolve it one can change the targetframework version in the csproj, however this will be overwritten by Unity.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor crashes when loading RenderDoc with Graphics API set to OpenGLES2 or OpenGLES3
- [Windows] Development Build with no scenes shows a purple screen when using OpenGLES3 graphics API
- Shader variants take too much memory at runtime
- [HDRP][VFX] Output mesh with default shader is incorrectly sorted before the HDRP fog
- Error "'GamepadSpeakerOutputType' does not exist in the namespace 'UnityEngine'" occurs in the Console when building a project
dizzyhippos
Mar 19, 2019 21:19
As of 3/19/2019 I am still getting this error and have been for weeks now through 3 updates of unity, its getting very frustrating to use this engine.
miniwolf_unity
Jan 08, 2019 13:57
This is going to be back ported to 2018.3, the fix is in the branch. Coming soon™
ArdaZeytin
Dec 30, 2018 11:18
Please fix for 2018.3.X
CrowbarSka
Dec 29, 2018 14:53
Will this be patched into a subsequent 2018.3.X update for those of us who don't intend to use 2019 for certain projects?
CrowbarSka
Dec 29, 2018 14:52
Will this be patched into a subsequent 2018.3.X update for those of us who don't intend to use 2019 for certain projects?