1 answer

Got the same error message as you, if I install the package Plugin.Share 7.1.1 to my Xamarin with reference Xamarin.Android.Support.v7.MediaRouter 27.0.2.

To resolve this issue, please install the dependency Xamarin.Android.Support.CustomTabs with version 27.0.2 first, then install the package Plugin.Share 7.1.1.

The reason for this solution:

Just like the error message shows, the default package of Xamarin project
is Xamarin.Android.Support.v7.MediaRouter 27.0.2, which have a indirect dependency Xamarin.Android.Support.Compat (= 27.0.2). However, the package Plugin.Share 7.1.1 also have a indirect dependency Xamarin.Android.Support.Compat (= 25.4.0.2), which lower than the already installed version 27.0.2. So nuget will give you the error NU1107 Version conflict detected for Xamarin.Android.Support.Compat.

In order to use the same version package Xamarin.Android.Support.Compat, we have to update the referencing package Xamarin.Android.Support.CustomTabs to 27.0.2, which is supported by the referencing package Plugin.Share 7.1.1.

So, the solution for this issue is install the Xamarin.Android.Support.CustomTabs 27.0.2 first, then install the package Plugin.Share 7.1.1.

Hope this helps.

See also questions close to this topic

I've written code to read in certain data from a CSV file, perform a PCA analysis on the data with the sklearn library, and then plot the resulting data as a heatmap. The code doesn't show any errors when run, but it also outputs no graph and just a line saying AxesSubplot(0.125,0.11;0.62x0.77).

I'm wondering if Visual Studio is unable to display plots like this and if so what would be a better IDE for me to use for this project. If not can anyone see a problem that would prevent this code from displaying a heatmap? Copying the relevant code below

I'm building a snake game derivative with C++ and OpenGL. I'm using following libraries/headers: glew, glfw, glm and stb_image.
I'm programming for both Windows 10 (Visual Studio 2017) and Ubuntu 16.04. I can build and execute both versions without any issues. But if I hand the executables to a friend neither OS version works. Do I do something wrong when building? Or do I have to also ship the libraries!

Any tips on how to always get a push message to your app in O? It does not need to be delivered "on time", it just have to be processed. My goal is to make and simple external triggered downloader app...

For most viewmodels, it’s common to not try to monitor other lifecyle
events. This is OK since most viewmodels don’t perform any actions and
don’t consume any resources when the view is not present - so these
can just be left to be garbage collected when the system needs the
memory back.

However, besides the custom platform situations, there are still many cases like navigating back from the view model, or (again) navigation away from current viewmodel with its following closing.

Came back from vacation this week (:-( i guess, :-)). Only to find myself a project I can't seem to be able to compile.

I was started as an project from the ASP.NET Core (.NET Core 2.1) Angular template but changed to .NET Framework (4.6.2) as we have some dependencies. My coworker can build and publish the thing to the cloud (Azure) where it also runs as expected.

But I get a lot of build errors, 344 at the moments. All of the same type:

Package System.Text.Encodings.Web 4.5.0 is not compatible with net462 (.NETFramework,Version=v4.6.2). Package System.Text.Encodings.Web 4.5.0 does not support any target frameworks

Now this is straight forward, the package in question (and all the other ones too) does not support .NET Framework.

Why is my coworker able to build this and not me? I've been poking around thinking nuget is to blame. I've got .NET Core 2.1 installed, .NET Framework 4.6.2 (latest 4.7.x too). I've updated Visual Studio (15.7.6) and have Nuget version 4.6.

I am creating a NuGet package via .csproj that contains MSBuild tasks (and I would like not to fall back to .nuspec or .nuproj).

The MSBuild tasks are compiled into one assembly compatible with .NET Standard 1.5 and one assembly compatible with .NET Framework 4.5 (so TargetFrameworks is set to net45;netstandard1.5). Thus, the NuGet package will only be usable by the project compatible with these two .NET versions.

However, I would like the NuGet package to behave like a "meta-package", thereby allowing every project to use it. Indeed, the package does not provide any lib folder, but all the assemblies are in build and they are meant to be used by MSBuild only.

Moreover, I have another NuGet package that only contains .targets and .props files, which depends on the NuGet mentioned above. I would also like this NuGet to have a framework-independent dependency with my task NuGet.

Is it possible to achieve separation between project target frameworks and NuGet target frameworks?

Ideally, I would like the package that contain MSBuild tasks not to declare the lines below in the mainfest, while still generating the NuGet file with .csproj:

I have a C++ library with NetStandard2.0 wrapper; this library has specialized builds for Windows, Linux and MacOS. I can generate the .Net wrapper and shared library which is specific for each platform only on this platform (i.e. no cross compilation).

So here I put files in runtimes/linux-x64/lib/netstandard2.0 but when building with: dotnet build --runtime win-x64 src/Foo.linux-x64 file are placed in [bin/Debug/]netstandard2.0/linux-x64/* So do I need to place files in lib/linux-x64/netstandard2.0 instead ?

Meta-Package: Mizux.Foo.npkg

Then I want to create a meta-package Mizux.Foo containing the three dependencies as PackageReference (supposing I copy past all generated in a local package folder).

This works but in fact it create a degenerated project where Foo.osx-x64 and Foo.win-x64 are ignored (which is cool when testing locally but not when building the meta-package...)

side note: dotnet run --runtime linux-x64 --project src/FooApp won't work since RuntimeIdentifier is ignored, so it try to rebuild as pure .Net project and look in bin/debug/netstandard2.0...

Exemple using Mizux.Foo.nupkg

So far so good ???
So now I now I want to create a Exemple which PackageReference Mizux.Foo package...

dotnet build -r linux-x64 example/Example
Program.cs(8,7): error CS0103: The name 'Foo' does not exist in the current context [/usr/local/google/home/corentinl/work/dotnet/example/Example/Example.csproj]
Build FAILED.