Method Design Screen Issue

Radzen Blazor Studio
58

Hi @korchev,

I've tried to write an absolute re-procedure list for the last 2 hours. I was unsuccessful many times. The closest test list is as follows (The lag started but not increased.)

  1. Open the test project that was shared by me.
  2. Try to create an event a couple of times (the " sign was not deleted from the #endregion directive).
  3. .razor and .razor.cs files are saved each time.
  4. Remove the " sign.
  5. Create a couple of events using the designer.
  6. Delete one of the events that were created by the designer from the .razor.cs file.
  7. Save the file.
  8. Open the .razor file and wait for the error message.
  9. Try to delete the event's name from the events tab. (Many times the event's name cannot be deleted.)
  10. Save the page
  11. Delete the event from the source manually.
  12. Repeat these procedures for each event that was created by the designer.
  13. Open another solution. This solution must be big.
  14. Open a couple of .razor pages.
  15. Collapse all the collapsable lines from the inside out.
  16. Save each page.
  17. The lag effect must be started.
  18. If no lag effect started then open the previous project and try to same routine.
  19. In my cases the third try is enough to feel the lag effect.

I hope it works on your side.