Tools: Support Xamarin/MAUI Projects (currently requires separate .NET Standard class library)
See original GitHub issueTooling is explicitly blocked at the moment, so we’d need to do some work there to enable migrations.
PM> Add-Migration Test
Startup project 'Phoneword' targets framework 'MonoAndroid'. The Entity Framework Core Package Manager Console Tools don't support this framework.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:15
- Comments:23 (10 by maintainers)
Top Results From Across the Web
Tools: Support Xamarin/MAUI Projects (currently requires ...
Tools : Support Xamarin/MAUI Projects (currently requires separate .NET Standard class library) #7152. Open. Tracked by #22945.
Read more >Will .Net MAUI be comptabile with .NET Standard 2.0?
My question is, will .NET MAUI be compatible with .NET Standard 2.0 class libraries? Yes, because, as it was mentioned in comments, ....
Read more >Manually upgrade a Xamarin.Forms app to .NET MAUI
In Visual Studio, create a new .NET MAUI class library project of the same name as your Xamarin.Forms library project. This project will ......
Read more >Cross-platform targeting for .NET libraries
NET and .NET Standard targets .NET and .NET Standard targets are the best way to add cross-platform support to a .NET library.
Read more >Switching Your Xamarin Project to Standard Class Projects
There are lots of differences between using a Standard Class/Portable Class Library (PCL) and Shared projects in a Xamarin solution.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@plamenkoyovchev This issue is in the Backlog milestone. This means that it is not going to happen for the 3.0 release. We will re-assess the backlog following the 3.0 release and consider this item at that time. However, keep in mind that there are many other high priority features with which it will be competing for resources.
@bricelam That walkthrough needs some love because it makes no mention about the need for the dummy console project and makes no mention of getting started with how migrations will work specifically in a Xamarin project. I will give it some praise though because it mentioned a couple of things needed in the linking behaviour, but this need for a separate console project and how to use it just isn’t there. I’d suggest updating the walkthrough document to include this information.