Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Users Search
Help Dashboard Sign In Sign Up
Q&A Code Reviews Meta
Q&A
Posts Tags Edits
Ask Question

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Post History

77%
+5 −0
Q&A Library that is platform-specific via selective compilation?

The proposed library would sit alongside cross-platform libraries in Xamarin apps for iOS and Android. However, it would include files with names like MyLibraryFile.android.cs MyLibraryFile.ios...

1 answer  ·  posted 1y ago by plod‭  ·  last activity 1y ago by Olin Lathrop‭

Question c# cross-platform
#5: Post edited by user avatar riQQ‭ · 2023-06-02T02:21:16Z (over 1 year ago)
Fix code blocks 
Library that is platform-specific via selective compilation?
  • The proposed library would sit alongside cross-platform libraries in Xamarin apps for iOS and Android. However, it would include files with names like
  • `MyLibraryFile.android.cs
  • MyLibraryFile.ios.cs`
  • Each file would have platform-specific content, and all files would be visible in the solutions for each platform, i.e. in the solution for the Android app, under MyLibrary, you would also be able to see MyLibraryFile.ios.cs.
  • The contents of the library would be steered via the project file, which would have a structure as follows.
  • First, a list of target frameworks is set
  • `<PropertyGroup>
  • <TargetFrameworks>Xamarin.iOS10</TargetFrameworks>
  • <TargetFrameworks Condition="'$(OS)' != 'Unix'">$(TargetFrameworks);MonoAndroid12.0</TargetFrameworks>
  • </PropertyGroup>`
  • Then, the project file selects which .cs files to build based on the TargetFramework set in the app project.
  • `<ItemGroup Condition="$(TargetFramework.StartsWith('MonoAndroid'))">
  • <Compile Include="**\*.android.cs"/>
  • </ItemGroup>`
  • My question is, is this a recognised pattern?
  • I can't find anything about it.
  • The proposed library would sit alongside cross-platform libraries in Xamarin apps for iOS and Android. However, it would include files with names like
  • ```
  • MyLibraryFile.android.cs
  • MyLibraryFile.ios.cs
  • ```
  • Each file would have platform-specific content, and all files would be visible in the solutions for each platform, i.e. in the solution for the Android app, under MyLibrary, you would also be able to see MyLibraryFile.ios.cs.
  • The contents of the library would be steered via the project file, which would have a structure as follows.
  • First, a list of target frameworks is set
  • ```
  • <PropertyGroup>
  • <TargetFrameworks>Xamarin.iOS10</TargetFrameworks>
  • <TargetFrameworks Condition="'$(OS)' != 'Unix'">$(TargetFrameworks);MonoAndroid12.0</TargetFrameworks>
  • </PropertyGroup>
  • ```
  • Then, the project file selects which .cs files to build based on the TargetFramework set in the app project.
  • ```
  • <ItemGroup Condition="$(TargetFramework.StartsWith('MonoAndroid'))">
  • <Compile Include="**\*.android.cs"/>
  • </ItemGroup>
  • ```
  • My question is, is this a recognised pattern?
  • I can't find anything about it.
#4: Nominated for promotion by user avatar Alexei‭ · 2023-05-13T19:35:19Z (over 1 year ago)
#3: Post edited by user avatar plod‭ · 2023-05-12T09:30:44Z (over 1 year ago)
  • The proposed library would sit alongside cross-platform libraries in Xamarin apps for iOS and Android. However, it would include files with names like
  • `MyLibraryFile.android.cs
  • MyLibraryFile.ios.cs`
  • Each file would have platform-specific content, and all files would be visible in the solutions for each platform, i.e. in the solution for the Android app, under MyLibrary, you would also be able to see MyLibraryFile.ios.cs.
  • The contents of the library would be steered via the project file, which would have a structure as follows.
  • First, a list of target frameworks is set
  • `<PropertyGroup>
  • <TargetFrameworks>Xamarin.iOS10</TargetFrameworks>
  • <TargetFrameworks Condition="'$(OS)' != 'Unix'">$(TargetFrameworks);MonoAndroid12.0</TargetFrameworks>
  • </PropertyGroup>`
  • Then, the project file selects which .cs files to build based on the TargetFramework set in the app project.
  • <ItemGroup Condition="$(TargetFramework.StartsWith('MonoAndroid'))">
  • <Compile Include="**\*.android.cs"/>
  • </ItemGroup>
  • My question is, is this a recognised pattern?
  • I can't find anything about it.
  • The proposed library would sit alongside cross-platform libraries in Xamarin apps for iOS and Android. However, it would include files with names like
  • `MyLibraryFile.android.cs
  • MyLibraryFile.ios.cs`
  • Each file would have platform-specific content, and all files would be visible in the solutions for each platform, i.e. in the solution for the Android app, under MyLibrary, you would also be able to see MyLibraryFile.ios.cs.
  • The contents of the library would be steered via the project file, which would have a structure as follows.
  • First, a list of target frameworks is set
  • `<PropertyGroup>
  • <TargetFrameworks>Xamarin.iOS10</TargetFrameworks>
  • <TargetFrameworks Condition="'$(OS)' != 'Unix'">$(TargetFrameworks);MonoAndroid12.0</TargetFrameworks>
  • </PropertyGroup>`
  • Then, the project file selects which .cs files to build based on the TargetFramework set in the app project.
  • `<ItemGroup Condition="$(TargetFramework.StartsWith('MonoAndroid'))">
  • <Compile Include="**\*.android.cs"/>
  • </ItemGroup>`
  • My question is, is this a recognised pattern?
  • I can't find anything about it.
#2: Post edited by user avatar plod‭ · 2023-05-12T09:29:15Z (over 1 year ago)
  • The proposed library would sit alongside cross-platform libraries in Xamarin apps for iOS and Android. However, it would include files with names like
  • MyLibraryFile.android.cs
  • MyLibraryFile.ios.cs
  • Each file would have platform-specific content, and all files would be visible in the solutions for each platform, i.e. in the solution for the Android app, under MyLibrary, you would also be able to see MyLibraryFile.ios.cs.
  • The contents of the library would be steered via the project file, which would have a structure as follows.
  • First, a list of target frameworks is set
  • <PropertyGroup>
  • <TargetFrameworks>Xamarin.iOS10</TargetFrameworks>
  • <TargetFrameworks Condition="'$(OS)' != 'Unix'">$(TargetFrameworks);MonoAndroid12.0</TargetFrameworks>
  • </PropertyGroup>
  • Then, the project file selects which .cs files to build based on the TargetFramework set in the app project.
  • <ItemGroup Condition="$(TargetFramework.StartsWith('MonoAndroid'))">
  • <Compile Include="**\*.android.cs"/>
  • </ItemGroup>
  • My question is, is this a recognised pattern?
  • I can't find anything about it.
  • The proposed library would sit alongside cross-platform libraries in Xamarin apps for iOS and Android. However, it would include files with names like
  • `MyLibraryFile.android.cs
  • MyLibraryFile.ios.cs`
  • Each file would have platform-specific content, and all files would be visible in the solutions for each platform, i.e. in the solution for the Android app, under MyLibrary, you would also be able to see MyLibraryFile.ios.cs.
  • The contents of the library would be steered via the project file, which would have a structure as follows.
  • First, a list of target frameworks is set
  • `<PropertyGroup>
  • <TargetFrameworks>Xamarin.iOS10</TargetFrameworks>
  • <TargetFrameworks Condition="'$(OS)' != 'Unix'">$(TargetFrameworks);MonoAndroid12.0</TargetFrameworks>
  • </PropertyGroup>`
  • Then, the project file selects which .cs files to build based on the TargetFramework set in the app project.
  • <ItemGroup Condition="$(TargetFramework.StartsWith('MonoAndroid'))">
  • <Compile Include="**\*.android.cs"/>
  • </ItemGroup>
  • My question is, is this a recognised pattern?
  • I can't find anything about it.
#1: Initial revision by user avatar plod‭ · 2023-05-12T09:27:56Z (over 1 year ago) 
Library that is platform-specific via selective compilation?
The proposed library would sit alongside cross-platform libraries in  Xamarin apps for iOS and Android.  However, it would include files with names like

MyLibraryFile.android.cs
MyLibraryFile.ios.cs


Each file would have platform-specific content, and all files would be visible in the solutions for each platform, i.e. in the solution for the Android app, under MyLibrary, you would also be able to see MyLibraryFile.ios.cs.

The contents of the library would be steered via the project file, which would have a structure as follows.

First, a list of target frameworks is set

<PropertyGroup>
<TargetFrameworks>Xamarin.iOS10</TargetFrameworks>
<TargetFrameworks Condition="'$(OS)' != 'Unix'">$(TargetFrameworks);MonoAndroid12.0</TargetFrameworks>
</PropertyGroup>

Then, the project file selects which .cs files to build based on the TargetFramework set in the app project.

<ItemGroup Condition="$(TargetFramework.StartsWith('MonoAndroid'))">
   <Compile Include="**\*.android.cs"/>
</ItemGroup>

My question is, is this a recognised pattern?  
I can't find anything about it.
c# cross-platform