Use of VC++ to create a DLL/Application monitoring/logging system. All actions/communications into a user specified DLL/Application and between the DLL/Application, the Kernel, and other applications must be logged. This includes logging of data sent and recieved over a network by the application, and data stored internally at various phases of the application's run. The emphasis is less on the typical Window to Window communications, resizing, draw events, etc. and more on creating a tool to really understand what the DLL/Application is doing.
Filter (inclusive/exclusive) and trigger functions must also be included, along with a user-interface allowing to specify log output location, filter information, trigger information, and application to target.
The filter capability will allow users to narrow down to log only those specific events they're interested in, by event type (data stored, function call, function results/returned, network communications etc) and by keywords.
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):
a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.
b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).
Windows platforms of various types