Andy Gerlicher

+1 on this. In MSBuild we use binary serialization all over (uhg) and changing private fields on [Serializable] classes changes the contract for serialization. It would be good to detect...

In the xplat branch, we've been using monodevelop / Xamarin Studio. Have you tried that branch? And if so what issues are you seeing?

I'll close this then. Reopen if you have any issues.

Uhg, I was working in the msbuild repo and clicked on this issue link in my email... There's definitely not an xplat branch or Linux support here, so I'll reopen....

Just FYI discussing this internally with the MSBuild team. I want to make sure this aligns with their vision before we make this change. Sorry for the delay!

Exactly the same thing happened to me, also started a few days ago. Same error. I have both a `Floodlight Cam Pro` and a `Floodlight Cam`. I get the normal...

@tmat Just to add some ammo here, I really think the version information in the assembly by default should be rolled back. Essentially, incremental build (or caching) is fundamentally broken....

I agree just disabling that for reference assemblies would be sufficient for most cases. Although then you would have assembly version differences between the two which seems odd. And I...

I definitely agree turning it on is good. It's just the stamping of the assembly version that breaks even VS scenarios I don't think was thought through fully. I don't...

That's correct it's only really an issue for ref assemblies, although it would seem odd for the reference assembly version information to differ from implementation. And yes, our workaround is...