The Visual Studio template “ElmSharp-Beta” uses the wrong TargetFramework
The Visual Studio template “ElmSharp-Beta” uses the wrong TargetFramework
BY 10 May 2018Tizen .NET
When creating a new ElmSharp project, the template uses:
<TargetFramework>netcoreapp2.0</TargetFramework>
This “works”, but may result in the wrong libraries being referenced when packages are installed.
For example, I am building a package (SkiaSharp.Views) that supports various Tizen UI elements that work for both Xamarin.Forms (via renderers) and plain old ElmSharp views. To indicate that this is platform code, is use the “tizen40” lib folder. Obviously, the current TargetFramework will not actually install it and might give an error.
The Visual Studio template “ElmSharp-Beta” uses the wrong TargetFramework
When creating a new ElmSharp project, the template uses:
This “works”, but may result in the wrong libraries being referenced when packages are installed.
For example, I am building a package (SkiaSharp.Views) that supports various Tizen UI elements that work for both Xamarin.Forms (via renderers) and plain old ElmSharp views. To indicate that this is platform code, is use the “tizen40” lib folder. Obviously, the current TargetFramework will not actually install it and might give an error.
I just changed the template to be:
This works now, but not everyone will know this.
BY
16 Apr 2025
Tizen Studio
BY
04 Nov 2024
Tizen Studio
BY
02 Apr 2024
Tizen Studio