Skip to content

Let ASP.NET be more agent-friendly #66008

@yhcedpn

Description

@yhcedpn

Is there an existing issue for this?

  • I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

Currently use agent to develop and debug ASP.NET programs has friction. I always need manual intervention to help the Agent find its way.
ASP.NET is not agent-friendly.

Describe the solution you'd like

We can follow the example of Next.js 16.2 and add the following:

  1. Integrate documentation directly into the package. Currently, code generated by models such as GPT typically relies on solutions from one or two years ago, rather than utilizing the most recently added APIs and syntax. The goal is to enable the model to utilize the latest features and syntax.
  2. Make the information output by various tools more agent-friendly (especially debugging information), and conserve tokens.
  3. Make it easier for the Agent to directly launch and interact with services, avoiding conflicts and duplicate startups. Currently, launching service processes from different locations results in the use of different ports (Visual Studio utilizes its own specific configuration, distinct from the behavior observed when directly launching the executable via a double-click). MCP may be helpful.

Additional context

See NextJS team's blog about version 16.2

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions