-
-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add RestoreProjectStyle --> PackageReference to Android and iOS projects? #181
Comments
Switching to hybrid mode is a good idea. (PackageReference in classic project) Also I'm currently playing with EDIT: It works well in JetBrains Rider, but cannot be deployed/debugged by VS/VSfM... For example: (removed <Project Sdk="MSBuild.Sdk.Extras/1.6.55">
<PropertyGroup>
<TargetFramework>Xamarin.iOS10</TargetFramework>
</PropertyGroup>
<Import Project="$(MSBuildExtensionsPath)\Xamarin\iOS\Xamarin.iOS.FSharp.targets" Condition="Exists('$(MSBuildExtensionsPath)\Xamarin\iOS\Xamarin.iOS.FSharp.targets')" />
<ItemGroup>
<Reference Include="System.Numerics" />
<Reference Include="Xamarin.iOS" />
<Reference Include="System" />
<Reference Include="System.Xml" />
<Reference Include="System.Core" />
<Reference Include="mscorlib" />
</ItemGroup>
<ItemGroup>
<PackageReference Include="Fabulous.Core" Version="0.20.0" />
</ItemGroup>
<ItemGroup>
<ImageAsset Include="Assets.xcassets\AppIcon.appiconset\Contents.json" />
<ImageAsset Include="Assets.xcassets\Contents.json" />
<InterfaceDefinition Include="LaunchScreen.storyboard" />
<None Include="Info.plist" />
<None Include="Entitlements.plist" />
<InterfaceDefinition Include="Main.storyboard" />
<Compile Include="ViewController.fs" />
<Compile Include="AppDelegate.fs" />
<Compile Include="Main.fs" />
</ItemGroup>
</Project> |
Migrating to PackageReference would also allow to remove the .nuget folder from the template. It happened to me several times to have a build failed because I moved files around and forgot to copy the hidden .nuget folder... (explicitly referenced in fsproj) |
That would be great |
Seems like we're stuck with those issues until Xamarin finally moves to the SDK style: dotnet/fsharp#4152 |
Based on my discussion with @nosami on Gitter, this limitation seems to apply to VS tooling only. But if it works, should we also migrate the templates? |
I migrated successfully a newly created solution from the Fabulous template. Opened an issue on dotnet/fsharp#5849 |
Closing the issue for now. |
I've noticed occasions where dependencies added or updated in the core F# project (SDK-style) don't seem to be copied correctly to the Android and iOS apps (old-style)
I'm not 100% sure why but it looks related to this issue: dotnet/standard#481
The recomendation there is to add
I'm not 100% sure but we should probably add this to our Android/iOS app projects
The text was updated successfully, but these errors were encountered: