Downloads: Project Line Counter Add-In v2.10 for VS.NET and VC6

<HTML>
<HEAD>
<Title>Compiling and Debugging</Title>
<link rel="stylesheet" href="helpmain.css">
</HEAD>
<BODY>
<Object type="application/x-oleobject" classid="clsid:1e2a7bd0-dab9-11d0-b93a-00c04fc99f9e">
	<param name="Keyword" value="Compiling Line Counter">
	<param name="Keyword" value="Debugging Line Counter">
	<param name="Keyword" value="hhc.exe">
</OBJECT><H1>Compiling and Debugging Line Counter</H1>
<p>&nbsp;</p>

<H2>Compiling - The Pitfalls</H2>

<p>The Line Counter project file includes the HTML Help Project file (LineCount.hhp)
which creates this help file using the HTML Help Compiler (hhc.exe).  If you don't 
have the HTML Help Authoring System installed on your system, you will not be 
able to compile the Line Counter project in it's default configuration.
</p>

<p>Two options are available to remedy the situation:
<ol>
	<li>Download the free HTML Help Authoring System from Microsoft from this
		URL: <a href="http://msdn.microsoft.com/library/tools/htmlhelp/wkshp/download.htm">
		http://msdn.microsoft.com/library/tools/htmlhelp/wkshp/download.htm</a>
	</li>
	
	<li>Exclude LineCount.hhp from the build process, and simply use the .CHM file
	    that came with the distribution.  To exclude LineCount.hhp, select Project|Settings,
		and highlight LineCount.hhp in the file list.  On the right side of the 
		dialog, select the "General" tab, and check the box titled "Exclude file
		from build".
	</li>
</ol>
</p><br>

<H2>Debugging DevStudio Add-Ins</H2>

<p>To debug a DevStudio Add-In, you must load DevStudio with the Add-In disabled
(i.e., go to Tools|Customize|Add-Ins and disable the add-in).  When you load
DevStudio the next time, the add-in will not be in memory, so you will be able 
to overwrite the .dll file when you compile the project.
</p>

<p>After the compilation, execute the program.  Since the add-in is nothing more
than a .dll, you will be prompted for a program to run.  Specify the full path
to MSDEV.EXE.  You'll get a warning message specifying that your program has no 
debugging information, because MSDEV.EXE itself has none.  This 
warning can be safely ignored.
</p>

<p>Once MSDEV.EXE is running under the debugger, you can reactivate the add-in
from the Tools|Customize|Add-Ins dialog.  The add-in will be loaded with it's
debugging information (if you compiled a Debug build), and you should be able
to set breakpoints and debug at will.  The next time you run MSDEV.EXE from the 
project workspace, the add-in will get loaded with it automatically.
<p>     

</BODY>
</HTML>

By viewing downloads associated with this article you agree to the Terms of use and the article's licence.

If a file you wish to view isn't highlighted, and is a text file (not binary), please let us know and we'll add colourisation support for it.

License

This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

A list of licenses authors might use can be found here

About the Author

Oz Solomon

Experion

Canada

Member

You may know Oz from his WndTabs days. Oz has long since left client side development to work on web technologies and to consult in the R&D management field.

Get statistics about your source code with a click of a button

Type	Article
Licence
First Posted	25 Mar 2000
Views	301,408
Bookmarked	133 times

VC6VC7WindowsDev
Advanced

		9,878,412 members (47,637 online) Visit CodeProject.TV Discuss CodeProject.TV Sign in Email Password Forgot your password? Sign in using