![]() %HomePath%\WindowsPowerShell\Modules\ Product Name %HomePath%\Script Applications\ Product Name The following table shows the locations for a 64 bit OS with “ Install for all users” selected Product Type: Your selection here, together with the “64 Bit installer” and “Install for all users” options determines where your files are installed. If you created an MSI with a higher number it will uninstall the old version and then install the newer one.Ĭompany Name: Another field that is shown in the “ Programs and Features” display. The installer will use that number to determine if the specific product version is already installed. You should increment that number whenever you create a new build of your product. Product Name: That is what you will see in the Control Panel’s “ Programs and Features” display. So we decided to make a time limited preview copy available for everyone to test. As we previously pointed out, this may be a transition for some of you. It works pretty straightforward put the files you want to install into a folder, enter some additional settings and mucho presto you have an installer. ![]() Both PrimalScript 2014 and PowerShell Studio 2014 will have to ability to create Windows Installer files (MSI) for your scripts, modules or packaged executables. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |