You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -47,11 +51,48 @@ If you only support a subset of these values, map the missing ones to the closes
47
51
48
52
### Framework selection
49
53
54
+
Short form: `-f <TFM>`
55
+
56
+
Long form: `--framework <TFM>`
57
+
50
58
### RID selection
59
+
60
+
#### Explicit RID
61
+
62
+
Short form: `-r <RID>`
63
+
64
+
Long form: `--runtime <RID>`
65
+
66
+
#### OS-specific RID
67
+
68
+
Short form: `-o <OS>`
69
+
70
+
Long form: `--os <OS>`
71
+
72
+
#### Architecture-specific RID
73
+
74
+
Short form: `-a <ARCH>`
75
+
76
+
Long form: `--arch <ARCH>`
77
+
78
+
#### SDK-matching RID
79
+
80
+
Short form: `--ucr`
81
+
82
+
Long form: `--use-current-runtime`
83
+
51
84
### MSBuild Properties
85
+
86
+
Short form: `-p <MSBuild property expression(s)>`
87
+
88
+
Long form: `--property <MSBuild property expression(s)>`
89
+
90
+
If at all possible we _strongly encourage_ not parsing the `<MSBuild property expression(s)>` syntax yourself. It is much more complex than you think it is. At _best_ you should detect and forward along any of these arguments to any MSBuild invocations you make.
91
+
52
92
### Output modes/formatting
53
93
54
94
Long form: `--output`
95
+
55
96
Allowed values: `text`, `json`, others are relevant for your use case
56
97
57
98
Users value scriptability of CLI commands, and some form of structured output is key to supporting this. JSON is a common structured output format, but other formats may be more appropriate for your use case. If you use a structured format like `csv`, please for the love of Turing use a proper CSV writer and not just a hand-rolled comma-separated list of values so that you don't break [RFC 4180][4180].
0 commit comments