Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
I added a new project to the 'tools' solution in MD which caused a 6000 line diff to be created as MD rewrote every csproj in the hierarchy. This is unwanted behaviour for most users and I don't know why MD did this.
What were the changes?
Created attachment 72 [details]
I assumed you would just do it and view the changes ;)
My peeve with this is that when I added a single new project MD automatically rewrote every csproj. Even if the change is valid it's weird for me that MD would take that action as an opportunity to rewrite what would appear to be completely unrelated csproj files.
Whenever the solution is saved, MD saves every project in the solution. That should be okay.
The problem here is that the project reference system appears to have annotated all the references with <Package> metadata. Package metadata is Mono-only, i.e. projects saved on .NET don't have it. So the problem is one of consistency in the deserializer/serializer and the reference resolver.
Ah, that makes sense. Hopefully there's a way to inform MD that that particular item can be inferred and doesn't have to be explicitly written in this kind of scenario. It's probably not worth investing a huge amount of time into at the moment as it'd only affect people who use both VS and MD on the same solution and also add/remove projects from it.
Most of unwanted changes should be fixed in master, and all of them in XS 6.0.