Is there an existing issue for this?
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:
- 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.
- Make the information output by various tools more agent-friendly (especially debugging information), and conserve tokens.
- 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
Is there an existing issue for this?
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:
Additional context
See NextJS team's blog about version 16.2