![]() ![]() 5 or later is installed and if not, install it (your installer will either have to include the. If you are using your own installation mechanism, be sure to check whether. The installer generated from the Generate Setup function described below automatically downloads and installs the. ![]() NET 4.5 or higher framework, so if it or a higher version isn't found on the user's system, it must be installed. One other thing: Stonefield Query requires the. If you are using your own installation mechanism, be sure to distribute or create this INI file. The Generate Setup function described below automatically creates this INI file on the user's system when they install your customized version of Stonefield Query. This installer requires a file called Setup.ini in the application folder, with the following contents: ĮXEName=Name of Stonefield Query executable without an extension ![]() Be sure to include this file in your installer. To facilitate this, a workstation-only installer, WSSetup.exe is provided. However, like most Windows applications, a minimal set of runtime files is required on each workstation that runs Stonefield Query. In the case of a network server, there isn't any need to install the Stonefield Query program files (the files in Stonefield Query program directory) or your custom project files on a workstation, since they can be accessed from the workstation you just need to install a shortcut to SFQuery.exe on the server. For details on standalone versus network installations, see. ![]() It can also be installed in a Citrix or Windows Terminal Server environment that works almost the same as a network server. Stonefield Query can be installed on either a single desktop computer for use as single-user software or a network server so it can be shared by several users across the network. In addition to avoiding the problems mentioned above, you can customize your setup to exactly suit your needs.īefore discussing how to create a setup executable, a discussion of setup types is in order. Instead, we recommend creating your own setup executable. Finally, our setup won't install your customized project files, so you'd need to do that as a separate step. Second, it shows the "Stonefield" name, which is a problem if you've private labeled or branded Stonefield Query. For one thing, that installs Stonefield Query Studio, which your user isn't licensed to use and you almost certainly don't want your user accessing. to install Stonefield Query on your user's system, we recommend against that. \AudioFile.Although you could use the setup executable you received from Stonefield Software Inc. Procedure OnMediaPlayerEvent(EventCode, Param1, Param2: Integer) TDirectShowEventProc = procedure(EventCode, Param1, Param2: Integer) įunction DSGetLastError(var ErrorText: WideString): HRESULT įunction DSSetVolume(Value: LongInt): Boolean įunction DSInitializeAudioFile(FileName: WideString ĬallbackProc: TDirectShowEventProc): Boolean Source: "MediaPlayer.dll" Flags: dontcopy Please note, that Inno Media Player is a Unicode library, and so you can use it only with Unicode versions of Inno Setup, not with ANSI ones! There is no support for ANSI versions of Inno Setup.! Here is an example of its use for playing audio file stored as a temporary file inside of a setup. You can use the Inno Media Player library (sorry for self promotion). ![]()
0 Comments
Leave a Reply. |