Magic xpa Application Platform vs. .NET

In our experience, the product performs really well when interfacing systems with ERP's through SQL server database tables, but we've even made some interfaces with the web service functionality included with the magic xpi integration platform. Also, we've made some SAP Business One - SAP Business One interfaces, for copying information from one company to another and even between two different ERP systems.

Incentivized

If you need to build anything from a quick-and-dirty GUI utility to a full-fledged desktop application, .NET is the way to go. It doesn't require extensive knowledge of the languages as Visual Studio is extremely helpful in its autocomplete, refactoring, and prompts, and lets you build out your solution easily without worrying about the details of [the] setup and boilerplate.

Incentivized

• The UI is really simple to use, you have source/destination mapping for the items.
• The scheduler gives you a lot of options when executing the models.
• The error handling is usually pretty good and the errors can be corrected fast.

Incentivized

• Visual Studio is one of the best IDEs and .NET is the best framework to use with Visual Studio.
• There is a large network of support for the .NET framework.
• The .NET framework encompasses a very large area of the programming stack.
• The .NET framework is flexible and can be used for desktop applications or web development.

Incentivized

• Although the scenarios may be online, the main service usually freezes and the processes can't transact any data. With a single restart of the service, the processes will be functioning again.
• The support for more applications would be nice, even though there is a nice number of them. Most of the main applications in the market are supported.
• The licensing for the software may be a little confusing; you can't buy individual licenses as they come in packages of four.

Incentivized

• .NET is heavily Microsoft Windows oriented, and while .NET core tried to resolve that with MacOS and Linux support, .NET Core is still waiting for wider adoption.
• While free for small projects, additional features for big projects can be a little expensive.
• Can be resource-heavy upon deployment. We continuously have our more senior staff optimize the code of our junior developers for performance. Other languages are a little bit more forgiving in comparison.

Incentivized

.NET frameworks are fantastic overall. There are no limitations to what you can accomplish with it. The most important part is that you'll have access to developer community support and that .NET is always being improved every month. Be it in web applications, back-end servers, or integrations, .NET enables developers to do it all.

Incentivized

As Microsoft Gold Partners, we do have access to a lot of additional information and support from Microsoft. Still, the availability of "open and free" documentation, community, and enthusiasts of the platform is vast. Added to that, the quality of resources provided for all the Microsoft ecosystem is very impressive.

Incentivized

Honestly, we have only used and evaluated magic xpi/xpa platforms because of the recommendation of our SAP Business One main supplier, who has previously used the platform for their developments. So far, we have no regrets with the acquisition of the platform and we are very happy with its performance.

Incentivized

If it was up to me, I'd rather use something like Node.js hands down. Things are simpler, there is no gigantic convoluted class hierarchy to learn like there is with .NET. Also Node is really fast and lightweight. I find .NET these days to be a totally solid product and it certainly has its place - but it seems a bit dated and boring to me now.

Incentivized

• The implementation time for this kind of projects has been greatly reduced.
• Certifying an In-House resource in the Magix xpi and xpa platforms is probably the best option, considering all of the projects that can be developed in the future without the need of an external consultant.
• The processes that have been automatized with the Magic xpi platform helped reduce human error and the time those processes took to finish.

Incentivized

• 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.

Incentivized