Development Stack and Design Approach

Eighty7 Consulting prefers development technologies that are .NET native or .NET inspired, with an emphasis on cross-platform employment and functionality. We are well experienced in the use of the original .NET Framework, but we prefer and recommend the flexibility and performance of the more modern .NET Core versions when crafting new projects or modernizing a legacy code base.

Indeed, we are experienced creating or maintaining solutions that may be made up of distributed services hosted in a heterogeneous mix of UNIX, Linux, Mac OS and/or Windows operating systems -- in the cloud, on premise, or hybrid environments.

For the creation of new or maintenance of existing web based solutions, we are experienced on the use of ASP.NET MVC projects as well as Blazor Server-rendered applications. We have some experience and training with Angular's JavaScript Framework, and actively pursuing competency with React library. We are also experienced with other technologies and may support code bases that use ASP.NET WebForms, IIS ISAPI extensions or websites that may have been written with only HTML CSS and make use of jQuery for client side scripting and Ajax functionality.

We like desktop development on Windows, Mac OS and Linux, and we make that possible by creating rich client applications that behave and feel native thanks to cross-platform UI frameworks, but may also opt for native UI frameworks if requirements specify it. We also create character based or command line friendly user interfaces as remote terminal applications and shell scripts often play a role in enterprise software development.

As a design guideline and best practices, we make extensive use of layering and creating library assemblies that are then packaged as NuGet packages. This modular approach facilitates code sharing, reuse, and separation of concerns.

Therefore, in those few exceptions when a homogeneous cross-platform UI framework cannot be used, the final solution still benefits from a common code base for data and business logic layers shared by all client applications -- even if more than one implementation of the UI layer must be provided per client type.