\rsid15277116\rsid15285540\rsid15428640\rsid15619894\rsid15929841\rsid16607764}{\*\generator Microsoft Word 11.0.6502;}{\info{\title AddInManager}{\author mich}{\operator mich}{\creatim\yr2005\mo11\dy29\hr19\min58}{\revtim\yr2005\mo12\dy8\hr19\min16}
\rsid14425394\rsid14484346\rsid15097273\rsid15277116\rsid15285540\rsid15428640\rsid15619894\rsid15929841\rsid16607764}{\*\generator Microsoft Word 11.0.6502;}{\info{\title AddInManager}{\author mich}{\operator mich}{\creatim\yr2005\mo11\dy29\hr19\min58}
If you have created an AddIn using the template, it will not show up in the AddInManager, not even as pre-installed AddIn. This is because the AddInManager only supports that have an }{\b\lang1033\langfe1031\langnp1033\insrsid2436208 Identity}{
If you have created an AddIn using the template, it will not show up in the AddInManager, not even as pre-installed AddIn. This is because the AddInManager only supports }{\lang1033\langfe1031\langnp1033\insrsid14102904 AddIns }{
\lang1033\langfe1031\langnp1033\insrsid2436208 . You should create one for every AddIn that you write, but you have to ensure that it is unique. SharpDevelop will not load two AddIns that use
\lang1033\langfe1031\langnp1033\insrsid2436208 that have an }{\b\lang1033\langfe1031\langnp1033\insrsid2436208 Identity}{\lang1033\langfe1031\langnp1033\insrsid2436208
the same identity. The identity is the internal name of the AddIn.
. You should create one for every AddIn that you write, but you have to ensure that it is unique. SharpDevelop will not load two AddIns that use the same identity. The identity is the internal name of the AddIn.
\par You can use any name, but it is highly recommended that you use a naming pattern like for namespaces: }{\lang1033\langfe1031\langnp1033\insrsid10317377 \'93}{\lang1033\langfe1031\langnp1033\insrsid2436208 AuthorName.AddInName\'94
\par You can use any name, but it is highly recommended that you use a naming pattern }{\lang1033\langfe1031\langnp1033\insrsid14116132 like}{\lang1033\langfe1031\langnp1033\insrsid2436208 namespaces: }{\lang1033\langfe1031\langnp1033\insrsid10317377 \'93}{
. You should use the same name as identity that you use as namespace for your AddIn.
\lang1033\langfe1031\langnp1033\insrsid2436208 AuthorName.AddInName\'94. You should use the same name as identity that you use as namespace for your AddIn.
\par All AddIns maintained }{\lang1033\langfe1031\langnp1033\insrsid10510865 by the SharpDevelop team}{\lang1033\langfe1031\langnp1033\insrsid8941365 use}{\lang1033\langfe1031\langnp1033\insrsid2436208 \'93ICSharpCode.AddInName\'94. Don't use \'93ICSharpCode
\par All AddIns maintained }{\lang1033\langfe1031\langnp1033\insrsid10510865 by the SharpDevelop team}{\lang1033\langfe1031\langnp1033\insrsid8941365 use}{\lang1033\langfe1031\langnp1033\insrsid2436208 \'93ICSharpCode.AddInName\'94. Don't use \'93ICSharpCode
\'94 for your AddIns; it is reserved for the SharpDevelop team! The reason why the default template does not include the identity section is because you really should think about which name you are going to use.
\'94 for your AddIns; it is reserved for the SharpDevelop team! The reason why the default template does not include the identity section is because you really should think about which name you are going to use.
\par }{\lang1033\langfe1031\langnp1033\insrsid13183743 After }{\lang1033\langfe1031\langnp1033\insrsid162269 adding the <Manifest> section}{\lang1033\langfe1031\langnp1033\insrsid10442943 , your AddIn will show up in the AddInManager:}{
\par }{\lang1033\langfe1031\langnp1033\insrsid13183743 After }{\lang1033\langfe1031\langnp1033\insrsid162269 adding the <Manifest> section}{\lang1033\langfe1031\langnp1033\insrsid10442943 , your AddIn will show up in the AddInManager:}{
@ -800,6 +800,6 @@ How to create .sdaddin installation packages
\par }{\lang1033\langfe1031\langnp1033\insrsid11092842 Creating these files is }{\lang1033\langfe1031\langnp1033\insrsid5664565 easy. Just compile the final version of your AddIn (maybe assign it a new version number). You\rquote re probably testing it as \'93
\par }{\lang1033\langfe1031\langnp1033\insrsid11092842 Creating these files is }{\lang1033\langfe1031\langnp1033\insrsid5664565 easy. Just compile the final version of your AddIn (maybe assign it a new version number). You\rquote re probably testing it as \'93
pre-installed\'94 AddIn inside the SharpDevelop\\AddIns directory; so you have to do only one thing to create the package: zip the files.}{\lang1033\langfe1031\langnp1033\insrsid11092842
pre-installed\'94 AddIn inside the SharpDevelop\\AddIns directory; so you have to do only one thing to create the package: zip the files.}{\lang1033\langfe1031\langnp1033\insrsid11092842
\par }{\lang1033\langfe1031\langnp1033\insrsid282022 Create a .zip archive containing the files \'93MyAddIn.addin\'94 and \'93MyAddIn.dll\'94. You can also include other files (required libraries, .pdb debug information, etc.).}{
\par }{\lang1033\langfe1031\langnp1033\insrsid282022 Create a .zip archive containing the files \'93MyAddIn.addin\'94 and \'93MyAddIn.dll\'94. You can also include other files (required libraries, .pdb debug information, etc.).}{
\lang1033\langfe1031\langnp1033\insrsid15285540 Rename the .zip to use the extension .sdaddin.}{\lang1033\langfe1031\langnp1033\insrsid14425394 That\rquote s all, your installation package is ready.}{
\lang1033\langfe1031\langnp1033\insrsid15285540 Rename the .zip to use the extension .sdaddin.}{\lang1033\langfe1031\langnp1033\insrsid14425394 That\rquote s }{\lang1033\langfe1031\langnp1033\insrsid9702452 all;}{