You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* FIXED: Fixed syntax error at token '-' in: IL_002d: ldc.r8 -nan(ind) with "return Double.NaN"
Through "Single + Double NaN token patching" option. Issue #158.
```
.field = float32(-nan(ind)) -> 0xFFC00000
.field = float64(-nan(ind)) -> 0xFFF8000000000000
ldc.r8 -nan(ind) -> 00 00 00 00 00 00 F8 FF
ldc.r4 -nan(ind) -> 00 00 C0 FF
```
* FIXED: NuGet packages are not visible as installed when DLLExport enabled for project.
Issue #152.
* FIXED: Concurrency Issue with Parallel Project Builds. Issue #73.
* FIXED: Fixed the first phase of the build when restoring. Related issue #159.
* FIXED: Fixed VS NuGet PM possible error:
"You cannot call a method on a null-valued expression."
* CHANGED: Improves package integration. PR #161.
- Updated logic for packages through `-pkg-link` key.
- Removed `-force` key from the project files
if it was pushed together with other commands for manager.
Steps to reproduce:
Create demo project with function, which returns
DllExport -version
: 1.7.1With Visual studio 2017 it works. I have tried to start development prompt:
Same code does not work with Visual Studio 2019.
I have tried to override this by modifying project settings and enforcing specific tool version, like this:
After that project compiled in both Visual studios.
Suspect some ildasm bug, at least looks somehow similar to:
#128 (comment)
=>
https://developercommunity.visualstudio.com/content/problem/545431/ildasmexe-regression-with-infinum-floating-point-v.html
Is this the same problem perhaps ?
I have vs2019 16.6.0, but there is update available, need to try it on.
The text was updated successfully, but these errors were encountered: