With the technical stacks, what happened is that Microsoft evolved in such a way that the features that are available in other technologies were gradually incorporated into .NET or C# for any Microsoft technical areas, whether it is Azure or any other tech stack. So it's gradually happening. We already have some Power Apps and so on. At this moment, Power Apps is restricted within Azure or any kind of Microsoft environment. Such things in the future should be .NET Core. It should be open source or deployable to any operating system so that the dependency can be removed. And with a click, we can get a solution ready for deployment.
Full Stack Developer at a outsourcing company with 5,001-10,000 employees
Real User
Top 10
2023-01-05T13:23:39Z
Jan 5, 2023
It would be beneficial if Microsoft provided more support for certain technologies, such as Blazor, in the form of basic components. As it stands, some reliance on third-party tools may be necessary. Having more support from Microsoft for these technologies would make it easier for users to build and maintain applications. For example, the grids, date pickers, and dropdown lists would be components to add.
The solution needs to support its framework on all devices used for mobile application development. For example, development on an Android device requires use of Xamarin and that adds a level of difficulty.
Scripted languages like AngularJS and Node.js are much faster than using ASP on the client side. We created server-side code in ASP based on client-side code but questions that hit the server took time to render as they searched the data. Node.js includes client-assisting languages that speed up the process.
I am not familiar with ASP. That's why I'm not sure which scenarios will see an increase. I don't use ASP very often. That's why I'm not sure what additional features would be of assistance to users. I am only using ASP to generate the APIs. You are required to have knowledge of C#.
There is room for improvement with the interface. It is not very fast at times. For example, when you click on something, it can lag a bit. That sort of waiting can be very boring when you are just trying to carry out an easy transaction.
Unemployed at a manufacturing company with 501-1,000 employees
Real User
2020-09-27T04:09:52Z
Sep 27, 2020
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.
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.
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.
COE Head - Emerging Technologies & Global Practice Lead - Digital Transformations at Tata Technologies
Real User
2020-02-10T07:39:02Z
Feb 10, 2020
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.
Although ASP.NET is a full package for any sort of development, whether be it in web or mobile, each part has been covered well enough but there is always room for improvement. I am pretty sure that Microsoft is working in the same direction to ease the pain of developers. I won't point out anything but I am going to enjoy the fact that it's pretty cool to solve something on our own rather than just complaining about something which we haven't tried. However, who said it's going to be easy, but nobody said it's impossible. The most important thing to improve in the next release would be support in tooling and high-level designer toolbox for cross-platform mobile app development.
ASP.NET is a very slow tool, and it should be faster.
With the technical stacks, what happened is that Microsoft evolved in such a way that the features that are available in other technologies were gradually incorporated into .NET or C# for any Microsoft technical areas, whether it is Azure or any other tech stack. So it's gradually happening. We already have some Power Apps and so on. At this moment, Power Apps is restricted within Azure or any kind of Microsoft environment. Such things in the future should be .NET Core. It should be open source or deployable to any operating system so that the dependency can be removed. And with a click, we can get a solution ready for deployment.
The solution is out of date and should not be used.
In my opinion, this solution should improve their web toolkit.
It would be beneficial if Microsoft provided more support for certain technologies, such as Blazor, in the form of basic components. As it stands, some reliance on third-party tools may be necessary. Having more support from Microsoft for these technologies would make it easier for users to build and maintain applications. For example, the grids, date pickers, and dropdown lists would be components to add.
We haven't had any issues with the product. It could use better reporting and documentation.
An area for improvement is the structure template.
The solution needs to support its framework on all devices used for mobile application development. For example, development on an Android device requires use of Xamarin and that adds a level of difficulty.
Scripted languages like AngularJS and Node.js are much faster than using ASP on the client side. We created server-side code in ASP based on client-side code but questions that hit the server took time to render as they searched the data. Node.js includes client-assisting languages that speed up the process.
I am not familiar with ASP. That's why I'm not sure which scenarios will see an increase. I don't use ASP very often. That's why I'm not sure what additional features would be of assistance to users. I am only using ASP to generate the APIs. You are required to have knowledge of C#.
The technology to integrate with cloud information could be improved.
There is room for improvement with the interface. It is not very fast at times. For example, when you click on something, it can lag a bit. That sort of waiting can be very boring when you are just trying to carry out an easy transaction.
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.
I am sure there is something that has room for improvement but nothing specific comes to mind.
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.
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.
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.
Although ASP.NET is a full package for any sort of development, whether be it in web or mobile, each part has been covered well enough but there is always room for improvement. I am pretty sure that Microsoft is working in the same direction to ease the pain of developers. I won't point out anything but I am going to enjoy the fact that it's pretty cool to solve something on our own rather than just complaining about something which we haven't tried. However, who said it's going to be easy, but nobody said it's impossible. The most important thing to improve in the next release would be support in tooling and high-level designer toolbox for cross-platform mobile app development.