Running Arelle from IIS

[Charles Little]

I'm running arelle from an ASP.NET WebAPI application.  When I register a plugin (inline xbrl plugin), the registration says that it works.  But when I call it again with --plugins show or try to use the functionality, I'm told it does not exist.  I now know that it registers plugins to the %APPDATA%\Local\Arelle directory in plugins.json.  But the user's directory for IIS is C:\Windows\system32\config\systemprofile\AppData\Roaming, and when I register, I don't see anything added.  I've tried to force it (copying over the data from my app data directory), but that doesn't seem to help.  How would I pre-register a plugin that's running under the system account?  Or either call the plugin registration and have it registered?

[Kenji Ikiryo]

How are you running it?  You can run it in two ways... from the commandline with the --plugins and specify the plugin, or permanently register it, something I had problems with.  So you'd do arelleCmdLine.exe --plugins=+inlineXbrlDocumentSet.py in order to make it persist before your call, or  arelleCmdLine.exe --plugins=inlineXBRLDocumentset.py  (Add your other commands here) to just use the plugin with one call.  if you don't include the + and try to do it in different calls, you'll have problems.