generated from jingkecn/MyScript.InteractiveInk.Starter.UWP
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Directory.Build.props
50 lines (50 loc) · 2.84 KB
/
Directory.Build.props
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
<!--
~ INTRO:
~ Directory.Build.props is imported very early in Microsoft.Common.props, and properties defined later are
~ unavailable to it. So, avoid referring to properties that are not yet defined (and will evaluate to empty).
~ General GUIDELINES:
~ - For many properties, it doesn't matter where they're defined, because they're not overwritten and will be read
~ only at execution time.
~ - For behavior that might be customized in an individual project, set defaults in .props files.
~ - Avoid setting dependent properties in .props files by reading the value of a possibly customized property,
~ because the customization won't happen until MSBuild reads the user's project.
~ - Set dependent properties in .targets files, because they'll pick up customizations from individual projects.
~ - If you need to override properties, do it in a .targets file, after all user-project customizations have had a
~ chance to take effect. Be cautious when using derived properties; derived properties may need to be overridden
~ as well.
~ - Include items in .props files (conditioned on a property). All properties are considered before any item, so
~ user-project property customizations get picked up, and this gives the user's project the opportunity to Remove
~ or Update any item brought in by the import.
~ - Define targets in .targets files. However, if the .targets file is imported by an SDK, remember that this
~ scenario makes overriding the target more difficult because the user's project doesn't have a place to override
~ it by default.
~ - If possible, prefer customizing properties at evaluation time over changing properties inside a target. This
~ guideline makes it easier to load a project and understand what it's doing.
-->
<!-- See: https://docs.microsoft.com/en-us/visualstudio/msbuild/customize-your-build?view=vs-2017#import-order -->
<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<!-- MyScript -->
<PropertyGroup>
<Company>MyScript</Company>
<Product>InteractiveInk</Product>
</PropertyGroup>
<!-- Common -->
<PropertyGroup>
<LangVersion>latest</LangVersion>
<RepositoryType>Git</RepositoryType>
</PropertyGroup>
<!-- Variables -->
<PropertyGroup>
<Authors>$(Company)</Authors>
<Copyright>Copyright © $(Company) $([System.DateTime]::Now.Year). All rights reserved.</Copyright>
<RootDir>$(MSBuildThisFileDirectory.TrimEnd('\\/'))</RootDir>
<Trademark>$(Product)™</Trademark>
</PropertyGroup>
<!-- Include RID to path if necessary.
~ See: https://docs.microsoft.com/en-us/dotnet/core/rid-catalog
-->
<PropertyGroup>
<AppendRuntimeIdentifierToOutputPath>false</AppendRuntimeIdentifierToOutputPath>
<AppendTargetFrameworkToOutputPath>false</AppendTargetFrameworkToOutputPath>
</PropertyGroup>
</Project>