Showing posts with label AppPackaging. Show all posts
Showing posts with label AppPackaging. Show all posts

Monday, 26 August 2013

Application Packaging Online Training - September 2013 Batch

Application Packaging online training using AdminStudio would start from 11th September 2013.
Interested candidates can call me on +91-9963678795 or email me on for registrations and to know more about timings and fee details.
Special Discount: Hurry! register and make payment by 7th September 2013 and avail 10% discount.
For more details of our training and consulting services, please visit

Friday, 18 March 2011

Merge Modules

Merge Modules are pre-compiled logic of code which can be used by different applications. For more info please visit MSDN at below URL

Saturday, 6 March 2010

Source Resiliency

Applications that rely on network resources for installation-on-demand are susceptible to source failures if the source location should change for any reason or become damaged. The Windows Installer provides source resiliency for features that are installed on-demand by using a source list. The source list contains the locations searched by the installer for installation packages. The entries in this list can be network locations, Uniform Resource Locators (URLs), or compact discs. If one of these sources fails, the installer can quickly and seamlessly try the next.

The application developer does not need to incorporate any special information into the installer package to ensure source resiliency. Once the application is installed, the installer has the behavior of adding the last successfully used source as an entry in the source list. By default, this source is the location from which the installer package is initially installed, and is the same as the SourceDir property.

A system administrator can change the source list by applying a transform or by changing the SOURCELIST property from the command line or in the Property table.

The installer begins searching for a source by checking the most recently used source location in the source list. If this search fails, the installer searches the list of network sources, then media sources, and finally URL sources. System administrators can change this search order using the SearchOrder system policy. If these searches fail, the installer may present a Browse Dialog so that the user can search for the source manually. The browse dialog box cannot be displayed if the user interface level is set to None. For details, see User Interface Levels.

Commonly, the installer should only display a browse dialog box if the current user is an administrator or if the installation does not require elevated privileges. An administrator can control the display of the browse dialog box to users with the DisableBrowse and AllowLockDownBrowse policies. An administrator also controls whether users can install applications from sources located on media by using the DisableMedia and AllowLockDownMedia policies. The use of these policies depends on the Windows Installer version.

Process for Creating InstalShield Response file(iss)

Refer to attachment containing steps on how to create Response Files.

Process for Creating InstalShield Response file(iss)

Thursday, 4 March 2010

Application Packaging

This is a place where you can know about Application Packaging. Its a hot and demanding domain in the current market.

Application Packaging is basically customizing applications according to Microsoft Best Practices/Requirements and making ready for deployment in Organizations.

Deployment of applications to client desktops will take place normally using a Deployment Tool ( Eg: SCCM,  BMC Marimba, HP OVCM, ManageSoft etc.., )