Situation
An automotive aftermarket business still ran a VB6 application that had to work with a newer website, and the website itself had performance problems.
Past engagement · .NET applications
VB6, AngularJS, and WebAPI in the automotive aftermarket
Past .NET work at Fisher Auto Parts: a VB6 application bridged to the web, and an AngularJS and WebAPI path aimed at replacing it.
Past engagement · Fisher Auto Parts · 2015–2016
Past engagement, not a current employer.Named for the kind of work. This page does not add a percentage, a dollar figure, or a result that was not in the record of the work.
Outcome
The VB6 application was integrated with the site through a Chromium bridge into .NET. An AngularJS and WebAPI application was designed to replace the VB6 programs. The engagement ended in February 2016.
From June 2015 to February 2016 Jon did .NET and AngularJS work at Fisher Auto Parts in Staunton, Virginia. That employment is finished.
The existing VB6 application had to work with a newly developed website. A Chromium-based bridge was the integration point between VB6 and .NET. Performance problems on the VB.NET site were traced through redundant calls in the user path, not by rewriting the site on a guess. Alongside that, an AngularJS and WebAPI application was architected to replace the VB6 programs.
This is the automotive-aftermarket shape of a .NET project: the old client is still in the building, the web stack is already chosen, and the work is the bridge plus a replacement that can actually be finished. It is not a staff-augmentation order, and Fisher is not a current client.
Related practice: .NET applications
Other examples
- Curio — iOS development
- Siebel 7.8 to IP2014, with Open UI and AWS environments — Siebel CRM
- Public Sector case management for a state attorney general — Siebel CRM
- Siebel membership pricing, then .NET, WCF, and SharePoint — Siebel CRM
- Two Siebel views, one order — Siebel CRM
- The billing app only one person could change — .NET applications
- Drafts beside the CRM, not a new system of record — AI consulting
If the system matters and the team is small, start with a conversation.
A paragraph on the system, the constraint, and the timing is enough. Jon reads these. There is no intake desk.