CCRewrite unhappy with Toolset Compilers 1.0.0-rc1-20150113-03 about roslyn

[codespare]

And re-reading myself I realize nuget also has an issue merrily upgrading Microsoft.Net.ToolsetCompilers 1.0.0-beta2-20141223-03 to Microsoft.Net.ToolsetCompilers 1.0.0-beta2-20141216-04 instead of Microsoft.Net.ToolsetCompilers 1.0.0-rc1-20150113-03... but the issue remains after rectifying that (and double checking the .csproj and the build output and restarting Visual Studio).

[tmat]

Could you share the binary before CC rewrites it?

[tmat]

I think I found what the problem is in Code Contracts. I have contacted the owners to see how CC can be fixed.

[codespare]

Apologies for the delay in replying, I should check github web interface more often... Do you or the Code Contracts team still want the assembly prior to rewrite?

[tmat]

Not necessary. We know where the problem is. As a workaround I'd recommend avoiding using Code Contracts in iterator and async methods.

[codespare]

All right, that's manageable, thank you. I saw even ILSpy can only render the complete source in IL, and by the looks of it, rewriting that is no mean feat. Hopefully no one will request an async iterators feature :)

[gafter]

@tmat Can you please close this issue if it isn't actionable in the Roslyn code base?