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
/Users/blake/Source/Synchro/MaaasClient/MaaasClientWin/MaaasClientWin.csproj: warning : Could not find project file /Library/Frameworks/Mono.framework/External/xbuild/Microsoft/WindowsXaml/v12.0/Microsoft.Windows.UI.Xaml.CSharp.targets, to import. Ignoring.
/Users/blake/Source/Synchro/MaaasClient/MaaasClientWin.Shared/MaaasClientWin.Shared.shproj: warning : Could not find project file /Library/Frameworks/Mono.framework/External/xbuild/Microsoft/VisualStudio/v/CodeSharing/Microsoft.CodeSharing.Common.Default.props, to import. Ignoring.
/Users/blake/Source/Synchro/MaaasClient/MaaasClientWin.Shared/MaaasClientWin.Shared.shproj: warning : Could not find project file /Library/Frameworks/Mono.framework/External/xbuild/Microsoft/VisualStudio/v/CodeSharing/Microsoft.CodeSharing.Common.props, to import. Ignoring.
/Users/blake/Source/Synchro/MaaasClient/MaaasClientWin.Shared/MaaasClientWin.Shared.shproj: warning : Could not find project file /Library/Frameworks/Mono.framework/External/xbuild/Microsoft/VisualStudio/v/CodeSharing/Microsoft.CodeSharing.CSharp.targets, to import. Ignoring.
/Users/blake/Source/Synchro/MaaasClient/MaaasClientWin.WindowsPhone/MaaasClientWin.WindowsPhone.csproj: warning : Could not find project file /Library/Frameworks/Mono.framework/External/xbuild/Microsoft/WindowsXaml/v12.0/Microsoft.Windows.UI.Xaml.CSharp.targets, to import. Ignoring.
/Users/blake/Source/Synchro/MaaasClient/MaaasClient.sln: warning : Don't know how to handle GlobalSection SharedMSBuildProjectFiles, Ignoring.
Not sure what any of these guys are yet.
The text was updated successfully, but these errors were encountered:
There are still a few warnings when building the MaaasIOSClient:
I think this is a Xamarin bug, being discussed in their forums.
Not sure what any of these guys are yet.
The text was updated successfully, but these errors were encountered: