Repository navigation
VS 2017 sln - #4748
VS 2017 sln#4748
Conversation
|
Maybe put the file in root folder with PowerShell.Common.props file? Currently I use Staffan Gustafsson (@powercode) sln file such way. |
|
I'll defer to Dongbo Wang (@daxian-dbw) on taking the sln from Staffan Gustafsson (@powercode) or this one. I can move it to the root if we decide to take this. |
There was a problem hiding this comment.
Is <RootNamespace> necessary to be added?
If so, can you please move it to the PropertyGroup section at top of the file?
There was a problem hiding this comment.
It avoids a warning when opening the solution. I moved it to the top.
|
I will take this |
|
Jason Shirk (@lzybkr) Could you please address the comments when you have time? Thanks! |
|
Comments addressed and I rebased on master to fix the conflict. |
Dongbo Wang (daxian-dbw)
left a comment
There was a problem hiding this comment.
LGTM. Thanks!
I created a VS2017 solution file for the powershell-win-core csproj and everything it references.
It "upgraded" each csproj - but I reverted all changes but the one to suppress future upgrades.
The solution doesn't build and I haven't investigated why, but it's useful for editing across the entire project.