fluentmigrator
Can not resolve reference `Microsoft.Identity.Client` on Xamarin.Forms
When updating from 3.2.15 to 3.2.16 our Xamarin.Forms solution cannot build because of the current error :
Can not resolve reference: Microsoft.Identity.Client, referenced by Microsoft.Data.SqlClient. Please add a NuGet package or assembly reference for Microsoft.Identity.Client, or remove the reference to Microsoft.Data.SqlClient.
Works perfectly with version 3.2.15. We don't want to add the specified nuget package so we will stick with version 3.2.15.
Information:
- OS: Windows 10, Android
- Platform: Net Standard 2.0
- FluentMigrator version 3.2.16
- FluentMigrator runner : 3.2.16
- Database Management System : SQLite
There were no SQLite specific features added in 3.2.15 so that should be fine for now. Thanks for reporting this.
I have not built a Xamarin Forms application before. Can you tell me how to set that up? It looks like the Xamarin.Forms Todo app uses SQLite. https://github.com/xamarin/xamarin-forms-samples/tree/main/Todo
Separately, can you tell me what TFM you're using when you say your Xamarin.Forms solution cannot build? Could it be as simple as you have put third party stuff in a specific TFM when it should go in a more general TFM so it can be transitively included?
I have not built a Xamarin Forms application before. Can you tell me how to set that up? It looks like the Xamarin.Forms Todo app uses SQLite. https://github.com/xamarin/xamarin-forms-samples/tree/main/Todo
Separately, can you tell me what TFM you're using when you say your Xamarin.Forms solution cannot build? Could it be as simple as you have put third party stuff in a specific TFM when it should go in a more general TFM so it can be transitively included?
We're targeting .net standard 2.0 in our solution and we are using the Mono.Data.Sqlite.dll (included with Xamarin SDK) instead of the package sqlite-net-pcl provided in the Xamarin.Forms Todo. Maybe the use of this dll could lead to this error.
@schambers Can you review closing this? Looks like it was a dll incompatibility issue and other people have not had the same experience.
