Closed mikeoliphant closed 2 years ago
It turns out that nanoFramework.M5Core2 v1.0.0 works, so maybe the preview nuget packages aren't aligned with the preview firmware?
It turns out that nanoFramework.M5Core2 v1.0.0 works, so maybe the preview nuget packages aren't aligned with the preview firmware?
In the case of M5Stack to M5Core, there is also a rename portion. So not sure if its just the preview.
I am also currently experiencing this on ESP32 preview when using UnitsNet.Temperature through the AHTXX package.
I think this can be fixed by updating the various Iot.Device.XXX nuget packages to require v4.112.0 of the relevant UnitsNet packages. Not sure why it seems to have to exactly match the version, when they are requesting version >= 4.110.0, though...
For now, you can work around the problem by manually downgrading the UnitsNet nuget packages for v4.110.0.
That's the workaround for the moment. The references update tool has been fixed in the meantime and this will be addressed shortly.
Fixed with nanoframework/nanoFramework.M5Stack#51.
Working now. Thanks @josesimoes!
Details about Problem
Installing nanoFramework.M5Core2 or nanoFramework.M5Core preview nuget packages causes applications to fail to run with "Link failure: some assembly references cannot be resolved!!"
.NET nanoFramework library: nanoFramework.M5Core2 and nanoFramework.M5Core
VS version: VS 2022 Version 17.0.4
VS extension version: nanoFramework Extensions v2022.1.0.6
Description
Looks like maybe an assembly version mismatch in the nuget deps? Relevant bit from the debug log:
I am running on an M5Stack Core2 with nanoframework installed by:
nanoff --target M5Core2 --update --preview --serialport COM3
Detailed repro steps so we can see the same problem
Create new blank ("Hello") nanoframework project.
Verify that it deploys and runs properly
Install pre-release version of nanoFramework.M5Core2 or nanoFramework.M5Core nuget packages
Verify that the application fails to run with assembly resolution errors.