Azure App Service vs. ComponentOne

You may easily deploy your apps to Azure App Service if they were written in Visual Studio IDE (typically.NET applications). With a few clicks of the mouse, you may already deploy your application to a remote server using the Visual Studio IDE. As a result of the portal's bulk and complexity, I propose Heroku for less-experienced developers.

Incentivized

C1 is great for creating custom reports. We have client apps where we've created some fairly complicated reports such as invoices and real estate inspections. We also use the True DBGrid in many of our apps since it is so customizable. Its grouping and filtering features are very nice and can provide summary counts and totals at the bottom or right side of the grid that are very handy.

Incentivized

• Extremely easy to deploy and update from Visual Studio
• It integrates seamlessly with other Azure PaaS resources
• It has an in-depth integration with AppInsights, so you can understand errors and their root cause easily.
• Easy to create and delete, what is not the same case in a IaaS resource
• It escalates based on CPU workload and some other resource variables.
• Configuration changes are almost immediate
• Offers an excellent abstraction from hardware backend of the platform
• That's updated very often, saving time and the risk of a self-performed update over a IaaS
• That's really easy to develop for Web Apps
• It supports Function Apps and Web Apps into the same "cost black box"

Incentivized

• The True DBGrid control is nice for showing parent/child relationships and being able to drill down and show the child data. It also is nice for showing summary totals.
• The report engine is great for building custom reports for Win Forms or web apps. It can do everything that Crystal Reports can do.
• They have a good selection of controls that can do just about anything you can imagine.

Incentivized

• Jumps between resource sizes can get expensive
• You may wind up putting a lot of eggs in one basket--not necessarily a con but something to keep in mind (most of your data will likely be managed and processed through Microsoft products/services if you fully commit to Azure App Service).
• Learning new technology. If you're moving from on-premises to Azure App Service (or any cloud solutions), you'll likely have to rethink how things are done to achieve the same end results (and/or resources may become expensive quickly).

Incentivized

• Sometimes it is difficult to figure out where things are in the properties of controls since there are so many things you can drill down into.
• I find myself using Bing or Google a lot to look up how to do something. Some things are not very intuitive.
• Of course, I would always like the price to be cheaper. The high price has caused us to not keep current and have the latest version.

Incentivized

I have given this rating because Azure App Service performs very well in terms of speed, reliability, and reducing overhead, and improves overall team productivity, with a little scope for improvement in complex testing scenarios and configurations, scalability concerns in a large setup, and similar tracking and audit needs.

Incentivized

Microsoft has always been known for providing a high standard in terms of customer support and Azure App Service (and as a matter of fact the whole Azure Platform) is no exception. Azure App Service never caused us any issues and we only contacted their customer support for questions regarding server locations and pricing. I feel pretty satisfied with how they treat their customers.

Incentivized

When we chose it, we did so because of its integration with Microsoft applications; now we need to integrate with AI, and Azure doesn't offer a good integration. That is the main reason to change it. It is still great to develop Windows- and Microsoft-based applications, but if we need to integrate with AI, Google wins by far.

Incentivized

We have been in business since 1992, so we have used many different products over the years. The two other products we've primary used that are similar to ComponentOne, are Infragistics and Crystal Reports. Infragistics has a vast array of controls similar to ComponentOne. We use both to be honest and I'm not sure which one I would pick over the other. I guess that would depend on what you're trying to accomplish and if one had some control or capability that the other didn't. ComponentOne does have the reporting capabilities, where Infragistics does not.

Incentivized

• Deployment of ASP.NET apps at the organization has been sped up.
• An option to offer access to the version control system on a third platform so that we could easily deploy our apps.
• Because of Azure App Service's scalability capabilities, the costs of running the services are kept to a minimum. As a result, we may save hundreds of dollars each month compared to the expenses of traditional servers by using fewer resources during slack periods.

Incentivized

• ComponentOne allows us to add additional features to our apps that wouldn't be found in apps written with just Visual Studio itself. That allows our clients to get more creative in their requirements, which in turn, means more work and billable hours for us!
• Our apps appear more professional when using ComponentOne which helps us get projects for new clients.
• ComponentOne also helps us to save clients some money since we are not having to develop things that it can do from scratch.

Incentivized