xamarin
/
xamarin-macios
зеркало из
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
xamarin-macios/dotnet/SingleProject.md

35 строки
1.7 KiB
Markdown
Исходник Постоянная ссылка Обычный вид История

[dotnet] Add support for some of the single-project MSBuild properties. (#10545) * [tests] Add test case for single-project properties in .NET. * [msbuild] Add support for the single-project ApplicationId MSBuild property. * [msbuild] Add support for the single-project ApplicationTitle, ApplicationVersion and AppleShortVersion MSBuild properties. * [dotnet] Enable the single-project MSBuild properties by default. * [dotnet] Add a short doc about single project properties. * [tests] Fix the GeneratePlistTaskTests.BundleIdentifier test according to bundle identifier changes. This test asserts that the CFBundleIdentifier value in the Info.plist isn't overwritten, and does so by calling the CompileAppManifest task, giving it a different value for the bundle identifier than what's in the Info.plist. The behavior change is that now we do things in the following manner: DetectSigningIdentityTask will read the Info.plist, compute a bundle identifier (which will be the value from the Info.plist if it's there), and returns it to the MSBuild code. Eventually that value will be passed to the CompileAppManifestTask, which will write it to the Info.plist. However, this test doesn't run the DetectSigningIdentityTask, which means that the initial value for the bundle identifier doesn't come from the Info.plist.
2021-01-29 19:37:37 +03:00
# .NET "Single Project"
In order to improve the cross-platform experience between Android and our
Apple platforms, there are certain properties that can be set in the project
file that will be added to the app in a platform-specific way.
More a more detailed description see this document: [OneDotNetSingleProject.md][1]
For our Apple platforms this means we're mapping the following MSBuild
properties to Info.plist keys (this mapping will only take place if the
Info.plist in the project doesn't already contain entries for these keys):
[dotnet] rename $(AppleShortVersion) to $(ApplicationDisplayVersion) (#12647) Context: https://github.com/dotnet/maui/issues/1662 Context: https://github.com/xamarin/xamarin-android/pull/6139 Previously: * `$(ApplicationVersion)` mapped to `CFBundleVersion` * `$(AppleShortVersion)` mapped to `CFBundleShortVersionString` To be able to leverage identical property names on iOS/Android, we're changing this to: * `$(ApplicationVersion)` maps to `CFBundleVersion` * `$(ApplicationDisplayVersion)` maps to `CFBundleShortVersionString` Lastly, let's allow `$(ApplicationDisplayVersion)` to set `$(Version)`, so the various C# assembly-level attributes are all set to the same value.
2021-09-08 17:13:29 +03:00
| MSBuild Property | Info.plist key | Notes |
| --------------------------|----------------------------|-------------------------------------------|
| ApplicationId | CFBundleIdentifier | |
| ApplicationTitle | CFBundleDisplayName | |
| ApplicationVersion | CFBundleVersion | |
| ApplicationDisplayVersion | CFBundleShortVersionString | Defaults to ApplicationVersion when blank |
[dotnet] Add support for some of the single-project MSBuild properties. (#10545) * [tests] Add test case for single-project properties in .NET. * [msbuild] Add support for the single-project ApplicationId MSBuild property. * [msbuild] Add support for the single-project ApplicationTitle, ApplicationVersion and AppleShortVersion MSBuild properties. * [dotnet] Enable the single-project MSBuild properties by default. * [dotnet] Add a short doc about single project properties. * [tests] Fix the GeneratePlistTaskTests.BundleIdentifier test according to bundle identifier changes. This test asserts that the CFBundleIdentifier value in the Info.plist isn't overwritten, and does so by calling the CompileAppManifest task, giving it a different value for the bundle identifier than what's in the Info.plist. The behavior change is that now we do things in the following manner: DetectSigningIdentityTask will read the Info.plist, compute a bundle identifier (which will be the value from the Info.plist if it's there), and returns it to the MSBuild code. Eventually that value will be passed to the CompileAppManifestTask, which will write it to the Info.plist. However, this test doesn't run the DetectSigningIdentityTask, which means that the initial value for the bundle identifier doesn't come from the Info.plist.
2021-01-29 19:37:37 +03:00
This is only enabled if the `GenerateApplicationManifest` is set to `true`
(which is the default for `.NET 6`, and not for "legacy"
Xamarin.iOS/Xamarin.Mac)
[dotnet] rename $(AppleShortVersion) to $(ApplicationDisplayVersion) (#12647) Context: https://github.com/dotnet/maui/issues/1662 Context: https://github.com/xamarin/xamarin-android/pull/6139 Previously: * `$(ApplicationVersion)` mapped to `CFBundleVersion` * `$(AppleShortVersion)` mapped to `CFBundleShortVersionString` To be able to leverage identical property names on iOS/Android, we're changing this to: * `$(ApplicationVersion)` maps to `CFBundleVersion` * `$(ApplicationDisplayVersion)` maps to `CFBundleShortVersionString` Lastly, let's allow `$(ApplicationDisplayVersion)` to set `$(Version)`, so the various C# assembly-level attributes are all set to the same value.
2021-09-08 17:13:29 +03:00
Additionally, `$(ApplicationDisplayVersion)` will overwrite the value for `$(Version)`,
so the following properties will be set with the same value:
* `$(AssemblyVersion)`
* `$(FileVersion)`
* `$(InformationalVersion)`
[dotnet] Add support for some of the single-project MSBuild properties. (#10545) * [tests] Add test case for single-project properties in .NET. * [msbuild] Add support for the single-project ApplicationId MSBuild property. * [msbuild] Add support for the single-project ApplicationTitle, ApplicationVersion and AppleShortVersion MSBuild properties. * [dotnet] Enable the single-project MSBuild properties by default. * [dotnet] Add a short doc about single project properties. * [tests] Fix the GeneratePlistTaskTests.BundleIdentifier test according to bundle identifier changes. This test asserts that the CFBundleIdentifier value in the Info.plist isn't overwritten, and does so by calling the CompileAppManifest task, giving it a different value for the bundle identifier than what's in the Info.plist. The behavior change is that now we do things in the following manner: DetectSigningIdentityTask will read the Info.plist, compute a bundle identifier (which will be the value from the Info.plist if it's there), and returns it to the MSBuild code. Eventually that value will be passed to the CompileAppManifestTask, which will write it to the Info.plist. However, this test doesn't run the DetectSigningIdentityTask, which means that the initial value for the bundle identifier doesn't come from the Info.plist.
2021-01-29 19:37:37 +03:00
Ref: [Issue #10473][2]
[1]: https://github.com/xamarin/xamarin-android/blob/40cedfa89c2660479fcb5e2482d2463fbcad1d04/Documentation/guides/OneDotNetSingleProject.md
[2]: https://github.com/xamarin/xamarin-macios/issues/10473