Rids #93
Rids #93
Conversation
|
/cc @jeffkl as well for use of the RoslynCodeTaskFactory. Any idea what build of the CLI tools it'll be in? 2.1.400-preview-008975 does not appear to have it yet. |
|
The built-in |
| var ns = doc.Root.GetDefaultNamespace(); | ||
|
|
||
| // Escape this to avoid MSBuild issues | ||
| var tf = "$" + "(TargetFramework)"; |
There was a problem hiding this comment.
You can set Evaluate="False" on the <Task /> element above to have MSBuild not evaluate the task body.
https://docs.microsoft.com/en-us/visualstudio/msbuild/taskbody-element-msbuild
| <_SdkFileLocation>$(MSBuildProjectExtensionsPath)</_SdkFileLocation> | ||
| <_SdkPropsFileLocation>$(_SdkFileLocation)$(MSBuildProjectFile).nuget.g.props</_SdkPropsFileLocation> | ||
| <_SdkTargetsFileLocation>$(_SdkFileLocation)$(MSBuildProjectFile).nuget.g.targets</_SdkTargetsFileLocation> | ||
| <_SdkTargetsFileLocationOut>$(_SdkFileLocation)$(MSBuildProjectFile).extras.g.targets</_SdkTargetsFileLocationOut> |
There was a problem hiding this comment.
This is a great use of my MSBuildProjectExtensions feature!
There was a problem hiding this comment.
It was really a hack since I couldn't directly manipulate the generated file....access denied because msbuild already had a lock on it :P
|
Closing in favor of #94, which is less invasive |
Add support for RID's.
What currently works: Adding a TFM with an RID like this
netstandard2.0+winor a set likenetstandard2.0+unix;netstandard2.0+winIt will set a define for both
NETSTANDARD2_0andNETSTANDARD2_0_UNIX.Currently requires
msbuild.exeto build. Will require MSBuild 15.8 on .NET Core (2.1.4xx). You can build the csproj directly. Sln is a WIP./cc @Drawaes
To Do