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
Should just be as easy as changing the csproj to the new .NETCore version.
After attempting to convert to .NETCore v3.0.0-preview2, I have discovered that...
MahApps.Metro.IconPacks, MVVMLightLibs, and Microsoft.Xaml.Behaviors.Wpf are not fully compatible yet, while all other nuget packages and API's are ready for the jump.
As for the csproj file, necessary for porting to .NETCore 3, with the current version, it looks like this:
Preliminary research/testing:
Should just be as easy as changing the csproj to the new .NETCore version.After attempting to convert to .NETCore v3.0.0-preview2, I have discovered that...
MahApps.Metro.IconPacks, MVVMLightLibs, and Microsoft.Xaml.Behaviors.Wpf are not fully compatible yet, while all other nuget packages and API's are ready for the jump.
As for the csproj file, necessary for porting to .NETCore 3, with the current version, it looks like this:
Follow this blog for .NETCore csproj changes: http://brianlagunas.com/getting-started-net-core-3-create-wpf-application/
Must update to the new theme manager for MahApps and do the following:
The text was updated successfully, but these errors were encountered: