Glad to hear it helped you Gregory. Thanks for the...

2011-04-29T11:07:14.994+10:00

Glad to hear it helped you Gregory. Thanks for the tip about the update, I'd considered making something like that if I couldn't get this working!

I've been talking to ADN about this problem, and if there's a business case for getting this problem fixed they might be able to fix it sooner and enable that option by default, so if anyone wants this fixed be sure to contact them (or post here and I'll pass it on) with some good reasons why it should be changed!

Rod, Thanks for the info. This appears to have fi...

2011-04-28T15:04:30.136+10:00

Rod,

Thanks for the info. This appears to have fixed my build problem...well at least part of my problems.

fyi. relative to your problem of keeping everyone up to date. At the office of one of my clients I have developed a small program that simply pushes the new/modified dlls/ addin manifests out to each computer.

Each time a user starts revit it compares a version in a simple text file on their computer with a similar file on the server. If they don't match, then I pop up a window and generate an email with computer name and info already written(but don't autosend) saying that their revit is out of date.

When i update or add a dll, i run the routine with all computer names (from a text file list) as a target.

When i receive the email, i simply run the routine with their computer as a target.

The only downside (and I suppose you have this with your method too) is that the user has to be out of revit for me to be able to up date (since it locks the dlls...or was that just the revit.ini...i'm not sure anymore)

anyway...info.

thanks again.

Comments on Rod Howarth: [Revit API]– Running your add-ins from a network d...

Glad to hear it helped you Gregory. Thanks for the...

Rod, Thanks for the info. This appears to have fi...