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
Please learn from one of the failures of the older project file format and enforce a consistent and predictable ordering to the contents of the slnx files
#110
Open
StingyJack opened this issue
Mar 18, 2025
· 0 comments
One of the biggest problems with the *proj files was that new elements were added inconsistently, making diffing/comparing/merging proj files a nightmare.
TBH, it was not really a problem to me that the older project file format needed to declare every file that needed to be in the project. I actually liked that after having lived through the pains of asp.net web site projects.
Please make sure that the slnx format is not a hot mess of unordered, inconsistent XML.
The text was updated successfully, but these errors were encountered:
One of the biggest problems with the *proj files was that new elements were added inconsistently, making diffing/comparing/merging proj files a nightmare.
TBH, it was not really a problem to me that the older project file format needed to declare every file that needed to be in the project. I actually liked that after having lived through the pains of asp.net web site projects.
Please make sure that the slnx format is not a hot mess of unordered, inconsistent XML.
The text was updated successfully, but these errors were encountered: