Note that there are some explanatory texts on larger screens.

plurals
  1. POVisual Studio installer project sets my database to require admin privileges to write when installed with elevated permissions
    primarykey
    data
    text
    <p>I am generating an install project in Visual Studio 2010 for a C# addin to be used with Microsoft Excel. My addin uses an SQLite database, and this database needs to have write permissions for the user working with the addin.</p> <p>The problem is that I also need to write to the registry in HKLM and the Program Files directory. To do this, the installer must run with elevated permissions, which is not a problem, but when I do so, the database is set to require admin rights to write, which is an issue, despite being played in the CommonAppData folder which does not require admin rights.</p> <p>Is it possible to set the database to not require admin rights in the install project? I have at my disposal to work with: Visual studio install projects, Installshield 2008 and Installshield 2012.</p> <p>I found an almost identical question to mine posted here: <a href="https://stackoverflow.com/questions/4719224/visual-studio-installer-project-setting-file-permission">Visual Studio installer project - setting file permission</a></p> <p>The msdn link, however, is dead and the other link only suggests putting the files in a location that does not require elevated permissions.</p> <p>(Note: I have, for the purposes of testing, simply removed the portion of the files that need to be put in program files, and written to HKCU so that I can get around this issue temporarily; however this is not going to be suitable for deployment as this is going to be added to a much larger project that needs to have these issues resolved.)</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload