Description
Move to GitHub
This issue tracks problems we faced, when we tried to move development.
It's divide into buckets.
Source parity
There are two parts: we cannot build some code as-is (i.e. we need #if !CORECLR guards), we don't build some things yet (completely or replaced with stubs)
- Replace Microsoft.Management.Infrastructure.Native by the real package on Full CLR build #760 Replace Microsoft.Management.Infrastructure.Native by the real package on Full CLR build
-
Use C# bindings in EventLog code #745 Use C# bindings in EventLog code(out of scope) -
ConvertFrom-String is missing #726 Replace FlashExtract sources by Nuget packages(out of scope) - FullCLR version should build x64 powershell.exe #683 FullCLR version should build x64 powershell.exe
-
Add excluded source files to Full CLR build #670 Add controlpanelitemcommand.cs to Full CLR build(out of scope) -
Submit#if !CORECLRguards and<windows.h>(from powershell.exe) to our current branch in source depot - We don't build all existing in the product artifacts. Identify difference of library sets between Nano and PowerShell Core from repo #1031
Process problems
- ResGen is missing from
dotnet cli(we workaround it withStart-ResGen+ submodule, but it complicates the process). - It's pretty hard to maintain two long-living branches at the current state of the repo: massive re-namings need to be carry-around as cherry-picks. It would be viable, when structure would settle better.
Regressions in the GitHub binaries
- BVT/DRT Regressions #543 BVT/DRT Regressions
- New-Object -Com doesn't work for custom Com objects #547 New-Object -Com doesn't work for custom Com objects
- BVT/DRT run for binaries from the proposed branch
server2016-oldis not clean. - We use artificially crafted NuGet packages as dependencies from local
nuget-feed. It allows us to build binaries, but they are failed to load from GAC in runtime.