Codex support for Visual Studio Professional please

The new Codex IDE extension looks promising, but I think it’s a big gap that it only supports VS Code.

A lot of professional developers — especially those working in enterprise .NET and C# environments — spend most of their day in Visual Studio Professional/Enterprise, not VS Code. These are also the same companies that actually have the budgets and motivation to pay for enterprise-grade AI tooling.

Right now, by limiting Codex IDE integration to VS Code, OpenAI is leaving out a huge slice of the developer community that would likely adopt (and pay for) this at scale. GitHub Copilot already runs inside Visual Studio 2022, which proves there’s both demand and technical feasibility for this integration.

It would make a lot of sense to prioritize Visual Studio Pro/Ent support so Codex can be used in the environments where enterprise developers actually work day-to-day.

Would love to see this on the roadmap — I know many others in .NET shops would too.

29 Likes


i think this is a great idea, i hate using my own MCP server and IDE! and having to make a database just to re-reference for my own development. not joking, maintence is blah

i was curious tho - and started asking why pro would be used over vs code, because i fr fr didnt know

but it seems i have alot to learn still - since i can make extension and ides automatically, and already have a working bridge between vs code and unreal engine 5.6 which uses c# with autoconversion i think a tool like this would be great.

image

anyway - wanna try to build a bridge together? pretty sure i can do this in a few days

like fr fr . and we can host the blueprints, i have a system that makes them

2 Likes

and started asking why pro would be used over vs code, because i fr fr didnt know

@dmitryrichard - “fr fr” does this mean French as in the language code “fr-FR”, or do you mean something like an abbreviation for “for real”?

I personally prefer Visual Studio over VS Code for .net development because I am more comfortable with using it. The layout of everything is clearer, and navigation, behavior, and interactions are well known to me so it is faster for me to produce quality .net based programs using the full VS that I’ve used for 20+ years now. VS Code didn’t even understand multi-project solutions until recently and support for it still seems kind of iffy.

I do use VS Code for other languages like Powershell scripts/modules and NodeJS projects (and I use Pycharm for Python). Full VS either has a lot of functionality that those languages/types of projects dont make use of or that those kinds of languages simply dont need.

I’ve worked in places where the development tooling is really locked down (banks, pharma) or there are some corporate policies that require using specific tools that have been reviewed and approved for use. That’s going to be another case where VS Code may not be an option. It may be hard to imagine the case where a business will prefer proprietary, closed source programs over FOSS but it is still a very real thing.

Not having support within full VS for a tool like this means I have to constantly switch between IDE’s, and we all know that context switching is the death of productivity.

Also GitHub Copilot needs proper competition.