Workshops: Agentic Coding by Tech Stack

Agentic Coding for .NET & C#: Workshop for Dev Teams

.NET teams work in more environments than most: Visual Studio, Rider and VS Code, legacy .NET Framework applications next to modern ASP.NET Core services. This workshop shows how to use coding agents across that landscape, from GitHub Copilot in Visual Studio and JetBrains AI in Rider to Claude Code and OpenAI Codex with the dotnet CLI, and how they help bring legacy applications to modern .NET.

Who is this workshop for?

  • C# developers building ASP.NET Core APIs, Blazor apps or background services
  • Teams maintaining .NET Framework applications with WinForms, WPF, WCF or ASP.NET MVC
  • Software architects planning the move to modern .NET
  • Developers who want consistent agent workflows across Visual Studio, Rider and VS Code
  • Microsoft-centric IT departments using Azure and Azure DevOps

What you will take away

  • Choose and configure agents for your IDE mix so everyone works with the same project rules.
  • Have agents implement ASP.NET Core features with dependency injection, options, logging and EF Core that follow your conventions.
  • Use nullable reference types, Roslyn analysers and dotnet format as automatic feedback for the agent.
  • Generate tests with xUnit, NUnit or MSTest as well as integration tests with WebApplicationFactory.
  • Assess a .NET Framework application for migration and let agents carry out well-defined porting steps.

Agenda

  1. Module 1

    Tools in the .NET world

    • GitHub Copilot in Visual Studio and VS Code, including agent mode
    • JetBrains AI Assistant and Junie in Rider
    • Claude Code and OpenAI Codex with the dotnet CLI in the terminal
  2. Module 2

    Shared context for every IDE

    • One set of rules across CLAUDE.md, AGENTS.md and Copilot instructions
    • Explaining solution structure, project references and build commands
    • Exercise: architecture summary of an existing solution
  3. Module 3

    Modern ASP.NET Core with agents

    • Exercise: an endpoint with validation, EF Core and tests
    • Minimal APIs or controllers: one convention, consistently enforced
    • EF Core migrations generated and reviewed, never applied blindly
  4. Module 4

    Quality gates

    • Nullable reference types and analysers as guardrails
    • dotnet format and .editorconfig
    • Integration tests with WebApplicationFactory and Testcontainers
  5. Module 5

    From .NET Framework to modern .NET

    • Assessment: dependencies, System.Web usage, Windows-only APIs
    • Porting libraries first, multi-targeting as a bridge
    • Where there is no drop-in successor: WebForms, WCF server and other gaps

The .NET Framework gap

Moving from .NET Framework to modern .NET is not one migration but several: project files, packages, configuration, hosting model and sometimes the UI framework. Some parts port almost mechanically; others, such as ASP.NET WebForms or WCF services, have no direct counterpart and need a redesign, for example towards Razor Pages, Blazor, CoreWCF or gRPC.

Agents excel at the inventory and the mechanical porting, and they help write the tests that prove behaviour is unchanged. We also show how Microsoft's own upgrade tooling fits in and how to split the work into reviewable steps.

Microsoft stack and data protection

Many .NET teams run on Azure, Azure DevOps and Microsoft 365. We explain the data flows of the tools you use, the difference between business and personal licences, and how to align agent use with your GDPR obligations and, where relevant, your works council. Legal assessment stays with your legal and compliance team.

  • Only approved tools with company accounts
  • No customer data in prompts or test fixtures
  • Connection strings and secrets kept out of the agent's context

Working with your solution

The day is most valuable with your own solution. If code may not be shared, we prepare a sandbox solution that mirrors your architecture. Remotely or on-site, in English or German, led by neooutput AI Code Engineers.

Frequently asked questions

Does the workshop cover desktop apps built with WPF or WinForms?

Yes, as far as agents can help: understanding and documenting code, writing tests for business logic and porting to modern .NET. Developers check UI-heavy work themselves, as agents cannot reliably judge desktop interfaces.

Is GitHub Copilot enough, or do we need other tools?

Many .NET teams start with Copilot because it is integrated into Visual Studio. Terminal agents such as Claude Code or OpenAI Codex add strength for larger multi-file tasks and migrations.

Can agents work with Azure DevOps instead of GitHub?

Yes. The local agent workflow does not depend on the Git host. We adapt branches, pull requests and pipelines to Azure DevOps or GitLab where needed.

Workshop

Get in touch

Is there a .NET Framework application your team would love to bring to modern .NET?

Tell us roughly how many people will join and pick dates that work – we will get back to you within 24 hours with a proposal for content, format and schedule.

Prefer to talk first?

15 minutes, free and without obligation – with our AI Trainers and AI Code Engineers.

Book a call for free (opens in new tab) +49 761 519 751 50 (24/7)

Request a training / workshop

Workshop: Agentic Coding for .NET & C#: Workshop for Dev Teams · 1 day

Dates that work for you (optional)

Suggestions about 2 weeks ahead – pick as many as you like

Reply usually within 24 hours · jocapps is ISO 27001 certified · Privacy