Blazor Pre-render / .NET 6 Source Generators about blog-examples HOT 2 CLOSED

Hi @dotdiego,

As you saw, the problem with the new razor build style you have is that you can't use a source generator to easily get the components. The way I see it, you have several options:

• Carry on with what you're doing
• Rework the build process slightly:
  • Build your app
  • Run the PostBuildEvent
  • Rebuild your app and embed the json as an embedded source. This way it ships down in the same dlls
• Do the same as above, but convert your powershell script to output a .cs file instead of json, and just compile as normal
• Disable the Blazor source generations, and do the other approach you describe
• Keep the Blazor source generation, Parse the .razor files yourself, and take the approach you describe

As for which approach you want to take, that's entirely dependent on how much pain you want 😄 If it was me, I would probably carry on with the approach you're already using, until they fix the source gen issue in .NET 7🤞 Given the size of Blazor Wasm, what's one more JSON file between friends 😉

from blog-examples.

Haha thanks for the quick reply.
I do not understand exactly everything about source generators yet, but yes I think i'll keep the pain level to a minimum seeing the other options i have for now. And that i just need a year to wait if they fix this issue in .NET 7

from blog-examples.