4 ms·
As the article talk mentions it as well; I wonder how good it scales for long running binaries and how well it integrates with stuff like .net native. I mean do
by maxpert 9y ago
As the article talk mentions it as well; I wonder how good it scales for long running binaries and how well it integrates with stuff like .net native. I mean doing artificial demos on a dll is cool, but how well will it scale for say tracing bug in say a key-value store than runs for days and then crashes.
- ComputerGuru 9y agoAs far as I know, .NET Native isn't really something you're supposed to be running for development; just a target you compile to for maximum performance that should produce identical results (think of it as an uber-release mode).
- pjmlp 9y agoMicrosoft advises to regularly test .NET Native builds, to ensure UWP apps work properly when compiled at the store level.
- ComputerGuru 9y agoThat’s correct. I just imagine the kind of cases that would need a time travelling debugger _and_ only occur with .NET Native are not too many.
- Const-me 9y agoI’ve found and reported multiple critical bugs in .NET Native compiler. http://stackoverflow.com/q/34187890/126995 http://stackoverflow.com/q/34187890/126995 https://github.com/Const-me/EsentSerialize/commit/ea2cc7be58cdea02cf43d6e344317bbcd1643552 https://github.com/Const-me/EsentSerialize/commit/ea2cc7be58... The third one (only reported via e-mail), .NET Native fails to marshal custom COM interfaces implemented in C# classes to C++ libraries, at least on ARM for Win10 IoT. Maybe .NET Native should produce identical results, but in practice it doesn’t always do that.