Authorization had to continue to work as usual, all previously-issued API tokens had to remain valid, and all routes and data structures had to stay the same, even when we were implementing completely different solutions to achieve the same results. Our team made it their mission to ensure that all public APIs and the 7pace Timetracker user experience remained constant and unchanged throughout the conversion process.
#7PACE TIMETRACKER REGISTRATION#
After switching to a common registration pattern and a more obvious call order, each part of the request would now be more easily controlled by us at 7pace. Everything – OAuth for authentication and authorization, API versioning, routing, SignalR connectivity and more – had to be re-written and transformed from an in-house solution to an open-source, fully-supported, well-documented, secure and configurable solution from the.
Tackling 7pace Timetracker business logic would be the easy part (with most of the work focusing on changing project targets and fixing references), while updating the web application (that included the most legacy code) itself would be the most challenging.Īll of the above was moved to our middleware. NET Core would take time, trial and error – and patience! – so, they got to work. NET Core”, it wasn’t quite as easy as just flipping a switch! Our devs anticipated that the process of updating 7pace Timetracker to. When we pronounced earlier that we “switched to. NET framework, our team knew the time to make the switch to “the most loved” framework had come.
With a lot of third-party packages suspending support of (or never having had support in the first place) the. NET Core is a free, open-source cross-platform framework from Microsoft used to create server applications that run on Windows, Linux, macOS, and mobile devices (via Xamarin). Well, if you’ve been living under a proverbial rock (or perhaps been in quarantine long before it was necessary!), in a nutshell.
#7PACE TIMETRACKER UPDATE#
Since then, a lot has changed, and at 7pace, we pride ourselves on being adaptive to and on top of not only time tracking, but time changing! So, our team has been working hard behind-the-scenes to not only bring you 7pace for GitHub (currently in beta testing) but to also update our existing systems to. When 7pace Timetracker officially launched in 2012, the ASP.NET MVC 3 framework was an obvious choice for us to work with. We’re stoked to share that we’ve made the switch to. For the first time in our history, 7pace Timetracker is no longer running in a Windows-exclusive environment.
0 kommentar(er)
