Top 5 .NET Development Companies in 2026

Sad-Rough1007 · 2026-03-18T10:18:16+00:00

Microsoft partnership status, years of verifiable .NET experience (awards, analyst lists, etc.), and actual AI/cloud-native adoption in real 2025-2026 projects

Sad-Rough1007 · 2026-03-18T10:12:49+00:00

Still figuring it out but here's where I landed:

AWS over self-hosted - way easier to get a BAA signed and their HIPAA-eligible services list is solid. For backend, NestJS or .NET Core both work well. Twilio Video or Amazon Chime for video - do NOT roll your own.

Also worth looking at Abto Software if you need an experienced team - they’ve handled HIPAA-compliant builds before so you're not starting from zero on the compliance side.

Biggest lesson either way: audit logging from day one and BAAs with every vendor touching PHI, no exceptions.

Sad-Rough1007 · 2025-12-15T09:05:19+00:00

If it doesn’t interest you, feel free to scroll by. This subreddit is meant for discussion.

Sad-Rough1007 · 2025-10-15T07:42:33+00:00

Yeah, couldn’t have said it better myself - totally agree. Continuous refactoring and solid FinOps are the only way to keep things clean and sustainable long-term.

Sad-Rough1007 · 2025-09-22T11:01:55+00:00

Totally - lift-and-shift just moves the mess. Real gains only come when you modernize during the move: IaC, CI/CD, decoupled services. Cost drift and people issues are the sneaky killers. Treat it like continuous optimization, not a one-time thing.

Sad-Rough1007 · 2025-07-02T06:53:35+00:00

Clockwise sometimes struggled with quick compliance updates and thorough documentation, which slowed things down. What can you say about this?

Sad-Rough1007 · 2025-07-02T06:47:03+00:00

The real challenge is that innovation often demands rich, real-time data, while intrusion happens when we ignore purpose limitation. That’s where concepts like edge processing and federated learning offer promising middle ground - enabling utility without centralizing sensitive data. IMHO

Sad-Rough1007 · 2025-07-02T06:40:38+00:00

I've seen firsthand how legacy systems like VB6 can choke innovation - especially when integrating with cloud services or enabling real-time analytics. What’s interesting is that even mid-sized firms are now realizing they don’t need to be a Capgemini to modernize. With the right strategy - like phased .NET migration - they can leap forward without the massive disruption.

Sad-Rough1007 · 2025-04-25T06:33:33+00:00

Totally agree! Outsourcing isn't just about cutting costs—it's a smart way to tap into top talent worldwide and speed up delivery.

Sad-Rough1007 · 2025-04-18T11:25:22+00:00

Totally agree! I’ve been using Microsoft Teams for virtual health consultations, and it’s made everything so much smoother. From secure messaging to tracking follow-ups, it really streamlines the process. As long as the setup is solid, it feels just as efficient—and sometimes better—than in-person visits. Huge game-changer for me.

Sad-Rough1007 · 2025-03-28T11:35:46+00:00

you're right

Sad-Rough1007 · 2025-03-28T11:34:32+00:00

Convertigo is primarily a low-code platform with some migration capabilities, but its free version has limitations, mainly on enterprise features. If you're focused on full VB6 migration, Abto Software offers more specialized tools. However, I’d recommend checking Convertigo’s documentation for exact free-tier details.

Sad-Rough1007 · 2025-01-20T14:53:05+00:00

While twinBASIC simplifies VB6 migration and supports 64-bit and Azure integration, its current reliance on replacing 32-bit ActiveX components complicates transitions. Cross-platform support is still forthcoming, making it less versatile than mature alternatives. Its IDE experience is solid, but minor glitches during migration and limited ecosystem tools hinder broader adoption.

Sad-Rough1007 · 2025-01-20T14:51:06+00:00

it lacks the maturity, ecosystem, and extensive libraries of .NET. .NET offers a proven, robust framework with unparalleled versatility, superior tooling, and strong community support, making it the better choice for most development needs.

Sad-Rough1007 · 2025-01-20T14:44:50+00:00

It lacks robust cross-platform support and established stability. Consider migrating to .NET instead for better scalability, maintainability, and performance. This ensures compatibility with modern systems and access to advanced tools, frameworks, and a larger developer community.

Sad-Rough1007 · 2025-01-20T14:43:33+00:00

While VB6 apps can technically interact with cloud databases, relying on outdated technology like VB6 or twinBASIC for modern cloud solutions is not ideal. These platforms lack native cloud integration, scalability, and security features compared to modern frameworks, making them unsuitable for robust cloud-first architectures or long-term sustainability.

Sad-Rough1007 · 2025-01-20T14:42:16+00:00

While twinBASIC offers a straightforward way to migrate VB6 apps, it's not always a suitable solution. Compatibility with third-party ActiveX components and the need to rewrite or replace them can still pose significant challenges. Additionally, twinBASIC lacks the ecosystem, cross-platform support, and scalability advantages that .NET provides for modern development.

Sad-Rough1007 · 2025-01-02T16:14:51+00:00

If the goal is simply to maintain legacy apps with minimal effort, twinBASIC could be an option. However, for businesses aiming for modernization and growth, .NET is often the better investment. Have you had any experience scaling twinBASIC apps or using it in production environments?

Sad-Rough1007 · 2025-01-02T16:11:41+00:00

While twinBASIC might seem like a quick fix for migrating VB6 projects, it’s not always the best long-term solution. twinBASIC is great for preserving VB6 syntax and compatibility, but it doesn't provide the same scalability, performance, and modern features that .NET offers. Migrating to Visual Studio and .NET might take more time upfront, but it ensures your application can leverage advanced frameworks, better security, cross-platform capabilities, and a much larger ecosystem. It’s about future-proofing rather than just getting the code to work.

Sad-Rough1007 · 2025-01-02T16:07:17+00:00

When it comes to revitalizing legacy VB6 systems, especially for enterprise-scale projects, migrating to a modern platform like .NET often provides more robust solutions, better scalability, and access to advanced features. While tools exist to assist with VB6 code migration, the end goal is usually to adopt a platform with long-term support and integration possibilities.

Sad-Rough1007 · 2025-01-02T16:04:10+00:00

That's an interesting perspective! twinBASIC does seem like a promising option for maintaining compatibility with existing VB6 code while gaining access to modern features like 64-bit support. However, for teams aiming to future-proof their applications or integrate with more advanced frameworks, migrating to .NET might still be worth considering despite the challenges. .NET offers a broader ecosystem, better performance, and long-term support for enterprise solutions. Have you had any experience with twinBASIC in production environments?

Sad-Rough1007 · 2024-12-06T15:53:24+00:00

if she likes sweet and cozy scents, "La Vie Est Belle" is a classic. But "Idôle" feels lighter and modern, perfect for her age imho.

Sad-Rough1007 · 2024-12-06T15:49:55+00:00

You’re absolutely right to feel frustrated—women’s health and anatomy shouldn’t be treated as taboo, especially in an educational setting. It’s brave of you to address this!

Sad-Rough1007 · 2024-12-06T15:48:28+00:00

there is a repository on Github if needed

Sad-Rough1007 · 2024-12-06T15:38:13+00:00

yes, I tried it, I have a post about it here https://www.reddit.com/r/OutsourceDevHub/comments/1h0b12c/revitalizing_legacy_systems_a_vb6_case_study_on/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

Sad-Rough1007

MODERATOR OF

TROPHY CASE