CodeWright Extension DLL using ATL/WTL

Environment: VC6 SP4, NT4 SP3, CodeWright Editor

There used to be a sample of an MFC extension for CodeWright on the Premia Web Site. This one is similar but uses ATL/WTL instead. This DLL was initially created with the ATL Wizard (aren't they all).

The stdafx header pulls in a bunch of ATL and WTL headers and doesn't really use them at all (yet). You'll be able to tune them out as you go.

Look for variables and names with 'atl_test'-- they probably have to be revised as further clones are taken of this arrangement.

I have removed almost all COM server support--most COM client functions should work since the caller must call ole initialize. CodeWright??

I use events a lot so there is a general handler for them. I also use the dinkumware version of the libraries ( you may not, the standard ones should work okay ).

Note--exports.h header must be hacked if you include it (you'll probably need to. The hacked version leaves out StrTrim because shlwapi.h has hogged that name already!!

The most convenient way to hack on this is to use the Brief keymap and to use F9/shift-F9 to load/unload the DLL and F10 to exec functions.

Downloads

Download demo project - 54 Kb


Comments

  • There are no comments yet. Be the first to comment!

Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • Complex hybrid environments can make it difficult to track interdependencies, increasing the risk of disrupting critical business services. In this white paper by EMA, you'll learn how application discovery and dependency mapping can help you: Meet granular targets for availability, cost, and time-to-revenue for cloud services. Accelerate mean time to repair (MTTR) while communicating better with stakeholders. Manage even the most complex hybrid environments more efficiently and effectively Understand the …

  • Following an IT incident through to resolution is more than just acknowledging an alert and restarting a server. The recent State of On-Call Report found that it takes most companies an average of 10-30 minutes to resolve an incident with an average of 5 people involved. Imagine how much money and time companies are spending to deal with incident resolution. But what if you had a tool that offered solutions baked in? Or a tool that sent alerts to the right person or team every time? These are the kind of …

Most Popular Programming Stories

More for Developers

RSS Feeds

Thanks for your registration, follow us on our social networks to keep up-to-date