Thank you to TwentyFourMinutes for teaching me about source generators. Please take a minute to star his PostgreSQL ORM Repo github.com/TwentyFourMinutes/Venflow
This was super helpful. I was having a hard time getting started using the Microsoft Docs, but this has given me the confidence to really dig in. Just wish I'd found this 6 months ago. Thanks for the great video!
My preferred way of debugging source generators is via unit tests. Not only are they good to do to catch all the edge cases, as usual, but for source generators they provide a very nice entry point for debugging. Can write the test code you want to drive your source generator, run the test, and debug as your source generator processes it and creates output. Nice and clean. I only try my source generator against my actual end-usage source code when I'm mostly done with the source generator and want to give it that last final test.
Good example, but many of those practices are banned for the current implementations of ISourceGenerator. Do you have any video using IIncrementalGenerator?
could you please make a video about incremental source generators? I'm playing around with source generators, trying to create a service client based on an interface+models. this video really set something straight in my head THANKS!!!
Why not just use AppendLine with the StringBuilder? I don't understand why you're just using Append like it's the only way to use StringBuilder But honestly I wouldn't even use StringBuilder, I'd probably opt for the new triple equals feature.
It is worth noting that ISourceGenerator is deprecated and should NOT be used AT ALL. All generators should be using IIncrementalGenerator, the newer, much more performant and optimized, source generation API. This isn't just me saying this, this has been stated on multiple occasions by the compiler architects who work on Roslyn.
dotnet clean does not help on updating analyzer at all in my case. For everyone having th same issue, here is what I use: "dotnet build-server shutdown ; dotnet build"
How did you manage to make the source generator work for .NET6? According to docs and my experience, the generator only works when written on .netstandard 2.0 project.
that was before the api is changed, the problem with core is it changed too many times.. good thing now that we are on .net 7 things have come to a standardized version.
How can I share my soruce generator project as nuget package or assembly/dll reference, I couldnt really find documentation and it really doesnt work by just referencing, looks like it needs some configuration.
Could you make a video about learning / debugging 3rd party code (open source)? I have Rider installed so I am able to debug some of the code with the decompilation feature but often I get the "Could Not Evaluate The Value" error when trying to inspect a variables in 3rd party code. Great video btw! With the new "Raw string literals" feature coming in C# 11, do you think it's still better to use the Roslyn Quoter? Seem like the code would be much more readable with "raw strings" tho more error-prone.
Thank you, on the debugging - what advice could I give except covering your specific usecase? I feel like debugging is a bit of a skill like googling, otherwise with programming your just zooming in on the issue, by finding the correct place in the execution sequence. as for string literals - that's a nope, you'll have alot of "logic" processing strings and values to create syntax, it's not going to be 1 neat string literal, it's going to be many little pieces put together based on your rules.
Anyone ever told you that you look very much like Topher Grace? specifically with his hair and beard style from the black mirror episode "smithereens"? - Just with darker hair and no glasses haha
Thank you to TwentyFourMinutes for teaching me about source generators.
Please take a minute to star his PostgreSQL ORM Repo github.com/TwentyFourMinutes/Venflow
The most complicated 'Hello world!' toturial I've seen in my life. But I love it!
This was super helpful. I was having a hard time getting started using the Microsoft Docs, but this has given me the confidence to really dig in. Just wish I'd found this 6 months ago. Thanks for the great video!
My preferred way of debugging source generators is via unit tests. Not only are they good to do to catch all the edge cases, as usual, but for source generators they provide a very nice entry point for debugging. Can write the test code you want to drive your source generator, run the test, and debug as your source generator processes it and creates output. Nice and clean. I only try my source generator against my actual end-usage source code when I'm mostly done with the source generator and want to give it that last final test.
Pro tip
Really good content. I look forward to look into this area more.
Cheers
Good example, but many of those practices are banned for the current implementations of ISourceGenerator. Do you have any video using IIncrementalGenerator?
Your channel is so underrated. Thanks for another great video.
Amazing tutorial. Thanks
I loved the thumbnail, thanks as always
Wow awesome work! I needed this video ♥️
Glad you like it )
could you please make a video about incremental source generators?
I'm playing around with source generators, trying to create a service client based on an interface+models. this video really set something straight in my head
THANKS!!!
I’ll see when I get around to them
Valuable information 🙏🏻
Why not just use AppendLine with the StringBuilder? I don't understand why you're just using Append like it's the only way to use StringBuilder
But honestly I wouldn't even use StringBuilder, I'd probably opt for the new triple equals feature.
It doesn’t matter, using string builder will produce complex code in a source generator.
It is worth noting that ISourceGenerator is deprecated and should NOT be used AT ALL. All generators should be using IIncrementalGenerator, the newer, much more performant and optimized, source generation API. This isn't just me saying this, this has been stated on multiple occasions by the compiler architects who work on Roslyn.
dotnet clean does not help on updating analyzer at all in my case. For everyone having th same issue, here is what I use: "dotnet build-server shutdown ; dotnet build"
28:52 _"...I think they kinda deserve it"_ *shocked pikachu face*
Came here for that epic thumbnail lol.
Haha 😂
i'm using source generator to create full crud module (using mutation) from db to controller and its works well slowing down the build
Holy shit why would you do that
@@meJevin rapid app development/ boilerplate code
Love that thumbnail
How did you manage to make the source generator work for .NET6? According to docs and my experience, the generator only works when written on .netstandard 2.0 project.
Not sure what to tell you it just works
that was before the api is changed, the problem with core is it changed too many times.. good thing now that we are on .net 7 things have come to a standardized version.
Rossynt isnt working for newer versions of Rider?
haven't checked
How can I share my soruce generator project as nuget package or assembly/dll reference, I couldnt really find documentation and it really doesnt work by just referencing, looks like it needs some configuration.
check this out: github.com/T0shik/Shpec
let me know if you need help
@@RawCoding PackagePath="analyzers/dotnet/cs" is the key I was needed
07:34 - Debugging
23:30 - flag to store the file in output dir
Great content as always :)
Why use the timeout and breakpoint instead of 'Debugger.Launch();'?
I've not known about this, will check it out and write back here
Sorry can it apply for anything? I don't understand what it will apply
Use code as data to create more code.
@@RawCoding wow its great, can tou upload more video tutorial about this?
great video 😊
Cheers )
How do you open this window where you search for everything?
i saw there's a new thing online, incremental source generator, what's the difference and how it is better than this?
They are designed to take advantage of caching. Otherwise they are the same old source generators
@@meJevin thanks i believe i'll use it sooner or later, my app build is very slow
Crazy hot take that experienced devs debug less
Could you make a video about learning / debugging 3rd party code (open source)? I have Rider installed so I am able to debug some of the code with the decompilation feature but often I get the "Could Not Evaluate The Value" error when trying to inspect a variables in 3rd party code.
Great video btw! With the new "Raw string literals" feature coming in C# 11, do you think it's still better to use the Roslyn Quoter? Seem like the code would be much more readable with "raw strings" tho more error-prone.
Thank you, on the debugging - what advice could I give except covering your specific usecase? I feel like debugging is a bit of a skill like googling, otherwise with programming your just zooming in on the issue, by finding the correct place in the execution sequence.
as for string literals - that's a nope, you'll have alot of "logic" processing strings and values to create syntax, it's not going to be 1 neat string literal, it's going to be many little pieces put together based on your rules.
Why i am the only one my SourceGenerator is not generating anything i am not getting which step i missed
The way many other languages are able to generate code compared to what C# is capable of makes C# seems ridiculous
Anyone ever told you that you look very much like Topher Grace? specifically with his hair and beard style from the black mirror episode "smithereens"? - Just with darker hair and no glasses haha
Never, I had Jesus and Golfoyle
Followed this but ended catch-up by incremental police. VS yell at me I should use IIncrementalGenerator instead.
;)
You could simply add the following to Initialize() for Debugging purposes
#if DEBUG
if (!Debugger.IsAttached)
Debugger.Launch();
#endif
CTRL+SHIFT+A (Action Menu) -> Build, Execution, Deployment > Debugger -> "JIT Debugger" set Rider as a Default Debugger