Hello everyone, I'm Gangzi, a seasoned .NET developer with years of experience in the industry.

A few days ago, I received a message from a fellow developer that really struck a chord: "Does C# still have a future? I heard XinChuang policies are excluding it. Should I be worried about my career in .NET?"

Honestly, when I read that message, I felt a pang of sympathy. This concern is shared by many in our community, and today I want to break down this issue thoroughly and provide some clarity on what's really happening.

Understanding the Origin of This Concern

The controversy first emerged in 2024 when the Shanghai Municipal Health Commission released a document titled "Shanghai Health Information Technology Application Innovation White Paper." In this white paper, C#/.NET was categorized as a "Class A Component," marked in red to indicate the highest risk level—essentially labeling it as technology that should be gradually phased out.

This white paper carries significant policy weight for IT system construction in public hospitals across Shanghai. In practical terms, it means that future informatization projects in Shanghai's public hospitals are discouraged from procuring systems built with C#/.NET, with a strong recommendation to migrate away from these technologies.

The reaction was immediate and intense. Consider this: countless core hospital systems nationwide—HIS (Hospital Information Systems), LIS (Laboratory Information Systems), PACS (Picture Archiving and Communication Systems), and EMR (Electronic Medical Records)—were developed using .NET technologies. When this document was released, .NET vendors specializing in healthcare informatics found themselves in a state of genuine panic.

Why Was .NET Classified as a "Class A Component"?

After thoroughly researching the criteria for Class A component classification, I discovered that the white paper determines this status based on three main criteria:

  1. Source code is not publicly accessible (does not meet open-source definitions)
  2. Core technology control does not reside within China
  3. Existence of supply chain security risks

In simpler terms, from the perspective of policy makers, C#/.NET is still perceived as that legacy Microsoft closed-source technology exclusive to Windows.

However, this assessment is severely outdated and does not reflect current reality. Here are the facts that policy makers may have overlooked:

  • C# has been open source since 2014, when Microsoft made the decisive move to open source the language specification and compiler
  • .NET Core has been open source and cross-platform since 2016, fundamentally transforming the technology stack
  • .NET 8 is fully open source and governed by the neutral .NET Foundation, ensuring community-driven development
  • Native support for Chinese operating systems: .NET runs seamlessly on Kylin, UnionTech, and other domestic operating systems
  • Domestic CPU architecture support: .NET has official support for LoongArch64 architecture from Loongson, and official adaptation packages have been released for domestic CPUs including Loongson, Phytium, and Kunpeng

There's a saying circulating in the technology community: "There are no longer technical barriers to using .NET in the XinChuang field." One developer even showcased their company's project portfolio: more than a dozen .NET Core projects running on Kylin servers with Dameng database as the backend—proving that the technology stack is not only viable but production-ready.

The essence of this issue is clear: policy judgment has significantly lagged behind technological evolution. This gap between perception and reality is at the heart of the current anxiety.

The Rationale Behind Policy Decisions

To truly understand this situation, we need to step into the shoes of policy makers and consider their perspective.

The core objective of XinChuang (Information Technology Application Innovation) is "autonomous controllability"—replacing foreign technologies with domestic alternatives in critical sectors to avoid being constrained by external forces ("carded by the neck").

What's the bottom line for policy makers? In 2022, SASAC (State-owned Assets Supervision and Administration Commission) issued Document No. 79, which mandates that central and state-owned enterprises must complete their XinChuang transformation by the end of 2027.

The timeline is tight, and the tasks are demanding. Decision-makers simply cannot afford to research the actual status of each technology individually. The simplest approach is a "one-size-fits-all" strategy: exclude any technology where core control rests with foreign companies. Better to err on the side of caution than risk potential vulnerabilities.

Even though .NET is now open source, Microsoft remains an American company in the eyes of policy makers. The concern is valid from their perspective: what if US-China relations deteriorate to the point where Microsoft is prohibited from providing technical support to China? What happens to all these systems then? This is a risk that no decision-maker wants to personally bear responsibility for.

So What Should .NET Developers Do? Is There No Future?

Friends, don't panic. The situation is not as dire as it may seem. Let me explain why:

First, XinChuang Does Not Equal the Entire Market

The Shanghai Health Commission's document only has binding authority within Shanghai's public healthcare system. Across the country, there are numerous sectors and enterprises that are not subject to mandatory XinChuang requirements:

  • Private enterprises continue to choose technologies based on merit and business needs
  • Foreign-invested enterprises often maintain their existing technology stacks
  • Non-critical infrastructure sectors have more flexibility in technology choices
  • Game development (Unity engine relies heavily on C#) remains a strong .NET stronghold
  • Industrial automation continues to depend on .NET for SCADA and control systems
  • ERP systems in many organizations are built on .NET frameworks

C# remains a mainstream technology in these domains, and the demand for skilled .NET developers remains robust.

Second, .NET Technology Itself Is "Clean"

As mentioned earlier, .NET 8 is fully open source and cross-platform. Domestic CPUs and operating systems have official adaptation packages available. Many companies are already successfully running XinChuang projects on .NET Core—the technology is proven and viable.

The entire .NET community is actively promoting ecosystem localization:

  • NCC (.NET China Community) is driving open-source ecosystem development
  • Senparc Developer Community is building localized tools and libraries
  • Domestic contributors are increasingly involved in the .NET Foundation

This grassroots movement demonstrates that the technology is not only capable but actively evolving to meet local needs.

Third, Policies Are Dynamic and Evolvable

Following this incident, technical experts and developers from the .NET community collectively voiced their concerns, pointing out that the white paper's assessment of C#/.NET contains significant technical inaccuracies.

While as of March 2026, there has been no official public correction, matters like this typically undergo multiple rounds of discussion and review. We can reasonably expect that future policies will become more scientifically grounded as technical realities are better understood.

Practical Advice from Gangzi

If you're currently using .NET or considering learning it, here are three pieces of actionable advice:

1. Don't Focus Solely on WinForms and WPF

These technologies do have strong Windows dependencies that make them challenging in XinChuang environments. Instead, expand your skill set:

  • ASP.NET Core for backend development—runs excellently on Linux
  • Avalonia for cross-platform desktop applications—native support for Linux, macOS, and Windows
  • MAUI (Multi-platform App UI) for mobile and desktop applications
  • Blazor for web-based user interfaces using C#

These modern .NET technologies are designed with cross-platform compatibility in mind and perform well in Linux-based XinChuang environments.

2. Business Domain Knowledge Trumps Language Proficiency

You are a problem-solver, not a "human accessory" to C#. The core competency of an excellent developer is always the ability to solve problems effectively, not mastery of a specific programming language.

Consider this: a developer who understands healthcare workflows, financial regulations, or manufacturing processes is infinitely more valuable than someone who only knows syntax. Invest in understanding your industry domain—it's the differentiator that will sustain your career regardless of technology shifts.

3. Maintain Technical Sensitivity and Adaptability

Keep an eye on what's happening in the broader technology landscape:

  • What are Java developers building?
  • How is Go being adopted in cloud-native environments?
  • What problems is Python solving in AI and data science?

This isn't about abandoning .NET—it's about being prepared. If the day comes when you need to transition or expand your toolkit, you won't be caught off guard. Versatility is your insurance policy.

A Final Word of Honesty

Does C# and .NET have a future? Absolutely, yes.

It's true that the XinChuang market is narrowing the survival space for .NET in certain government and state-owned enterprise sectors. However, .NET remains one of the mainstream technology stacks globally, with millions of developers and countless production systems.

Moreover, the .NET ecosystem is accelerating its domestic adaptation efforts in China. This actually presents an opportunity: developers who understand how to deploy .NET in XinChuang environments will become highly sought-after specialists. There's a first-mover advantage for those who can bridge this gap.

Don't let every rumor send you into a panic. Continue learning, continue building, continue solving problems. The most valuable asset for a technology professional has never been the specific language you know—it's your ability to deliver solutions that create value.

If this article helped clarify the situation for you, please share it with fellow developers who may still be anxious. Knowledge dispels fear, and our community is stronger when we support each other.

I'm Gangzi, an old .NET programmer who's still writing code and believing in the future of this technology stack. See you next time!

Note: This article is based on publicly available information and personal analysis. Policy situations may evolve, and readers are encouraged to stay informed through official channels.