Repository navigation
Bring .cs code for CimCmdlets, WSMan.Management and WSMan.Runtime dlls - #1367
Conversation
|
Dongbo Wang (@daxian-dbw) can you take a look, please? |
|
Note from Dan Travison (@dantraMSFT):
|
There was a problem hiding this comment.
Why does it need to depend on "AssemblyLoadContext" and "Eventing"?
There was a problem hiding this comment.
Good catch! I think this is a left-over from my copy-paste
|
I cannot find the 'AssemblyInfo.cs' for wsman.management and wsman.runtime. I think we need to add them. For wsman.runtime, you can refer to: (at least the AssemblyVersionAttribute is needed) |
|
- Microsoft.WSMan.Runtime - Microsoft.WSMan.Management - Microsoft.Management.Infrastructure.CimCmdlets
- Microsoft.WSMan.Runtime - Microsoft.WSMan.Management - Microsoft.Management.Infrastructure.CimCmdlets
commit 96877403a6a2eb9dcbee0f71bbc6dfb6e61dd9a3 - Microsoft.WSMan.Runtime - Microsoft.WSMan.Management - Microsoft.Management.Infrastructure.CimCmdlets
3caa769 to
daae24f
Compare
|
|
|
sergei (@vors) I believe some sub-projects have AssemblyVersionAttribute defined in AssemblyInfo.cs. We need to clean them up then. |
|
We need AssemblyInfo.cs for Wsman.Management and WSMan.Runtime. Else, they default to 1.0.0.0. But on Windows PowerShell, they need to be 3.0.0.0 |
|
Nope, my mistake: it's actually controlled by the attribute only. |
- Microsoft.WSMan.Runtime - Microsoft.WSMan.Management - Microsoft.Management.Infrastructure.CimCmdlets
daae24f to
a655c9a
Compare
|
LGTM. |
|
Indhu Sivaramakrishnan (@Indhukrishna) It has over info we need (internal visible to). I think explicit is better then implicit in this case. |
Bring .cs code for CimCmdlets, WSMan.Management and WSMan.Runtime dlls
master.