Microsoft .NET Framework Reviews

Our development tools, our platform, every solution we've developed, most of them are Microsoft products. So we're using .NET. 

Almost all of our enterprise applications are developed within that whether it will be reading those applications, web applications, or a background service, etc. Of course, there's a different case when it comes to our mobile application. We're quite open-minded and like to explore other frameworks due to the fact that there has been a lot of frameworks getting more popular nowadays.

I have very diverse experiences in most of the major programming frameworks, whether it is DHP, Java, etc.

Basically, .NET is simply is the easiest programming language to use, based on my experience. It has flaws, however, the performance and agility are much better compared to other programming languages.

They've done a lot in the past few years. You can see this especially in the fact that they allowed .NET to be run in Linux environments.

For .NET, what I can say is that maybe it needs adaptation of a more streamlined function. What we can see is vital is a simple programming model. However, .NET Is still heavy or dependant on other Microsoft libraries and frameworks. Therefore, although they're going there, they're already open-source for that network. There are lots of improvements that can be done there within that industry.

For example, .NET support needs to offer big data similar to Mongo DB or to the other big data technologies. It's still in its infancy from I've experienced. When it comes to the big data or data science fields, I think .NET framework has a lot of things to hash out.

Another item worth improving in .NET is support to Mac. There's still a lot of grey areas when you use a Mac. There's a lot of instability when it comes to that OS. .NET programming language will be very difficult to compete with when they fully jump into the Apple territory.

I've been dealing with the solution for probably more than ten years. I've been using .NET since the beginning when it was .NET 1.0. Therefore, I believe it's been more than a decade.

The solution is stable. Aside from issues surrounding using Macs, it's not too glitchy. It doesn't freeze. It's pretty reliable.

The biggest problem with programming language nowadays, because there are a lot of things happening, is that changes happen too fast. Due to the competition, they tend to release new features almost every week. I don't think there's an exception on that one. In return, the application framework can have bugs in it. 

Nowadays when it comes to scalability performance, it's in the hand of the programmers. It's not in the framework. Even if you're using a very efficient or powerful framework, if that application was developed improperly, it just makes everything else shakey. If the framework is there to help you to do the best practices and apply everything, .NET is still really good at doing that, compared to other frameworks. Almost everything is bootstrapped or is ready for you to use, unlike other frameworks like Java. You have to develop everything to make sure that it is able to address the issues. In .NET it's pretty straightforward.

If we contacted technical support it may have been a long time ago. Nowadays, it's rare to go directly to support. For the most part, all you need to do is Google your queries and you can find the answers yourself.

The tool itself, in terms of the initial implementation, is pretty straightforward. The tool will do everything for you, unlike other programming languages where you have to install these different dependencies, et cetera. 

We're just a customer.

We use multiple deployment models. I'm using Azure Dev Ops for my previous projects, but for my company, we're using Jenkins to deploy our applications.

The good thing with the .NET framework is that it allows you to develop an application faster and in a professional way. The downside is that it's different due to the fact that it's abstract. It's different from every other program. You really need to know the fundamentals of software development. That's the downside. Using .NET You will be able to develop many applications without really knowing what the inner workings of that application are. Compared to Java, or C++ where you should be able to know every fundamental of every foundation, you don't need that deep knowledge with .NET. If there will be a trainee or entry-level person on the program, I suggest they study first computer programming fundamentals, maybe in Java or another more engineering-oriented programming language before they go deeper into the .NET framework. Or they should at least do their homework to learn those things.

Overall, I'd rate the solution eight out of ten. If they slowed down a bit with the new releases and made sure they were bug-free before releasing them, I might rate it higher.

Our primary use case is custom business applications, Integration services using WCF/Web API.

Using this framework has enabled us to create services out of things things that we used to do manually. Not only has it made our lives easier, but it has increased productivity as well.

The most valuable features for us are web frameworks like MVC, Web API, and WCF.

I would like to see more pre-built features in the MVC framework because as it is now, it's very open and you have to develop your own controls in order to use it. It would be much easier for us if there were more pre-built controls.

There should be more security features included.

The performance should be improved.

The technical support is in need of improvement to make solving issues more efficient.

I have been using the Microsoft .NET Framework for more than 16 years.

This is a very stable solution and we haven't had any issues.

This is a scalable framework but it depends on how you deploy the solution. Because it is a framework and not a product, it will give you options on how to develop your solution. If you develop it in a way that is scalable, then it will be scalable. But if you don't develop it properly then it will not be scalable.

In my previous company, we had approximately ten thousand users.

In my current company, we only use this solution internally. We have fewer than ten people, and they are business users. We do not currently have plans to increase usage but it may happen in the future.

On a scale from one to ten, I would rate Microsoft technical support a seven.

Whenever we are trying to solve issues by dealing with Microsoft, they ask so many irrelevant questions that it delays things.

We are also using WebLogic Suite with SharePoint on the server-side.

The initial setup was straightforward and the deployment took not more than two to three days.

We implemented this solution using our in-house team.

The Microsoft .NET Framework is free of charge, without licensing cost. The only cost is purchasing the hardware that it runs on.

Java SDK. Java SDK is also good but require little bit more effort.

My advice for anybody who wants to use the Microsoft .NET Framework is to have the proper foundation before implementing the solution. This means that they should lay the architecture first, properly, and then develop the solution based on the architecture. Without this, the solution will not be scalable and will suffer from problems in the long run.

This is a good solution but there is always room for improvement.

I would rate this solution a nine out of ten.

Our primary use case is generally for clients that are enterprise-sized businesses like insurance companies or bit telecom companies in the US. They are generally the customers that use this solution and my company provides services to them. Our work is related to putting the solution together and implementing the whole thing end to end. A lot of companies are moving towards the cloud, so either it's AWS or Azure or Google. Google is not as popular as AWS, followed by Microsoft Azure. And of course there are a lot of products on Microsoft which are also popular like their database and of course the Windows server and things like that.

We're a partner of Microsoft and I'm the associate director of our company.

The most valuable features are the customization and the support moving towards a .Net framework.

Nothing in particular comes to mind in terms of improvement. It's a proven solution and it really depends on the resources that a company has for maintenance once a solution is in place. That said, it would be good if auto-scaling could be included. I also believe implementation could be simplified.

Microsoft has got a lot of products and improvements would be in the context of a particular product. I've seen there are areas that are much harder to capture - so things like auto scaling and implementation could be improved. 

I've been using this solution for three or four years. 

It's a stable solution. 

It's a scalable solution. 

The technical support is good and they also have some community forums where people can get quick responses to some of the queries that they have. So the community is good.

I"ve used Java previously and find it a more portable solution. 

Initial setup is somewhat complex and requires some training. I would say that Microsoft can  improve on that somewhat in terms of enabling someone to understand the process and set it up themselves.

I would definitely recommend that anyone considering implementing the solution do a proof of concept. That gives you an idea as to whether you're on the right path. A company also needs to take into account the requirements of their organization in terms of scalability and ease of maintenance and also whether they have the skill set to maintain the IT resources required. A lot goes into it but proof of concept would be good before going ahead.

I would rate this product an eight out of 10. 

We primarily use the solution as a self-check-in tool for customers for a number of hotels.

The ability to incorporate the customers is the solution's most valuable aspect.

The pricing and support have room for improvement. The pricing is too high currently. We are thinking about the pricing from the end customer's perspective.

I've been using the solution for around three years.

I'd rate the solution as highly stable.

The solution offers good scalability capabilities. There are tens of thousands of end-users on the solution currently.

I've never been directly in touch with Microsoft's technical support team. My team has been, however, and I'd say, according to them, they are quite responsive.

We did previously use a different solution. We switched because of the lack of quality within the other solution. The way Microsoft adapted to the corporate customers, offered stability and scalability, and also the quality of support were some of the reasons we switched.

The initial setup is not straightforward. It's complex. Typically, deployment takes one year.

I handled the implementation myself with the assistance of my team.

The pricing is a bit expensive.

We did evaluate other options. We looked at both Java and PHP.

We are official partners and we are sellers for UiPath. For Microsoft, however, we're just customers.

I'm not sure which version of the solution we're currently using.

I'd advise others to find a solution that is suitable to the customer's needs and to examine the customer's business case before deploying anything. In our case, this solution was something that is a bit more expensive. However, it's of the highest caliber and it's stable. In this scenario, it made sense for us to choose Microsoft.

I'd recommend the solution to others serving a similar type of customer.

I'd rate the solution eight out of ten.

We are part of the development team.

We use this solution with TFS as our ALM tool, and we use the information server for the deployment.

We have been using this solution for development for a long time and it has proven to be helpful.

The .NET framework is a mature platform that is very helpful and saves time during the software development process.

The IDE is quite helpful.

There is a lot of very extensive documentation available.

The price of the Enterprise version is quite high and can be improved. If Microsoft would provide a monthly subscription at a cost that a developer can afford then it would be really helpful.

From a security standpoint, the tools are not that mature.

I have been using the Microsoft .NET Framework for more than 25 years.

This is a very stable platform for enterprise development. It has been maturing since its inception and is very helpful for delivering products.

We have dealt with the technical support team and they are very helpful. Whenever there are issues, especially when troubleshooting in a production environment, Microsoft and the support people provide a lot of technical expertise and we are very happy with it.

This product is really helpful when compared to other solutions such as open-source platforms. All of the tools are interlinked, rather than having individual tools for individual features. What Microsoft provides is a complete tool, with all of the features contained.

The initial setup is easy. There is a vast amount of resources made available by Microsoft and a lot of guidance being provided to the developers. 

I lead a development team and the team members perform the deployments. There is a lot of guidance available on the Microsoft website that is really good, so the deployments are not troublesome.

There is a Community Edition that can be used free of charge, but the licensing cost for the Enterprise version is quite high. Some of the tools that are available in the Community Edition need a valid license to run.

Compared to other vendors, Microsoft products definitely have a higher price tag. I would say that is my only grievance.

Talking from an application developer's perspective, this platform is very helpful because it provides a common development line across all of the products that Microsoft provides. This includes things like Microsoft Dynamics, the Cloud Integration tool, and SharePoint. It makes it very easy to jump from one application tool to the other.

The Community Edition can be used free of charge and is helpful for both new developers, as well as those who are shifting to the Microsoft platform.

Over time, this product has matured and all of the new features have been helpful in improving the performance of application developers. Overall, we are very satisfied with using this platform for application development. It is very good. That said, there is always room for improvement.

I would rate this solution a nine out of ten.

We are working with version 2019, but we have clients who are still on older versions. We deployed the solution in 2014 or 2015 and they still haven't upgraded.

Cross-platform development is better than all of the other frameworks. When it comes to the user interface, the context is better than other tools because it is easier to use. You can still use C# in the developer infrastructure, which makes it far better and you don't have to learn a new language.

For me, the cost is what is most important. We have an agreement with Microsoft to co-sell some of the applications. When we started developing using the Microsoft Framework, it went well because we started making more money than the cost to Microsoft. We don't have this agreement with Red Hat or JBoss.

One thing that I like is that from the usability point of view, nothing has changed all that much. We use Visual Studio and if you compare the older version of Visual Studio from 2013 to the 2019 edition, the scale is still there. You're not moving to a different environment and you are still able to find your way around very quickly. With the new features, we are still able to feel those out within a short period.

For the mobile application, I like the iOS interface. Android is a little different from what you have on iOS, but the iOS package includes the same thing.

The pricing could be cheaper.

They should have more training materials available that are specific to .NET. We spend a lot of money training our engineers. I think that it would be better if there was more training available to the partners who invest in Microsoft.

At this time, the training is all over the place and there is no specific certification.

This solution is not scalable with older versions without using patches for it to work.

I have been working with this solution for more than ten years.

Microsoft's strategy is not scalable, especially with the Visual Studio environment. If for example, I am testing things from on older version, it's not available in the newer version. You will have to use notes and the patches for it to work.

Currently, we have two enterprises. One of them has over 1000 employees and an IT department with 200 developers.

The technical support has been excellent. If you are working with them, they are always there to connect with you all the way, which makes things so much better.

The first day takes a couple of hours and the second day is for the configuration and switching everything out to make sure that everyone has access to it. Then they test everything to make sure that it is fine and working. It's not a lot of work for us to do.

The support has been very good, maybe because we have a local office with resources.

Some of the issues with support is not with .NET, it's dealing with some of the packages that should offer support. One of the new products that Microsoft has introduced is called Dynamics 365, this is outside of .NET. We have been struggling to find someone for support, but unfortunately, it has to be through the US.

When it comes to everything else, the .NET Framework has a lot of support from the local Office.

If they struggle with .NET there is someone in the UK office that would be able to assist us.

The initial setup is easy for our guys who spend quite a bit of time with Microsoft.

Just today, one of the guys set up an environment for one of our clients on Azure. This was a Visual Studio environment and it took him two hours. He did not encounter any difficulties. 

We have guys take care of the server section and we have our developers that implement from the installation for the environment.

It seems very easy for them to get everything up and running.

Small clients don't do their development internally. We have three of these types of clients. Small to medium-sized organizations don't have an environment because they are easy to develop with easy requirements.

I would recommend this solution but it depends on the environment and what they want to do.

If you do mobile applications, to avoid the headaches of doing development on multiple platforms, I think that .NET is something that really works. We have tried everything, so when we try iOS it becomes a problem because we have to re-develop what you do for Android on iOS, even though we don't use Windows phones anymore. We can still use the same tools for your desktop applications.

If you have a different environment then you have to develop based on whatever application you are going to run your application on. 

I would rate this solution an eight out of ten.

We primarily use this solution for point-of-sale and finances. We also use it for maintaining student information, details about teachers, attendance, and grades.

The most valuable feature is the financial accounting.

This solution should include Power BI so that we don't have to use any third-party tools. Including business intelligence tools would allow for easy understanding and quick decision making. It will help as it is for summarizing all of the business-specific analytics.

We have been using the Microsoft .NET Framework for six years.

The Microsoft .NET Framework is 100% stable. We have to use it for our day-to-day activities. Also, based on the business functionality you have to keep upgrading.

This platform is easy to scale. We have approximately 100 users, five of which are administrators and the remainder are business users.

We have been in touch with Microsoft technical support and we are happy with their work.

Prior to Microsoft .NET, we used Oracle DPK. The problem with DPK is that it is old technology that was used ten or twelve years ago. It has some limitations regarding client-server models.

We switched because .NET is a very flexible framework for enhancements, and it is cost-effective for developers.

The initial setup is easy.

We used consultants for the deployment and we use third-party business intelligence tools for the integration.

We did have the option to go with PHP and Joomla, but we were concerned that it may not be available after a few years. When it comes to Microsoft technology, it is more stable and because they are a giant in technology, .NET will be an everlasting solution for which we can always find developers and support.

This is a product that I recommend.

I would rate this solution a ten out of ten.

I use this solution for infrastructure work and Business Intelligence.

The most valuable features are the Domain Controller and the WBFS Manager.

The integration services allow us to connect to resources like Oracle.

There are certain tools, such as Oracle, that this solution does not integrate well with. The performance is slow and the connection takes a long time. Better integration with other tools to make the operation faster would be an improvement.

I have been using the Microsoft .NET Framework for one year.

There were problems with the older versions of this solution. The newest version is stable, but sometimes you have multiple versions installed and you have to switch between them. You don't always know if you're compiling with the most recent version.

I am the only one who is working with this solution in my company.

I always use the community chat and my experience with it is very good.

The initial setup is easy. Finding services is easy on the service tab. You can install the features that you want to use. It is better than using the Control Panel to add features, which was the old way to do it.

This is a solution that I recommend, but the best versions to have are 3.5 and 4. 

I would rate this solution an eight out of ten.