Home Modernization .NET Application

Modernize the .NET application or continue maintaining it?

Jenny Bichsel

Jenny Bichsel

Senior Project Manager

+41.. Show number
Get expert advice. Our References

Expert knowledge for your project

Jenny Bichsel is a senior project manager at soxes. She has a background in business, numerous professional certifications in IT project management from KV Zürich Business School and over 20 years of experience in the industry. She loves to get to the heart of complex projects and implement them successfully with calmness, structure, and foresight.

Contents

.NET Application

When changes become time-consuming, knowledge is lacking, and your application becomes a risk

Your .NET application may still be running. But internally, you’ve long since noticed that something isn’t right. Minor changes take too long, updates are put off, knowledge is concentrated in the hands of a few people, and every modification feels riskier than it should.

This is exactly what many companies experience with legacy .NET solutions. Not because .NET is the problem, but because the application has had to handle more and more over the years, becoming increasingly complex, harder to modify, and more prone to errors. Here, you’ll learn how to recognize warning signs, what business risks lie behind them, and when maintenance is still sufficient or when modernization makes sense.

Alexandra Mittmann, Team Lead Project Management

Alexandra Mittmann, Team Lead Project Management

The most important question is not: Is the technology outdated? But rather: Can the application still reliably support the business without changes becoming a risk?

Why does this affect so many companies?

These issues are very common. Many .NET applications were developed when the company was at a different stage of its development. Later, new processes, interfaces, users, security requirements, and operational expectations were added. In day-to-day operations, there is rarely time to keep the technical foundation up to date. As a result, complexity grows gradually until making changes becomes expensive, slow, and risky.

You’ve come to the right place if…

  • Changes to your .NET application are becoming increasingly complex
  • Releases seem unreliable
  • Knowledge is tied to individual people
  • Updates and integrations are causing problems
  • You want to determine whether maintenance is still sufficient or modernization is necessary

Common Problems with .NET Applications in Everyday Use

  • Small changes require a disproportionate amount of effort

  • Releases are postponed or released with uncertainty

  • Knowledge is held by only a few people

  • New tasks are left undone

  • Updates are being postponed

  • Errors are difficult to pinpoint

  • Interfaces result in significant additional effort

  • Internally, no one really wants to deal with the application

Business Risks and Impacts

Financial Risks

As changes become increasingly complex, costs rise gradually. Typical consequences:

  • higher costs per change
  • higher costs for support and troubleshooting
  • increasing dependence on specialists
  • Additional effort due to manual workarounds

Operational risks

Many problems directly impact day-to-day operations. Typical consequences:

  • Disruptions in key processes
  • Longer response times when errors occur
  • Unreliable releases
  • Increased workload for IT and business units

Strategic risks

If the application becomes a roadblock, a strategic problem arises. Typical consequences:

  • New requirements are delayed
  • Integrations become more difficult
  • Innovation is blocked
  • Loss of know-how becomes a corporate risk

Why do these problems arise?

The causes are rarely purely technical. Common reasons include:

  • the application has grown over the years
  • Dependencies are not properly documented
  • Knowledge is tied to specific individuals
  • Operation and further development were never clearly separated
  • new requirements have grown faster than the software base
  • Roles and responsibilities are unclear

Infographic on the topic of Net. Challenges

Possible solutions

Technical Solutions

  • Improve monitoring and logging
  • Highlight critical dependencies
  • Targeted cleanup of problematic areas in the code
  • Implement tests where they reduce risk
  • Decouple interfaces and architecture
  • Gradually modernize outdated components

Organizational Solutions

  • Clearly define responsibilities
  • Document knowledge and share it more widely
  • Align business units and IT on shared priorities
  • Consciously distinguish between operations, stabilization, and further development

Case Study: Modernizing .NET Interfaces

Go to References
  • Case Study: Modernizing .NET Interfaces

  • From the 32-bit risk to a stable 64-bit solution.

  • 1 Project Overview

    Sika Services AG used a proven software solution for material testing and torsional stiffness measurements. However, with the switch to Office 365 and modern IT infrastructures, it became clear that the existing 32-bit interfaces were no longer future-proof.

  • 2 Challenge

    The measurement method needed to continue functioning reliably without losing any existing logic. At the same time, the solution had to be compatible with 64-bit environments, easier to install, and better integrated into the future IT infrastructure.

  • 3 Solution

    soxes developed an independent .NET-based interface that seamlessly connects the defined spreadsheet to the verification engine. The existing VBA logic was carefully ported, technically decoupled, and enhanced to simplify operation, maintenance, and further development.

  • 4 Result

    The new 64-bit .NET interface ensures the continued operation of the proven measurement system and makes it compatible with Office 365. Sika benefits from more stable integration, simplified maintenance, and a solution that also supports future enhancements.

Maintenance or modernization?

Maintenance is sufficient if ...
Modernization is necessary when ...

the application serves its purpose

any change is unreasonably expensive or risky

the code is manageable

the architecture is hindering new requirements

critical processes run smoothly

important integrations are difficult to implement

the biggest problems lie in operations, documentation, or transparency

Safety requirements are not being properly met

Risks can be mitigated at a reasonable cost

the technological foundation is not sustainable in the long term

there is too much reliance on individuals

Frequently asked questions

  • Do we have to completely rebuild our .NET application?

  • Is an old .NET application automatically a problem?

  • What is the first sensible step?

  • What are typical problems with .NET applications?

  • When is maintenance enough for a .NET application?

  • When should a .NET application be modernized?

Contact

Do you have any questions? Would you like to find out more about our services?
We look forward to your enquiry.

Contact us
Sofia Steninger

Sofia Steninger
Solution Sales Manager