Mass deployment of an API or macro 1

[powder99]

I have created a small macro and would like to know if there is a way to install on 50 or so machines via the network rather than installing on each machine. I would ideally like to install a compiled dll of the macro on the server and when each solidworks client machine starts up the program is automatically started. Is this possible. I'ld appeciate any help.

Cheers
Steve

 

[TheTick]

Since macros are simply run-time VB code, they can be run from a network location.

Put your macros in a network folder, then set everyone's SW options for macro directort to look at that folder (there may be a way to set the options over the network, but I wouldn't know).

"Great ideas need landing gear as well as wings."--C. D. Jackson

http://www.EsoxRepublic.com

 

[JNR]

That reminds he, Tick, I was going ask our Guru about your distribution question before the holiday. Now that the holiday is over (and we have dug out from our ice storm that really screwed things up round here) I will corner him. I did mention it yesterday when he was loading a new one on my system, but he was real busy.

Tell you what maybe we can get you two in direct contact. I think you would be able to help eachother out a lot.

BTW: The stuff he loaded yesterday runs from a custom toolbar add-in menu and goes out and searches our FlexGen system for part information.


I was - and he did. So at least I didn't get coal.....

 

[deek05]

Powder99,
We share our macro's over the network except the macro's that have a keyboard shortcut associated to it (like our properties editing macro). For these I use a .BAT file and email it to the users. I updated 2 macro's yesterday using this .BAT file. Here's what the .BAT looked like:

***********the .BAT file*****************************
@echo off
c:
cd\Program Files\SolidWorks2004\Macros
copy \\NetworkLocationOfMacro\MacroName#1.swp
copy \\NetworkLocationOfMacro\MacroName#2.swp
*****************************************************

Hope this helps,
DT

 

[TheTick]

JNR:

Thanks. I forgot what my question was, though. What was my question?

"Great ideas need landing gear as well as wings."--C. D. Jackson

http://www.EsoxRepublic.com

 

[powder99]

Thanks Deek05 I'll give it a shot!

 

[JNR]

Tick: I sent you his email address so you guys can talk directly.

Ref. This thread. Our programmer guru sends us an email when there is an update to their custom tools. It contains a link to click on and the whole thing is automatic. Actualy, come to think of it, I think he automatically senses the version now and forces the update. I'll let him explain to TheTick and he can probably tell you if it is what you need.

I don't get into the SolidWorks programming myself - in fact I don't really do that much SW these days at work. I'm mostly busy being Hardware Lead Engineer on 2 developemnt programs.

I was - and he did. So at least I didn't get coal.....
OK, OK, It's a reference to my holiday sig. "Be naughty - Save Santa a trip..."

 

[powder99]

Hi JNR,

The update process that your programmer implements is exactly what I'm looking for - a simple way for the 50 or so workstations to update tools. I look forward to TheTicks post.

 

[JNR]

I have been one of 3 beta guinea-pigs for a new feature in our custom toolset. I just got an up date which only affects the 3 of us. He send me an email with the new files. All I have to do is detach them to a folder he uses for our tools. There are 2 .dll file and one .ex_ One is the top level tool module, one is the module that runs this application and the other is the executable that goes out and queries our company's FlexGen MRP system. So it is not too cumbersome to do it that way.

I was - and he did. So at least I didn't get coal.....
OK, OK, It's a reference to my holiday sig. "Be naughty - Save Santa a trip..."