Technical Upgrades Overview for Partners
We are pleased to unveil the upcoming technological evolutions in SuperOffice versions 11 and 12. Our goal is to ensure that our partners are well-informed and prepared to use these advancements, enhancing both the development experience and the end-user solutions you create.
Technical Enhancements in Version 11
Async/Await Integration: We're fully integrating async/await paradigms across NetServer, enhancing responsiveness and efficiency. This shift helps non-blocking I/O operations, significantly improving the scalability and performance of integrations and custom solutions.
Dependency Injection Adoption: With the implementation of Dependency Injection (DI), we're promoting loose coupling and improved testability within our architecture. This allows for more maintainable code and eases the integration of unit testing, easing a more robust development process for your custom solutions.
Removal of Legacy C++ Code: Transitioning away from C++ to a more modern, unified .NET approach simplifies our stack and reduces complexity. This means a cleaner, more consistent development environment and the elimination of outdated dependencies.
Implications for Version 11 Development
-
Prepare for a significant shift in how you interact with SuperOffice back-end systems, particularly through the enhanced async programming model, needing updates to existing integrations or custom solutions.
-
Plan for adaptations in your development practices to accommodate DI, leading to better separation of concerns and more testable code.
-
Adjust to the removal of C++ components, understanding that all SuperOffice functionalities will now be accessible through a harmonized .NET-based approach.
-
End of life components:
-
-
Reporter and Reporter Studio
-
SoAdmin.exe
-
-
-
Travel Gateway
-
ServerSetup and DbSetup
-
Advancements in Version 12
.NET 8 and ASP.NET Core Transition: By moving to .NET 8 and ASP.NET Core, we're not only embracing the latest in performance, security, and development features but also ensuring cross-platform compatibility, from Windows to Linux and containerized environments.
From WCF to RESTful APIs (Application Programming Interface): Aligning with modern web standards, we're transitioning from Windows Communication Foundation (WCF) to comprehensive RESTful APIs, streamlining data interchange and integration with third-party services. However, ERPSync and Quote connectors will remain as WCF (SOAP) APIs. Database Mirroring will also remain as a WCF-based (SOAP) API.
Authentication and Authorization Modernization: Updating our authentication frameworks to align with current best practices using ClaimsPrincipal, providing more secure and flexible authentication mechanisms that can easily integrate with your existing systems.
What Version 12 Means for Partner Developers
-
Transition any existing onsite solutions, including all plug-ins, away from NetServer packages to SuperOffice.WebApi. NetServer packages will be deprecated in version 12, and all new development must be based solely on REST API's.
-
Transition any existing WCF-based integrations to RESTful APIs, ensuring your solutions stay compatible and take advantage of more standardized, modern communication protocols.
-
Update your security practices in line with the new authentication mechanisms, ensuring that your applications stay secure and integrate seamlessly with SuperOffice's updated security model.
-
No API (Application Programming Interface) plugin support, including sentry, document, archive and MDO providers, etc.
Will this affect me?
As long as your integrations uses the REST APIs (or SuperOffice.WebApi nuget package), your integration should not be affected.
Database mirroring applications are unaffected by the upcoming changes.
We are hosting a webinar that focuses on the breaking changes pertaining to the SOAP proxy client and onsite libraries, SuperOffice.NetServer.Services and SuperOffice.NetServer.Core respectively, as well as other onsite technologies.
Collaborating for Success
We are committed to supporting our developer community through these transitions. In addition to detailed documentation, migration guides, and support to ensure a smooth adaptation process, we look forward to the webinar where you can hear in-detail what our plans are, and get all of your answer questions.