Video Screencast Help

Wise Packaging

Results for Wise Packaging

If a file that should have been removed from the user's computer remains installed after running an uninstall, the installer may not be removing the component containing the file for one or more of the following reasons: The ...
Blog Entry by R-Vijay | 12 Nov 2007 | 7 comments
Application packaging is a process of binding the relevant files and components to build a customized application for a customer. Using tools like Wise Package Studio and Install Shield we carry out the whole process of packaging. In this article we ...
Article by R-Vijay | 09 Nov 2007 | 3 comments
Files in Use and Restart manager are two big features of Windows Installer 4. These features provide excellent support to MSI packagers when customizing an application which needs a restart for optimal functionality. Files in Use: Files-In-Use ...
Blog Entry by R-Vijay | 09 Nov 2007 | 0 comments
While packaging a .NET application, Identifying where the assemblies reside will purely depend on the usage of an assembly. This article will be useful in identifying where an assembly should reside. Further, it will give a brief understanding of ...
Article by R-Vijay | 09 Nov 2007 | 0 comments
A shim, in the software world, is a thin piece of code we wedge between Windows and an application to solve compatibility problems. The following are some specific examples of Microsoft's ACT (Application Compatibility Toolkit) Shims and where they ...
Article by R-Vijay | 07 Nov 2007 | 0 comments
When a vendor MSI installation fails on deployment, many a times it may be because of the Custom action present in it. Here are some steps to take if you suspect your failure is related to such an action. Generate the MSI log and search for RETURN ...
Blog Entry by R-Vijay | 07 Nov 2007 | 0 comments
Adherence to the following guidelines when authoring a Windows Installer package helps maintain a secure environment during installation: Make any property set by the user a public property. Private properties cannot be ...
Article by WiseUser | 05 Nov 2007 | 0 comments
Session 0 isolation introduces a problem for Services that need to display UI to the user. Since the Service is now running in a different Session and Desktop, the UI would not be visible to the end user and hence the application would appear to hang. ...
Article by R-Vijay | 02 Nov 2007 | 2 comments
You've heard the adage that "timing is everything". With application packaging, timing (or the sequence of events) really is everything. If you're having trouble with a package the problem might be related to conflicts caused by ...
Blog Entry by WiseUser | 02 Nov 2007 | 1 comment
Software packages should not automatically repair data (local- or server-based data) on launch. Such an automatic repair could overwrite data changes made by the user. Therefore, components in the MSI that include data files (e.g. Access MDBs) will not ...
Blog Entry by R-Vijay | 01 Nov 2007 | 5 comments