ASP.NET Room for Improvement
Whenever I don't know how to fix some critical issues, the Microsoft support team always gives us some good guidance and we follow it. When it comes to the application simulation and whether we think it should be added into the latest Microsoft released technology or not, we get everything we need. The only thing is they need to up their new technology and to revamp or migrate our current or existing applications into the latest version, and it should fix the current issues. But it's not me as a developer who can simply buy or implement the tool. Its edition should come from the management, which is not that easy. We only can propose that we get better features in the latest ASP.NET technology, and our higher reporting managers were keen to emphasize that it might take some time. We use the latest technologies that will be implemented with my current applications. We just sample it.
With ASP.NET there are pros and cons. The main pro is that it's very easy and we have Microsoft helping to stabilize the product which is coming with the all new features every year. It does improve the product. But the con is that every year they are launching a new technology, and for a company like us, we get confused about which version should be used.
Let's say we started using the next version, then the next year the version is no longer supported or it got upgraded to the new one. It's not that easy to migrate that entire software to that new version so they have a challenge here. I would hope when Microsoft releases any new products, they would release at least once in five years, and they need to give all the features for that version together. Not like now, when every edition they launch is a new product with the next version and entirely change that Framework. This is not advisable, because when we deal with the project, the size matters and the application usually also matters. Because if all projects are in one year, and you started working on the next version and we were going to launch that software the next year, that version has changed. It's very tough to migrate the entire one year project to the next version. So this is the challenge.
Unemployed at a manufacturing company with 501-1,000 employees
The areas in need of improvement will vary based on the environment and what it is that you are working on.
Performance is an area that can always be improved. For example, when you are doing invoice processing, you want to make sure that they can run at a faster rate. In terms of claims processing for an insurance company, you want to make sure that they have an increased rate of productivity.
I would like to see a summary or list of key concepts that are available. It should include a list of challenges that people are having, and some of the solutions that can help to solve them.View full review »
Following can be improved:
1. VS IDE should be license free so that community edition interactions can be enhanced
2. Undefined Application Architecture with lack of Separation of Concerns (SoC)
3. Lack of abstraction with least control over HTML.
4. Limited support for testing and SEO.View full review »
Associate Technical Architect at a tech services company with 1,001-5,000 employees
In the future, I would like to see more AI and machine learning technologies made available in libraries.
It would be helpful if they supplied templates or boilerplate code for the microservices architecture that would assist people in starting to build software.
ASP.NET does not support Apple or macOS devices.View full review »
I am sure there is something that has room for improvement but nothing specific comes to mind.View full review »