WIP Use early preview of .Net Core 3.0#8370
WIP Use early preview of .Net Core 3.0#8370SteveL-MSFT merged 74 commits intoPowerShell:netcore30from
Conversation
… image creation process
…t (build number does not match sdk)
… to problems, they have stopped supporting it, therefore use dotnet test as an alternative xunit/xunit#1675 https://xunit.github.io/releases/2.4
…o netcore2.2 # Conflicts: # build.psm1 # test/hosting/hosting.tests.csproj
…o netcore2.2 Conflicts auto-resolved by Tortoise-Git (white space problem only) # Conflicts: # assets/files.wxs
…ccore and sos due to the upgrade from preview2 to preview3
… not working with using netcore3.0
|
crossgen is returning exit code 139 on Linux and macOS which causes CI to fail. Created https://github.com/dotnet/coreclr/issues/22276 |
…o netcore3.0 # Conflicts: # assets/files.wxs # build.psm1
…o netcore3.0 Mainly resolved by keeping the version of the branch due to the runtime update # Conflicts: # PowerShell.Common.props # assets/files.wxs # global.json # test/Test.Common.props # test/tools/WebListener/WebListener.csproj
5d91318 to
3528292
Compare
|
Reverted attempt to move to newer 3.0 release since it caused more problems |
|
We should try the new preview3 that got published yesterday |
|
Since 6.2-GA was forked we can actively work on the PR. |
|
I tried to update to To me this looks like the Asp.Net Core Team needs to publish a newer |
|
I wonder how we depend on Microsoft.AspNetCore.App? |
…o netcore3.0 # Conflicts: # assets/files.wxs
|
@bergmeister I try to compile your .net v3 branch and found the same symptom. If I remove 'RuntimeFrameworkVersion' on PowerShell.Common.props and Test.Common.props , it lets me compile. I also rollback your change to Microsoft.WindowsDesktop.App dotnet.exe -info There is a version's conflict between all Microsoft.*.App runtimes and PowerShell.Common.props |
|
@fMichaleczek At the moment we are waiting for preview4 to fix problems like that. If you want to try out a working version of netcore3 you could try using a daily build or checkout one of the older commits on this branch that used preview1 or preview2 |
|
Looks like Preview.4 just became available, I'll move the build to that version |
|
Moving this to a working branch on PS/PS |
PR Summary
There are only 1 failing test on Windows due to Compatibility section in application manifest not being embedded in pwsh.exe (https://github.com/dotnet/core-setup/issues/4963).
.Net Core 3.0 adds one reference assembly and also a
.nupkg.metadatafile for each shipped module containing the hash, which I ignore for the installer.Removed dependency on rcedit to embed manifest and update assembly file properties as .Net Core 3.0 SDK supports same capabilities from csproj file. Due to this change, the fileversion and productversion embedded as rouces in pwsh.exe has changed to their desired format defined in the csproj. Tests were updated to account for this difference.
.Net Core 3.0 supports writing to reserved device names (like CON which writes to the console as expected; didn't test COM or LPT but presumably they would write to the COM and printer ports), so updated code to only check for
CLOCK$as a reserved device name.Breaking Change By default, long paths are returned by the FileSystemProvider whereas before, it would retain the short path. This change is due to a change in .Net Core 3.0 behavior related to long paths which invalidated existing tests that used
$TestDrivewhich is built from$env:TEMPwhich has a short path (if the username is > 8 characters which is the case on AzPipelines for Windows).PR Checklist
.h,.cpp,.cs,.ps1and.psm1files have the correct copyright headerWIP:to the beginning of the title and remove the prefix when the PR is ready.[feature]if the change is significant or affects feature tests