will/pdm
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Initial Commit of the PDM project (ready for DWS migration)

Browse Source
This commit is contained in:
will
2026-04-20 08:42:38 -05:00
commit dda7b664e7
2721 changed files with 442772 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

86
documentation/api_extracted/DebugAddins.htm Normal file
View File

@@ -0,0 +1,86 @@
<html>
<head>
<title>Debugging Add-ins</title>
<meta name=MS-HKWD content="Add-ins, debugging">
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<link rel="stylesheet" type="text/css" href="ApiHelp.css">
<style>
<!--
div.Section1
{page:Section1;}
.auto-style1 {
font-size: x-small;
}
-->
</style>
</head>
<body>
<h1><span style="font-weight: normal; font-size: 7.5pt;">SOLIDWORKS PDM Professional API Help</span></h1>
<h1>Debugging Add-ins</h1>
<div class=Section1>
<p class=MsoNormal><span lang=EN-US style='font-family:Verdana'>Add-ins
<span class=GramE>are</span> stored in the file vault and are downloaded to
and COM-registered on the client computer when they are needed. This
presents a problem when developing a new add-in that you want to debug, because the add-in is re-registered in a folder
that is different than the
compiler’s output folder. Testing an add-in in a
production vault can also be a problem, because it affects all users of the
vault.<o:p></o:p></span></p>
<p class=MsoNormal><span class=SpellE>
<span lang=EN-US style='font-family:Verdana'>SOLIDWORKS </span></span>
<span lang=EN-US style='font-family:Verdana'> PDM Professional provides a menu command that solves these two problems, <b>Debug Add-ins</b>.</span></p>
<p class=MsoNormal><span lang=EN-GB style='mso-ansi-language:EN-GB'><br>
<img border="0" src="DebugAddIn.gif" width="290" height="256"></span></p>
<p class=MsoNormal><span lang=EN-US>&nbsp;</span></p>
<p class=MsoNormal style='background:white'>
<span lang=EN-US style='font-family:Verdana'>When an add-in is installed as a
debug add-in, it
is registered only on your machine. No other users are affected by it. The add-in
is also loaded from the location where it is registered.<o:p></o:p></span></p>
<p class=MsoNormal style='background:white'>
<span style="font-family: Verdana">T</span><span lang=EN-US style='font-family:Verdana'>o
debug an add-in using File Explorer:</span></p>
<ol>
<li class=kadov-p>
<p>
Open
the Windows Task Manager.</p></li>
<li class=kadov-p>
<p class=MsoNormal style='background:white'>
<span style="font-family: Verdana">K</span><span lang=EN-US style='font-family:Verdana'>ill the
<b>explorer.exe</b> process.</span></p></li>
<li class=kadov-p>
<p style='background:white'>
<span style="font-family: Verdana">Right-click the project name in the
Solution Explorer of Visual Studio and click <b>Properties</b>.</span></p></li>
<li class=kadov-p>
<p style='background:white'>
<span style="font-family: Verdana">Click the <b>Debug</b> tab.</span></p></li>
<li class=kadov-p>
<p style='background:white'>
<span style="font-family: Verdana">Click <b>Start external program</b> and type
the File Explorer executable's path. For example:</span><span lang=EN-US style='font-family:Verdana'><br>
<br>
</span>
<span lang=EN-US style='font-family:Courier New; font-weight:700' class="auto-style1">C:\windows\explorer.exe</span></p></li>
<li class=kadov-p><p class=MsoNormal style='background:white'>
Click <b>Debug &gt; </b><span lang=EN-US style='font-family:Verdana'><b>Start
Debugging</b>.</span></p>
</ol>
</div>
</body>
</html>