Open Source File Visual C++ Add-In

Environment: VC6 x86 NT4 W2K

I wrote a Visual C++ add-in that opens a file that is stored anywhere in your Visual C++ x86 "Include" path. I use it to open files such as winerror.h or header files mentioned in MSDN.

The source files were built using Visual C++ 6.0 and the Add-In wizard.

To install:

  1. Compile the OpenSourceFile.dll
  2. Click on Tools|Customize|Add-ins and Macro Files
  3. Browse and select the DLL file
  4. It will add a new toolbar


Download source - 39 Kb


  • Even more cool way to do so...

    Posted by Legacy on 09/07/2001 12:00am

    Originally posted by: Jyoti

    just click on the file name included or type the name of file in string quote or surrounded with angle bracket and right click (in visual studio editor) then select the option , Open Document.

  • A free tool rename an Existing Visual Studio project.

    Posted by Legacy on 09/07/2001 12:00am

    Originally posted by: Steven

    UCanCode Just release a new version of toolbox,you can use it to rename an existing visual studio project or to backup an existing visual studio a free copy by visit

  • Another way to do this

    Posted by Legacy on 09/06/2001 12:00am

    Originally posted by: Keith Bussell

    You can achieve the same effect by typing the file name in the FindTool (find combo box in the toolbar) and hitting Ctrl-Shift-G (FileGoTo).

    This also works for opening any file contained within the active project of the current workspace.


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

Top White Papers and Webcasts

  • Enterprises are increasingly looking to platform as a service (PaaS) to lower their costs and speed their time to market for new applications. Developing, deploying, and managing applications in the cloud eliminates the time and expense of managing a physical infrastructure to support them. PaaS offerings must deliver additional long-term benefits, such as a lower total cost of ownership (TCO), rapid scalability, and ease of integration, all while providing robust security and availability. This report …

  • Moving from an on-premises environment to Office 365 does not remove the need to plan for disruptions or reduce the business risk requirements for protecting email services. If anything, some risks increase with a move to the cloud. Read how to ease the transition every business faces if considering or already migrating to cloud email. This white paper discusses: Setting expectations when migrating to Office 365 Understanding the implications of relying solely on Exchange Online security Necessary archiving …

Most Popular Programming Stories

More for Developers

RSS Feeds

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