yang686526

setup project for developed addin
hello,
i want to send the developed addin (in the format of a "setup.exe") to my colleague for test purpose. it may be convenient for him to just click the executable file and install the addin. then he test the addin from solidworks. i have no idea about how to build such installer. please help.
newform
edited: 09/18/2008 at 02:47 pm by newform newform
winrar and or winzip has a functionality where you can create an executable zipped archive, and run a set of commands that you tell it to do.
this may be the easiest way for you to do this..
sw2009 sp3.0
pentium d 840-3.2 ghz
4gb ddr2 667
ati firegl v5600 - driver ver. 8.440.0.0
winxp pro 32bit
an understanding that without any understanding, we would all be misunderstood..
how can winrar register the addin to solidworks then? i want to build an "setup.exe" using visual studio 2005. the exe file is able to copy the addin (dll) file and associated files to a specified folder and register it to solidworks. then the addin will be loaded when you open solidworks. it could be better if it can be uninstalled as well.
can i do that?
thanks
edited: 09/18/2008 at 03:10 pm by newform newform
check out the api topic how do i create an installer api project...
wayne matus
texas engineering systems
dear wayne,
appreciate your information. i found the api topic about "create setup project to distribute solidworks add-in". i follow the instruction and build a setup.exe and setup.msi. my colleague installs it. but he cannot find the addin (through solidworks - "tools" - "add-in") when he starts up solidworks. he is using windows xp 64bit. does the os cause the problem?
many thanks
newform
originally posted by: wayne matus
check out the api topic how do i create an installer api project...
what version is this topic in? i could not find it in '07.
drc inc.
minneapolis, mn
.designreadycontrols.com
sw2007 sp5.0
core2 quad
3gb ram
xp pro sp2
ati firegl v3600
hi,
i am using solidworks 2008, visual studio 2005 and windsows xp 32-bit.
edited: 09/19/2008 at 10:50 am by newform newform
newform,
the os does make a difference. x64 stores the add-ins under a different registry key.
what i did for a quick fix was to manually register the add-in on a computer with 64 bit os. i then found the registry keys it created and copied them. i used a shareware tool called inno setup to create the setup file and had it add these registry keys on install and remove them on uninstall.
unfortiunately i live in houston and our office is still without power, so i cannot give you more info in this.
wayne matus
texas engineering systems
i'm just wondering where you found the topic "create setup project to distribute solidworks add-in".
chris
solidworks 2007 (office pro.) sp5.0
testing solidworks 2009 (pro) sp0.0
dell precision t3400
2 cpu (8500) 3.16 ghz, 3.25 gb of ram
window xp pro sp2
nvidia fx 570 6.14.11.6262
i found this topic in solidworks api help file
i guess it's in sw2008
do you mind to copy and paste it here
thx, chris
solidworks 2007 (office pro.) sp5.0
testing solidworks 2009 (pro) sp0.0
dell precision t3400
2 cpu (8500) 3.16 ghz, 3.25 gb of ram
window xp pro sp2
nvidia fx 570 6.14.11.6262