Uh oh!
There was an error while loading. Please reload this page.
Removing "netcoreapp" and "netfx" TargetGroup - #457
Conversation
ViktorHofer
commented
Dec 2, 2019
This collides with the work being done in #445. Can you either pause this until the other PR is in or use the same TFM name so that we can simply replace the property define here after the other one is in? |
Anipik
commented
Dec 2, 2019
Sure I can wait until the #445 is in |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
ViktorHofer
commented
Dec 4, 2019
We agreed on |
ViktorHofer
commented
Dec 5, 2019
@Anipik this work is now unblocked. |
| inputs: | ||
| sourceFolder: $(Build.SourcesDirectory)/artifacts/bin/pkg/${{ parameters.framework }}/runtime | ||
| targetFolder: $(Build.ArtifactStagingDirectory)/artifacts/bin/pkg/${{ parameters.framework }}/runtime | ||
| sourceFolder: $(Build.SourcesDirectory)/artifacts/bin/pkg/netcoreapp5.0/runtime # The hardcoded target framework should be removed when we drop the support for versionless targetframeworks from ci. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
jkoritzinsky
commented
Dec 12, 2019
safern
commented
Dec 12, 2019
Anipik
commented
Dec 12, 2019
sure i can wait. let me know when i can go ahead and merge this one. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
ViktorHofer
commented
Dec 12, 2019
Actually I just saw in how many places we hardcode net472 and I'm not really happy about that. As we are already touching so many files as part of this PR I would introduce a property for it |
Anipik
commented
Dec 13, 2019
@ViktorHofer as we are not gonna increase the netframework version, what will be the advantages of having this new property ? |
Anipik
commented
Dec 13, 2019
@jkoritzinsky@safern@ViktorHofer |
jkoritzinsky
commented
Dec 13, 2019
Yes. You'll need to add a job to build coreclr for that pipeline now that live-live is enabled. |
Anipik
commented
Dec 14, 2019
@safern@ViktorHofer@ericstj can we go ahead and merge this one ? |
davidsh
commented
Dec 14, 2019
This has been fixed already with PR #843 which was merged in the last hour. |
Anipik
commented
Dec 14, 2019
Thanks @davidsh |
Anipik
commented
Dec 14, 2019
This one is ready to go in. the merging is blocked and require an approval |
Most of the work is done using regex. The commit messages contain the regex used for that commit.
I also introduced a new variable to track the latest version of netcoreapp, making it easier to increment for later version
.sln files will need to be updated with every new major product version.
Regexs used
netcoreapp -> netcoreapp5.0 in .sln
netcoreapp; -> netcoreapp5.0; in .props
netcoreapp- -> netcoreapp5.0- in .props
netcoreapp- -> netcoreapp5.0- in .csproj
'netcoreapp -> 'netcoreapp5.0 in .csproj
netcoreapp5.0 occurences are then replaced using the above regex by TargetFrameworkVNext
Same stuff has been done for netfx