Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.3.X
Votes
0
Found in
2018.1.0a1
2018.2.1f1
Issue ID
1066726
Regression
Yes
HttpClient namespace is not recognized in VS with .NET 4.x
Steps to reproduce:
1. Open attached project "HttpBug"
2. Make sure Scripting Runtime Version is set to .NET 4.x
3. Open "main" scene
4. Open "test" script with VS2017
5. Press Attach to Unity
-Notice "The type or namespace name 'HttpClient' could not be found" error appears
Note: using mcs.rsp file with contents "-r:System.Net.Http.dll" allows to run the script without problems in the editor but debugging is still not possible.
Actual result: VS can't find namespace "HttpClient"
Expected result: VS should be able to see "HttpClient" namespace without errors
Reproduced with: 2018.1.0a1, 2018.1.8f1, 2018.2.3f1, 2018.3.0a1, 2018.3.0a8
Didn't reproduce with: 2017.4.9f1
Regressed in: 2018.1.0a1
In 2018.3.0a8 msc.rsp workaround doesn't work (changing the file name to csc.rsp has no effect also)
Visual Studio version is 15.7.6
VSTU version is 3.7.0.1
Comments (4)
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
- ACES Tonemapping causes banding artifacts and negative values in ColorGradingLUT when HDR is enabled and "High Dynamic Range" Grading mode is selected while Android Platform is used
- Android Player freezes when an Audio Source is playing and an incoming call is picked up and then hung up and the Audio Source is started again
- Green success icon is poorly visible in the light Unity theme
- Incorrect input into the Input Field when using Microsoft IME Japanese
- Multiplayer role "ClientAndServer" is displayed without the spaces in the "Play Mode Scenarios" window
travelhawk
Mar 13, 2019 14:44
Suddenly I can't compile anymore....
travelhawk
Mar 13, 2019 14:44
I have the same problem with Unity 2018.2.15f1
imtrobin
Jan 06, 2019 10:33
How is this closed and fixed? I'm seeing the same issue
imtrobin
Jan 06, 2019 10:32
How is this closed and fixed? I'm seeing the same issue