Skip to content
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

Install addin for all users #57

Open
daren-thomas opened this issue Jul 11, 2017 · 2 comments
Open

Install addin for all users #57

daren-thomas opened this issue Jul 11, 2017 · 2 comments
Assignees

Comments

@daren-thomas
Copy link
Member

El Capitan Dan wrote:

I believe the problem is that the Addins / Revit version folder does not necessarily exist under the admin user account combined with the fact the installer fails to place the addin file if that path doesn't exist for that account. Can the installer be modified so it installs for all users and creates the addins folder path if it doesn't exist already? This would fix the issue... I ran into this today btw.

In this thread: https://groups.google.com/forum/#!topic/revitpythonshell/ChXrDbyi6zg

Seems that installation by an admin results in the users not having the addin installed.

@joseph-kirkpatrick
Copy link

I've had an issue with this as well. I've read over the discussion groups and have even added the correct addin file. I ran this on my laptop and it works, however my workstation not so much. I'm trying to start with revit 2016, however it keeps giving me a missing revitpythonshell.xml from the %appdata%\Autodesk\Revit\Addins\RevitPythonShell.xml.

On my laptop I checked downloads/install for RPS 2016/2018 and the .xml file doesn't exist, nor does it on my workstation.

I'm afraid it's not working on my workstation due to my Revit at work being 2018.2

Currently I'm downloading revit 2016 on my laptop so I can get the .Addin file and put it on my workstation and see if that makes RPS work for 2016.

@fbe-work
Copy link

To me the problem seems two-fold:

  • RPS gets installed into C:\Program Files (x86)\RevitPythonShell20XX which requires admin privileges.
  • The install is per-user so the addin gets dropped into the admin per-user revit addin directory:
    C:\Users\<user_name>\AppData\Roaming\Autodesk\Revit\Addins\2017

One ( hacky ) approach I took in our office:
I compiled a (old - current does not build on my machine) version of RevitPythonShell that tackles both of these issues:
It drops the addin into per-machine revit addins directory, so everyone profits:
C:\ProgramData\Autodesk\Revit\Addins\2018
and installs to a non-admin path
C:\ProgramData\RevitPythonShell20XX

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants