Relative file paths and Target Framework Monikers (TFM)

Open
#162 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
build-system, tooling

Research direction

The payload names no source files, tests, or entry points. Start by locating the TFM-specific Xcode project generation and static-file synchronization logic; done means validating the relative-path behavior for Platforms/iOS, Platforms/MacCatalyst, and single-TFM projects without disrupting other project types.

Written by the indexing model from the issue text.

Description

When copying static file content in either direction, the files relative path is kept intact. That is if the file bar.storyboard is in a subfolder foo under the .NET project folder. Then the file is copied into a subfolder name foo in the Xcode project.

This is fine until you consider the .NET MAUI project. .NET MAUI segregates platform specific files in the Platforms folder, so iOS-specific files are in the Platforms/iOS and Mac Catalyst files are in the Platforms/MacCatalyst folder. It is expected that .storyboard, .xib, files and .xcassets folders would reside under the appropriate platform folder. In that case those files/folders are copied to the Xcode project correctly, in a subfolder Platforms/iOS or Platforms/MacCatalyst

However, since by default, the Xcode project is generated in a TFM specific folder, and each Xcode project generated for a specific TFM when generating or syncing the project with a specified TFM, or if there is only one supported TFM, then the relative path for Platforms/iOS and Platforms/MacCatalyst can be removed. This makes the .NET MAUI project projection to Xcode appear similar to a non-MAUI project resulting in a unified user experience across different project types.

Dominant language
C#
Stars
25
Forks
10
Avg merge
12h 50m
Merged PRs (30d)
10

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/xcsync

All issues in dotnet/xcsync

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.