Remove unneeded "Windows-Full" modules#7030
Conversation
| <CopyToPublishDirectory>PreserveNewest</CopyToPublishDirectory> | ||
| </Content> | ||
| <Content Include="..\Modules\Windows-Core\**\*;..\Modules\Windows-Core+Full\**\*;..\Modules\Shared\**\*"> | ||
| <Content Include="..\Modules\Windows\**\*;..\Modules\Shared\**\*"> |
There was a problem hiding this comment.
Ah, maybe we merge powershell-unix.csproj and powershell-win-core.csproj in one powershell-core.csproj to make file structure more simple?
There was a problem hiding this comment.
It's doable, but I'm not sure it will make the .csproj file simpler. There will be a bunch of conditions to separate the win-only and unix-only settings. Like RuntimeIdentifiers, content to publish (powershell.config.json, modules, install-powershellremoting.ps1 and ETW related files), and packages/projects to include.
So even after merging them into one file, it will look pretty diverged. I think it's cleaner to keep them separate, especially since we seldom change them :)
PR Summary
This PR contains following changes:
Windows-Fullfolder undersrc/ModulesWindows-Core+FullandWindows-CoretoWindowsundersrc/ModulesNote: the
Microsoft.PowerShell.ODataUtilsmodule inWindows-Fullhas its own repository: https://github.com/PowerShell/ODataUtilsPR 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