Problem when trying to build from source and debug. Again...

[DoctorKrolic]

I haven't done debugging of this repo for a while, so this error may have appeared before, therу is no evidence, that it appeared after upgrading to the latest VS preview. Tried to build and debug with v17.2 Preview 1. After loading a blazor project I got an error bar, saying that there was a problem loading it. There was also an exception stack attached. Here it is:
VsProjectFault_eeae0f32-9cba-416e-b437-775eb921dbbe.failure.ru.en.txt. Note that the file was processed by translator, because I use VS not in English and the original report was not in English either. Help me please😥

[NTaylorMullen]

@DoctorKrolic could you try reverting this commit to see if it fixes your experience?

[DoctorKrolic]

Done via command line: git revert e873be1d166ce64ad6879d704ce2dd7594288907, got some messages about merge conflics
Checked, that commit was actually reverted
Tried to open project in VS - it got stucked at "Loading project 2 of 39 Microsoft.CodeAnalysis.Remote.Razor". After some time VS completely freezed

[DoctorKrolic]

But I got an idea of what is wrong. e873be1 bumps Roslyn version to 4.2.0-2.22108.10, while 17.2 Preview 1 is using 4.2.0-1.22108.11. It seems like I will be able to debug this repo only when Preview 2 comes out. This is sad...

[NTaylorMullen]

Tried to open project in VS - it got stucked at "Loading project 2 of 39 Microsoft.CodeAnalysis.Remote.Razor". After some time VS completely freezed

I had this too actually the other day and re-running restore.cmd + re-opening VS solved it

But I got an idea of what is wrong. e873be1 bumps Roslyn version to 4.2.0-2.22108.10, while 17.2 Preview 1 is using 4.2.0-1.22108.11. It seems like I will be able to debug this repo only when Preview 2 comes out. This is sad...

We'll get you unblocked so you don't have to, definitely don't want you to have to wait

[DoctorKrolic]

I had this too actually the other day and re-running restore.cmd + re-opening VS solved it

Well, it helped. Now I need to adress 255 build errors that occured...

[NTaylorMullen]

Well, it helped. Now I need to adress 255 build errors that occured...

O_O, I wouldn't think you'd get any. What sort of build errors?

[DoctorKrolic]

After reverting the proposed commit manually everything got fine. There were some merge conflicts when I tried to revert commit by command. It was late for me yesterday and I didn't notice them. I'll keep this issue open until 17.2 Preview 2 so if anyone try to build razor tooling from source can see this conversation

[ryanbrandenburg]

Sorry about this, we're thinking about ways to avoid such disruptions in the future. In the mean time this should be resolved when 17.2 Preview 2 comes out ~soonish, and in the mean time if anyone runs into this issue they can revert the indicated commit.