Be advised: this thread is not for serious in-depth discussion of weighty topics (we have a link for that), this thread is not for anything Culture War related. This thread is for Fun. You got jokes? Share 'em. You got silly questions? Ask 'em.
- 188
- 1
Jump in the discussion.
No email address required.
Notes -
That is pretty funny that they changed the official documentation to just say to use an agent.
Like, I can sort of see the idea: upgrading from .NET Framework always had too many edge cases for the dummy automated tools to ever really work fully correctly. There was always cleanup to do afterwards, so wouldn't it be nice to have an agent do that whole process instead? But if the recommended agent isn't actually smart enough to do it, then that's just giving up on maintaining any actual solution.
I'd agree with the other comment though that a normal non-agentic LLM could probably do the task way better. If your projects really are small, you could probably just go one at-a-time, concatting each .csproj file with all its .cs files into one big .txt file (labeling each file within the big text blob), feed that to Gemini Pro or some equivalent smart and big-context model, and let it give you back all the changes you need. Would still be a slower process than the CLI, though it might handle some of the edge cases better (especially where there aren't directly equivalent APIs).
In any case, the good news is that once you're through the .NET upgrade, you never need to worry about .NET Framework again. Only poor, poor Microsoft still needs to worry about .NET Framework. I kind of feel bad for them, except that it's also kind of their fault what with the bad communication that so many organizations are still on it.
More options
Context Copy link