Open cbagpipe opened 2 years ago
Seeing the same issue on ESP_WROVER_KIT 1.8.0.534 :
I debugged while taking System.IO.FileSystem into my solution and the static field InvalidPathChars remains null. https://github.com/nanoframework/System.IO.FileSystem/blob/0ccac9e0ecf10844f64ad90b942407dcba47c439/System.IO.FileSystem/Path.cs#L38
Suffering from this bug again.
I have static Helpers
class with static Crc
class in it with static property. So, this property remains null and debugger no stopping inside static constructor.
Workaround → made class a singleton
This static initialization can be very complex. That's the reason why this issue is still open... I've start looked into it and it requires a serious amount of hours to get to the bottom of it.
Library/API/IoT binding
BCL
Visual Studio version
VS2022 (17.3.4)
.NET nanoFramework extension version
2022.2.0.41
Target name(s)
ESP32_REV0
Firmware version
1.8.0.594
Device capabilities
Description
Static field contained inside class, initialized in static field of
Program
class, not populated with value.How to reproduce
gettingNull
variableExpected behaviour
variable
gettingNull
MUST be equal to static fieldtest
Screenshots
Sample project or code
Aditional information
I don't know where to address this bug, so addressing to BCL. If I mistaken, please, fix this issue description.