Dependencies to Include with Setup Project MSI Creater

Dependencies to Include with Setup Project MSI Creater

TheLaymansShaman
Explorer Explorer
1,432 Views
3 Replies
Message 1 of 4

Dependencies to Include with Setup Project MSI Creater

TheLaymansShaman
Explorer
Explorer

 

Hi,

 

I have created Visual Studio Setup Projects for deployment of my Revit addin across the relevant product versions but am stumped as to what dependencies I need to include.

 

I have added the project output to the setup project and the detected dependencies list is as below.

image.png

image (1).png

 

I have excluded a fair few of these as can be seen on a purely experimental basis with no adverse affects thus far, but still feel that I am including too many with my deployment and it is adding potential bulk to the MSI file size.

 

Please can someone kindly highlight any of the dependencies I need on the Autodesk side and any others which may seem obvious to you professionals? Or those I need to exclude, whichever is simpler. I am obviously using a few nuget packages which is why I have Mahapps dependencies etc. I assume I need to include all these? I have searched online for the answers but to no avail sadly.

 

Thanks in advance.

 

Sincerely,

 

David 

 

Accepted solutions (1)
1,433 Views
3 Replies
Replies (3)
Message 2 of 4

jeremy_tammik
Alumni
Alumni
Accepted solution

All the Revit API .NET assembly DLLs are already provided and loaded by Revit, so your add-in does not need to include those in its MSI. All the system assembly DLLs are already provided by the .NET framework, so you can skip those also. There should hardly be anything left, really.

  

Jeremy Tammik Developer Advocacy and Support + The Building Coder + Autodesk Developer Network + ADN Open
Message 3 of 4

TheLaymansShaman
Explorer
Explorer

Jeremy,

 

Thanks for the rapid response on this. You've confirmed my suspicions.

 

I guess part of the problem for me was my setup project populated this dependency list automatically which made me question whether they were needed.

Also the naming of some of them wasn't obviously associated with Revit to my mind.

 

I think what I may do is look in the Revit install directory and if I see one of these dependencies there will assume I don't need it. If this is a bad approach let me know please.

 

I'm abit of an amatuer so I don't know what the system assemblies you're referring to are by name either but will assume they must be the System.something dll's.

 

Thanks again,

 

David

 

 

Message 4 of 4

jeremy_tammik
Alumni
Alumni

I have often streamlined my references by trial and error: remove one, try to recompile, restore it if it fails; repeat.

  

Jeremy Tammik Developer Advocacy and Support + The Building Coder + Autodesk Developer Network + ADN Open