Adapt applications at the speed of business with .NET
September 23, 2020

Adapt applications at the speed of business with .NET

Anonymous | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with .NET

Our organization has used .NET extensively for many years. We have created and implemented countless applications for both our internal and external customers. Virtually every user in the company is using a .NET application we've built, at least once per day if not all day.

We have started to create applications built on .NET Core, which gives us the flexibility to build applications that will run on any platform.
  • The most helpful aspect of .NET is the large user community. I have on numerous occasions put out a question about a problem I was having and was helped by at least one .NET developer from the community.
  • With .NET Core becoming more mature, it has helped us build our applications to be able to run on any platform without doing too much extra work. Our internal customers have not asked for this but we anticipate that they will and .NET Core allows us to be ready for that.
  • As our applications develop over time and business needs change, .NET has proven that it remains stable for backwards compatibility.
  • We've found that depending on the type of application that you're developing, resource usage can be high at times. This is something that we've needed to keep in mind especially during peak usage of our applications.
  • We've found that dependency management can be an issue at times. This has messed up our builds once in a while.
  • Better and real-world online examples of new methods and classes would be beneficial.
  • We are slowly switching from a dying programming language to .NET because it was too expensive to hire developers for the old programming language. There are way more .NET developers around and an amazing community which has allowed us to keep our costs low.
  • Our development time has been greatly reduced because now we're not developing applications for each OS platform. We do it once and deploy accordingly.
  • .NET Core has been a big mindshift in terms of how to program. The learning curve has been quite high for existing .NET developers.
We are currently moving away from Visual LANSA as it does not do well on the web. Developers are hard to find for this language while .NET developers are readily available and very knowledgeable.

By switching to .NET, our development time has been cut down and has become more robust with automated testing, builds, and deployments.
Customer support has been amazing. .NET has an amazing online community that is very supportive. The abundance of .NET developers online as well as in the office has sped up our time to market.

When we have a problem and need to submit a ticket to Microsoft, their support has been extremely helpful and prompt.
The full .NET Framework is an amazing thing and is very robust. We have used it to create console apps, Windows apps, and online apps.

When coupled with Visual Studio, development, testing, building, and deploying our applications has become 100 times easier as compared to doing those things manually before.

The automation of this process has helped us push out changes to our applications faster to adapt to the ever-changing business requirements.

Do you think .NET delivers good value for the price?


Are you happy with .NET's feature set?


Did .NET live up to sales and marketing promises?


Did implementation of .NET go as expected?


Would you buy .NET again?


One of our business requirements was to have field workers use their tablets to gather information. They may or may not be connected to the internet. Our .NET application allowed us to create this application and retain the data locally until they got back to the office to upload the data to a central server. The tablets were Android- and iOS-based so writing an application one time with .NET Core helped us out immensely.