You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm finding that the solutions generated by slngen are not stable, at least when multiple projects are supplied on the command line. I discovered this while writing an MSBuild target to diff two solutions.
Here's the command line I'm using, by way of the SlnGen MSBuild target (as updated by #609) I've placed one parameter per line to make it more legible.:
My expectation is that the first project on the command line will be the first one in the solution, and therefore the default startup project. That's what I get most of the time, but that doesn't seem to be consistent.
I've attached two generated solutions (with a .txt extension added, since .sln files can't be attached):
Microsoft.VisualStudio.Shell.sln.txt: the expected output, with Microsoft.VisualStudio.Shell.csproj as the first project
Microsoft.VisualStudio.Shell.unexpected.sln.txt: this one has FileChangeManagerTests.csproj as the first project, and differing solution folders as a result
@mruxmohan4, #609 doesn't resolve this issue, I just happened to discover it while working on #609. Did you mean to refer to another PR which resolved this issue?
I'm finding that the solutions generated by
slngen
are not stable, at least when multiple projects are supplied on the command line. I discovered this while writing an MSBuild target to diff two solutions.Here's the command line I'm using, by way of the
SlnGen
MSBuild target (as updated by #609) I've placed one parameter per line to make it more legible.:My expectation is that the first project on the command line will be the first one in the solution, and therefore the default startup project. That's what I get most of the time, but that doesn't seem to be consistent.
I've attached two generated solutions (with a
.txt
extension added, since.sln
files can't be attached):Microsoft.VisualStudio.Shell.sln.txt
: the expected output, withMicrosoft.VisualStudio.Shell.csproj
as the first projectMicrosoft.VisualStudio.Shell.unexpected.sln.txt
: this one hasFileChangeManagerTests.csproj
as the first project, and differing solution folders as a resultMicrosoft.VisualStudio.Shell.sln.txt
Microsoft.VisualStudio.Shell.unexpected.sln.txt
The text was updated successfully, but these errors were encountered: