-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MSI add-in installer #42
Comments
Yes I will do a video and code on this. I'll leave this open until I do it |
It would be great! Actually I am working on it now but unfortunately can't register COM object with WiX toolset. BTW Am I right, sw exe path is not necessary for COM registering? |
Correct. I just have that in my Addin Installer tool so the user clearly sees if they actually have SolidWorks installed :P |
Even in the existing an option for installing MacroFeature COM may be necessary in the future. |
@angelsix, do you have a plan when you approximately complete this video? |
Probably a month, as I go away next week then 2 weeks after that for another 2 weeks. So prob 5-6 weeks away |
@angelsix, it would be great. I've done MSI installer with COM registration using WiX, if you need any help I'll be glad to provide |
Hi @doronkind I am just being in the same situation that an installer from WiX is required for my project, did you ever have permission issue that is preventing you from activating the add-in ? For example, install the addin with a path like: C:\Program Files\Folder\ |
@angelsix, good morning!
What do you think about to provide some examples how to create msi/exe installer for your sw add-in? I think it can be useful cause it is really lack of information about this.
Does it works with your framework: http://help.solidworks.com/2015/English/api/sldworksapiprogguide/Miscellaneous/Create_Setup_Project_to_Distribute_SolidWorks_Add-in.htm?id=5e152c0abbef41ad99e957ec76cb2335
I think we can use WiX Toolset, e.g. to create MSI but if you have a working example it will be great to analyze it.
The text was updated successfully, but these errors were encountered: