![]() ![]() I didn't have to worry about sensitive information being returned so this worked - if you do have to worry about information being returned that shouldn't be stored in plain text then you will need to figure out a different method for getting the data back. I ended up needing to return objects so I exported the information as a clixml file, with a standard naming convention based on username and function so that the person running the script would always get their file back. ![]() Getting the data back to the form is a little more tricky - but there are a few ways to do that as well. Starting with PrimalScript 8.0.153 and PowerShell Studio 5.8.193, the MSI builder can now sign all files included in your installer. Just pass in the data you need as parameters to the background exe. This limits what can be done with this other account. This article provides an overview of a new feature introduced in PrimalScript 8.1.177 and PowerShell Studio 5.8.219 that enables you to quickly backup your source code. This also included interacting with SQL databases.Ī workable way would to take the bit of code that interacts with the sql database and package that as an exe running under the necessary windows account - and the main form runs only under the standard user account. I've been in your shoes before - my instance was I had a set of commands that had to run under different user accounts depending on the domain being interacted with - and the main form had to run as the logged in user. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |