We have built an Outlook Plugin that listens for incoming and outgoing email and based on certain rules posts them to a Web Service.? This plugin has approximately 14,000 lines of code.? This Plugin is code complete but we’ve had a number of issues with the software hanging Outlook. While we can fix these issues as we find them, we’d prefer to avoid them entirely.? As a result, we’re looking for an Outlook Plugin and Visual C++ expert to review our code, make suggestions on improvements and best practices, and help us avoid potential pitfalls that would not allow us to scale this plugin to multiple versions of Outlook and multiple versions of Windows.
We would demonstrate the application and answer any questions. ? We would expect this would take an hour or less.
Provide a detailed code review of existing code base with suggestions, specific examples of code, and potential issues in the following areas:
• Outlook Plugin best practices as far as project setup, use of appropriate application libraries, and tools. ? Are we using current appropriate libraries? What do we need to do differently for different Outlook Versions, OS Versions etc?
• Details on how to instrument the code appropriately to log all errors and exceptions at each potential hot point in the application. ? We’d like to be able to see the exception, line number, current application data, and details when problems occur. ? We want to be able to turn detailed logging on and off easily, and have a good trace of exactly what was happening when errors or faults occur in the application.
• Provide a document that details findings on the items above and provides specific instructions on how to either fix the code, achieve the required level of logging, etc.
**Team Walk Through**
After delivering the document, have a 1-2 hour session with the team on our end to explain the findings and essentially provide a knowledge handoff on the delivered document. ? Would be able to answer the questions the team has and potentially follow up with additional code action items and/or questions.
After our team has implemented the suggested changes, we would like a second review of the code base to verify the suggested changes have been completed accurately and correctly.