Cannot pair to mac server when building TFM Xamarin.iOS in Visual Studio 2017 about msbuildsdkextras HOT 7 CLOSED

You can ignore that warning. Libraries don't build on a Mac, only applications do. @kzu, can that warning be removed for libraries?

from msbuildsdkextras.

Understood.
Actually, we have the same warning on a "xamarin.ios class library" when VS is not connected to the mac server.
So this is definitely not specific to multi-targeting, and it's not a big deal since the connection is actually not required for a library.
Thanks !

from msbuildsdkextras.

Does passing /nowarn: from MSBuild work? If not, @mauroa we need to look into that and allow to build class libraries without warnings (maybe we should modify the templates? /cc @joj)

from msbuildsdkextras.

When using msbuild (cmd line instead of visual studio), there are actually 2 warnings:

• (SayHello) : warning VSX1000: No Address and User has been specified in order to establish a connection to a Mac Server
• (SayGoodbye) : warning : There is no current Build Connection to get. A new connection needs to be created first

When passing /nowarn:VSX1000, the first warning is suppressed. However the second one is still here.

In visual studio, adding "VSX1000" to csproj does not seem to have an effect.

from msbuildsdkextras.

There is a somewhat unpleasant workaround described here

I was wondering if the real issue is tracked somewhere?

from msbuildsdkextras.

If you report it at https://developercommunity.visualstudio.com (or via the "Send Feedback" inside VS), we can track it internally and fix it sooner than later in the Xamarin.iOS side. I already filed a work item internally anyway, but a public feedback item will allow you to track it better.

from msbuildsdkextras.

Closing as external

from msbuildsdkextras.