Repository navigation
Create nuget packages for the MI.NET and WSMan related binaries #1105
Description
Activity
- addedWG-Maintainers-Buildspecific to affecting the buildspecific to affecting the build
on Jun 14, 2016 andyleejordan commented
on Jun 14, 2016 MemberMore actionsPlease work with Dan Travison (@dantraMSFT) here, as he has existing packages from MMI and MMIN.
sergei (@vors) I thought we already did this?
Yes, they are all available at appveyor-psl-windows-build. I'm closing this issue :)
PS:34> nuget list -Source appveyor-psl-windows-build -Prerelease
Using credentials from config. UserName: [email protected]
Microsoft.Management.Infrastructure 1.0.0-rc2
Microsoft.Management.Infrastructure.CimCmdlets 1.0.0-rc2
Microsoft.Management.Infrastructure.Native 1.0.0-rc5
Microsoft.mshtml 1.0.0
Microsoft.PowerShell.ScheduledJob.Interop 1.0.0-rc1
Microsoft.WSMan.Management 1.0.1-rc1
Microsoft.WSMan.Runtime 1.0.0-rc2I'd like to revisit this issue.
We should consider using reference-only packages, instead of full packages.For example,
Microsoft.mshtmlneeds to be replaced.sergei (@vors) The MMI and WSMan related packages need to have implementation dlls in them. PowerShell on windows depends on them to support WSMan provider (the WSMan module) and WMI/CIM (the CimCmdlet module). We probably need to re-create them when it's time to publish those packages to nuget though.
Partially suppressed by #1317
daxian-dbw commented
on Jul 14, 2016 MemberAuthorMore actionssergei (@vors) close this one as it really had been done. Please create another issue to track "merging MMI and MMI.Native and MMI.Native.Unmanaged" into one nuget package.
We are not going to open source the MI.NET and WsMan related code, including both managed and unmanaged. So we need to create nuget packages for them.