Architectural refactoring<\/h2>\n
This release introduces a major refactor of Dev Proxy\u2019s architecture to better align with .NET features. We\u2019ve:<\/p>\n
- \n
- Adopted .NET Dependency Injection to simplify object management<\/li>\n
- Reorganized project structure for better clarity<\/li>\n
- Replaced event-based plugin architecture with base methods<\/li>\n
- Improved code consistency and alignment with .NET conventions<\/li>\n<\/ul>\n
This change allows us to set the foundation for a more scalable and maintainable project going forward.<\/p>\n
Breaking changes<\/h3>\n
As a result of the refactoring, we have the following breaking changes:<\/p>\n
- \n
- The assembly with standard Dev Proxy plugins is now named DevProxy.Plugins.dll<\/strong>. The assembly with shared code for building custom plugins is named DevProxy.Abstractions.dll<\/strong>.<\/li>\n
- Custom plugin architecture has changed, introducing a different base class. We also no longer use events, but virtual methods which you can override in your custom plugins.<\/li>\n
- Changed organization of shared code and other utilities in the DevProxy.Abstractions assembly.<\/li>\n<\/ul>\n
Dev Proxy MCP server<\/h2>\n
We\u2019re excited to announce the release of the Dev Proxy MCP server! Use our server to:<\/p>\n
- \n
- Create Dev Proxy configurations using natural language<\/li>\n
- Get contextual help for working with Dev Proxy<\/li>\n
- Discover Dev Proxy features and capabilities<\/li>\n<\/ul>\n
For a long time, we\u2019ve wanted to let you configure Dev Proxy using natural language. Dev Proxy offers many features and supports a wide range of scenarios, but if you\u2019re not using it regularly, it might take you a while to discover what\u2019s possible and how to correctly configure Dev Proxy.<\/p>\n
With the advancements in LLMs we\u2019ve been getting closer and closer to this ability. The recent support for MCP (Model Context Protocol) servers was the final piece of the puzzle that we needed. Using a custom MCP server, we can provide AI agents with the necessary information about Dev Proxy to help you configure it for your needs!<\/p>\n
Here are some examples of how you can use our MCP server with the GitHub Copilot agent in Visual Studio Code:<\/p>\n
![\"GitHub](\"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-content\/uploads\/sites\/73\/2025\/06\/word-image-24434-1-2-scaled.png\")
GitHub Copilot in Agent mode creating a Dev Proxy configuration for simulating Microsoft Graph behaviors using the Dev Proxy MCP server<\/em><\/p>\n![\"GitHub](\"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-content\/uploads\/sites\/73\/2025\/06\/word-image-24434-2-2-scaled.png\")
GitHub Copilot in Agent mode creating a Dev Proxy configuration for simulating latency on a public API using the Dev Proxy MCP server<\/em><\/p>\nIf you use Visual Studio Code, you can get our MCP server by installing Dev Proxy Toolkit<\/a> from the extension marketplace. Otherwise, get it from npm<\/a> and follow the instructions for your MCP host to use it.<\/p>\n
Try it and let us know! We\u2019d love to hear from you what\u2019s working and what else we should consider to make it better for you.<\/p>\n
Exposed Dev Proxy LM prompts<\/h2>\n
Dev Proxy uses language models to improve some of its features, such as generating OpenAPI specs or TypeSpec files. By default, we use llama3.2 on Ollama, but you can switch to any other language model and host. While researching language models we realized that when you use a different language model, you also need to update the prompt.<\/p>\n
Dev Proxy now exposes the language model prompts used in features like OpenAPI and TypeSpec generation. This gives you full control to tailor prompts when switching models. Our prompts are exposed in the prompt<\/strong> folder in Dev Proxy\u2019s installation directory. To let you easily test them, we store them as Prompty<\/a> files.<\/p>\n
![\"A](\"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-content\/uploads\/sites\/73\/2025\/06\/word-image-24434-3-2-scaled.png\")
<\/p>\nImproved logging with logger categories<\/h2>\n
Debugging just got easier. Dev Proxy now prints the logger category for debug and trace messages, helping you quickly identify where logs originate in the application.<\/p>\n
![\"Dev](\"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-content\/uploads\/sites\/73\/2025\/06\/word-image-24434-4-1.png\")
<\/p>\nCertificate cleanup on uninstall (Windows)<\/h2>\n
Uninstalling Dev Proxy on Windows now removes the root certificate that Dev Proxy uses for decrypting HTTPS traffic, ensuring a clean uninstall experience.<\/p>\n
New version of Dev Proxy Toolkit<\/h2>\n
Dev Proxy Toolkit is a Visual Studio Code extension that makes it easy to create and update configuration files. Alongside the new release of Dev Proxy, we\u2019ve also released a new version of the toolkit, v0.26.0.<\/p>\n
In this version, we\u2019ve included:<\/p>\n
- \n
- Dev Proxy MCP Server<\/li>\n
- Updated snippets with 0.29 schema and new plugin DLL name<\/li>\n
- Plugin path guidance and code action to identify and update old DLL references<\/li>\n
- Generate JWT command<\/li>\n<\/ul>\n
We\u2019ve also updated the way we handle upgrades. When you choose to upgrade Dev Proxy via the upgrade toast notification, if you installed Dev Proxy via a package manager, we now upgrade Dev Proxy in the background for you.<\/p>\n
Checkout out the changelog<\/a> for more information on changes and bug fixes.<\/p>\n
Try it now<\/h2>\n
Download Dev Proxy v0.29<\/strong> and try the new architecture, better customization, and improved diagnostics. Thanks again to Artem Azaraev<\/a> for contributing to this release.<\/p>\n
Got feedback or ideas? Join us<\/a> and be part of the conversation.<\/p>\n
Follow us on <\/em>X,<\/em><\/a> LinkedIn<\/em><\/a>, and subscribe to our <\/em>YouTube<\/em><\/a> channel to stay up to date on the latest developer news and announcements.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"
Introducing Dev Proxy v0.29, with a major architectural overhaul, control over language model prompts, and improved diagnostics.<\/p>\n","protected":false},"author":74222,"featured_media":24443,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[186,289,398],"class_list":["post-24434","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-microsoft-365-developer","tag-net","tag-dev-proxy","tag-mcp"],"acf":[],"blog_post_summary":"
Introducing Dev Proxy v0.29, with a major architectural overhaul, control over language model prompts, and improved diagnostics.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/24434","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/users\/74222"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/comments?post=24434"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/24434\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media\/24443"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media?parent=24434"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/categories?post=24434"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/tags?post=24434"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- The assembly with standard Dev Proxy plugins is now named DevProxy.Plugins.dll<\/strong>. The assembly with shared code for building custom plugins is named DevProxy.Abstractions.dll<\/strong>.<\/li>\n