@shahid_pk Sorry for the late reply.
Thank you very much for the link It can been useful for the C++ part of mscorlib, but I’d like to add some comments.
Visual Studio and mscorlib managed C# part debugging
Last paragraph reads
To step into and debug managed code of Mscorlib.dll … using Visual Studio, is something that will be supported with Visual Studio 2015. We are actively working to enable this support.
Any updates about it??
mscorlib for unit test
Also, I discovered that I needed to copy (overwrite) the more recently compiled files from the Product x64 directory into the CoreRun (test runtime) directory to make the changes of
mscorlib effective during the unit tests (I prepared a new unit test in the
Another problem was the long time it took to
build -rebuild everything from scratch: I’ve noticed that I could use the much more effective
build windowsmscorlib followed by
build nativemscorlib for C# changes in mscorlib, while
build skiptests was the way to go for the C++ part.
Still I don’t know how to rebuild only the
readytorun part without taking the long way of a full (and very slow)
build-test.cmd? (solved the only mandatory folders are baseservices, Common, TestWrappersConfig so it can be made faster…)