Les Questions les plus
fréquemment posées (FAQs)
for Windows Installer
What is the "Windows Installer"?
Microsoft has stated that the second most common problem with managing
desktops is application installation and maintenance. One of the common
goals of the Zero Administration for Windows (ZAW) initiative was
to create a streamlined process for installing and managing applications.
This process has been developed by Microsoft and named the Windows
Installer service. This process is a set of guidelines, an Application
Programming Interface, and a runtime service to help make application
installation and ongoing management part of the basic Windows system
services. It is a setup "engine" and rule set for installation
packages. The Windows Installer service, developed by Microsoft, is
not a setup-authoring tool. It defines the guidelines for all installation
packages, but does not solve the problem of creating the setup. That
is the role of Wise for Windows Installer. For more information on
the Windows Installer service, please visit http://msdn.microsoft.com/developer/sdk/wininst.asp.
Go to the Microsoft Windows Installer service white paper.
Why is there a different tool to create
installations, why can't I use my current Wise product?
All of Wise's current technology is based on one common solution,
an installation script. The new Windows Installer technology does
not use a script, in fact the entire installation is stored in a database.
The end user supplies all the necessary information about the installation:
files, features, registry settings, icons/shortcuts, etc. The Installer
service reads the database, decides what should be installed, and
then performs the appropriate actions.
Will installations I create with Wise
for Windows Installer be able to run on all Windows platforms?
Yes, installations created can run on Windows 95, Windows 98, Windows
NT 4.0, Windows Me, and Windows 2000. The installations created can
either be a single MSI file, or a self-installing executable. With
the self-installing executable option, you can choose to pre-install
the Windows Installer service and then hand off the installation to
your Windows Installer (MSI) file.
I've just upgraded to Wise 8.0, do I
need the new Wise for Windows Installer?
If you are using Wise 8.0, your installations can be executed on Windows
3.x (16-bit applications), Windows 95, Windows 98, Windows NT 4.0,
Windows Me, AND Windows 2000. You can also eliminate the time and
expense of recreating your Wise scripts by directly importing them
(V5 and higher) into Wise for Windows Installer. If you need to edit
the Windows Installer tables, or require any of the other functionality
and customization features for the Windows Installer service, you
will need to purchase Wise for Windows Installer 3.
I'm not really interested in the Application
Specification for Windows 2000, should I still investigate Wise for
Yes, the Windows Installer service provides a better way to manage
and track applications. New functionality includes the ability to:
manage install/uninstall at the component level for the entire system,
advertise applications without ever loading software on a system,
automatically repair key product files that have been corrupted, provide
rollback functionality in the case of a cancelled installation.
MSI, Windows Installer what's the difference?
Originally Microsoft referred to the technology as MSI, since that
was the file extension of the database (installation) that was created.
Over the last few months they have started using the term Windows
Can I convert my existing installation
to the Wise for Windows Installer tool?
Absolutely. Our development team has created an import Wizard that
will read in any Wise 5.0 or higher script, and create a stock Windows
Installer installation. After the import, you can edit this installation
as easily as if you created it from scratch. Also, we have converted
SetupCapture, Wise's snapshot technology that repackages existing
installations, to support creation of these new installations. Currently,
we are the only installation tool available that can repackage any
existing installation into a Windows Installer installation, and allow
that installation to be fully customized.
Installation System 9
What are the new names for Wise Installation System 9 products? Why
were they renamed?
Wise Installation System 9 is available in two editions:
· Wise Installation System - Professional Edition
· Wise Installation System - Standard Edition
This is a change from Wise Installation System 8, which was available
in three editions called InstallMaster, InstallBuilder, and InstallMaker.
Professional Edition, designed to meet advanced installation needs,
is comparable to the product formerly known as InstallMaster. Standard
Edition, designed to meet basic installation needs, is comparable
to the product formerly known as InstallBuilder. The names were changed
to make it easier for our customers to determine which Wise Installation
System product is the best fit for their needs.
Why are you no longer selling InstallMaker
for version 9? What does this mean for InstallMaker customers?
After careful consideration and feedback from our customers, we've
decided that having three different product levels within the Wise
Installation System family was not necessary. Having three product
levels was confusing to many customers, and the effort involved
in maintaining multiple products within a single family is significant.
Having said that, we also realize that some of our customers would
still like an entry-level installation tool with the quality of
a Wise product. For current InstallMaker customers, we're offering
a very cost-effective upgrade to Wise Installation System 9 - Standard
Edition. Standard Edition provides all the functionality of InstallMaker,
plus lots of great additions. For details on pricing and ordering.
What makes Wise Installation System
different from other products on the market?
Wise Installation System is the only script-based installation product
on the market that is still actively maintained and updated. While
other installation companies have focused solely on Windows Installer
based tools, Wise realizes that a significant number of developers
still prefer script-based technology. Regardless of which technology
you prefer, Wise Solutions offers a choice of best-in-class products.
A few other things that set Wise Installation System apart are:
· An intuitive scripting language that is easy to learn and
· Small, single file, self-installing EXEs with minimal overhead
· A more reliable installation solution
· A commitment to up-to-date runtimes
· The only script-based tool with application self-repair.
What is application self-repair? Don't
other products offer this same functionality?
Application self-repair checks for the existence of specific files
or registry keys every time your application is started on an end-users
PC. If any files or keys are damaged or missing, the user will be
prompted and the files or registry keys will be automatically replaced.
This provides a more reliable application to your customers as well
as reducing your support calls.
Self-repair functionality is currently only available with Windows
Installer-based installs, a technology that many developers have
not yet adopted. Wise Installation System is the only script-based
tool with self-repair.
Are script-based installation products going away?
Not anytime soon. Since Microsoft introduced Windows Installer,
many developers have been concerned that the script-based products
they are comfortable using will no longer be available. At Wise,
we want our customers to have a choice. We've worked hard to develop
best-in-class products for both script-based installations and Windows
Installer installations, and we plan on maintaining our script-based
product as long as the technology is still applicable.
Package Studio 3
Is Wise Package Studio a new product?
Wise Package Studio 3 is a new version of the product formerly called
Application Integration Suite, which consisted of the products PackageManager
Why was the product
A couple of reasons. First, we've restructured the product into
three different editions - Enterprise, Professional, and Standard
- each designed for a specific type of user. This would have caused
confusion trying to apply this new structure to the old naming scheme.
Second, our customers told us that "packaging" is increasingly
becoming a standard term for this technology, and when they think
of packaging they think Wise - hence, the name Wise Package Studio.
How is Wise Package Studio different
from other products on the market?
There are several things that make Package Studio unique. Among
1. At Wise, we believe
that one size does not fit all when it comes to repackaging solutions.
Wise Package Studio is available in three editions - Enterprise,
Professional, and Standard - to meet the needs of every type of
2. Package Studio applies a process-oriented approach to repackaging,
based on industry best practices and our own experience with repackaging
projects ranging in scale from large to small. No one else can incorporate
this experience into their product, because no one else has the
experience of Wise.
3. Wise Package Studio - Enterprise Edition is the only product
that promotes a collaborative approach to repackaging. The Workbench
interface streamlines the workflow process, promoting hand-offs
between group members, task documentation, project tracking, and
4. We've made significant advances in installation capturing technology.
Our SmartMonitor technology provides superior installation capturing
ability. This can save countless hours when repackaging a complex
5. Package Studio provides a true conflict management system, not
just simple package validation. Our ConflictManager detects and
resolves software conflicts between applications before they are
deployed throughout an organization.
6. Package Studio is the only product that provides both Windows
Installer and script-based installation technology. We provide full
support for installation creation and editing with either technology.
Why three editions?
We realize that one size does not fit all for system administrators
looking for a repackaging solution. Some individual administrators
are looking for a simple, cost-effective way to repackage applications
for Windows 2000 or Windows XP. For them, Standard Edition is the
perfect choice. Others work as part of application integration teams
that deploy software at a department or division level within their
company. For these users, Professional Edition will provide an ideal
approach. Still other administrators work at the enterprise level,
with teams that work closely together on coordinated, large-scale
repackaging projects. Enterprise Edition provides a proven solution
to meet the rigorous demands of these administrators.
Wise Solutions is the
only company offering a repackaging tool for each of these three
types of administrators.
What is repackaging? Why would I want
Repackaging refers to changing or customizing a vendor-supplied
installation, such as creating a silent installation or common installation
for all users, or pre-selecting which features will be installed.
There are several reasons
you might want to repackage installations. First, repackaging can
improve the reliability of a software application running on your
desktop environment. Second, installations can be streamlined by
making them silent (no user interaction) or by limiting the options
available to end-users. Third, repackaging can help to standardize
installations, making support and troubleshooting easier. Finally,
anyone migrating to Windows 2000 or Windows XP will want to repackage
installations to take advantage of the benefits of Windows Installer
technology. Since most ISVs currently don't distribute installations
in Microsoft's Windows Installer (.MSI) format, you will have to
repackage to take advantage of features such as application self-healing,
install-on-demand, and installation rollback.
The bottom line is repackaging
will result in more reliable desktops, reduced help desk support
needs, improved end-user productivity, and lower total cost of desktop
What is conflict management?
How does it work?
Conflict management refers to minimizing potential software conflicts
(competing .DLL files, registry entries, etc.) that can occur and
cause desktop crashes, end-user frustration, and downtime. However,
there are many different approaches to implementing conflict management,
so you need to be aware when shopping for a repackaging solution.
Some repackaging products provide limited conflict detection and
resolution which only works within a single software package. Package
Studio will guide the administrator to resolve virtually any type
of conflict across installation packages.
Package Studio provides three different levels of conflict management.
First, package validation tests an installation package to ensure
there are no internal conflicts within the installation. This includes
various checks for internal consistency, component design, file
duplication, advertising support, uninstall support, and more. Wise
package validation ensures compliance with Windows 2000 logo specifications.
Package validation is available in all three editions of Package
Second, wizard-based conflict resolution automatically detects conflicts
between an application and other applications to be installed on
a desktop. The Wizard guides administrators through the resolution
process by identifying each conflict and presenting alternatives
for its resolution. Wizard-based resolution gives administrators
the greatest degree of control by allowing them to resolve conflicts
on a case-by-case basis.
Wizard-based conflict resolution is available in the Professional
and Enterprise editions of Package Studio.
Finally, administrators can automatically eliminate conflicts between
applications using resolution rules. Resolution rules encompass
business standards regarding how conflicts are resolved, thereby
providing consistency and reducing the level of knowledge required
to produce a conflict free environment. Rules-based conflict resolution
fully automates the conflict resolution process by detecting and
resolving application conflicts with a single mouse click.
Rules-based conflict resolution is available in the Professional
and Enterprise editions of Package Studio. In addition, the Enterprise
edition allows administrator to tailor the pre-built rules in order
to customize conflict management for their organization.
Does Package Studio
help me distribute my application once it's been repackaged?
Wise Package Studio prepares installation packages for distribution,
but does not actually perform the distribution function. Packages
can be created for distribution via CD, local area network, Internet
or intranet site, or through your company's software distribution
system. Because Package Studio creates a single-file, self-contained
executable, it can be distributed through any of the leading software
Package Studio provides
additional levels of integration with Microsoft SMS®, and ON
Command SiteManager® to provide even more seamless package hand-offs
to these distribution systems.
What is a transform? Why is it useful?
A transform is a special kind of Windows Installer package (.MST)
used in conjunction with a native .MSI package. The transform file
is applied at runtime to change the way the base package runs. Transforms
are generally used to customize an installation for a particular
group of users.
The InstallTailor feature
found in Wise Package Studio allows you to easily create transforms.
InstallTailor simulates running an installation, capturing your
specific changes, and saves those changes to a transform file.
for Visual Studio .NET
What is Wise for Visual Studio .NET?
Wise for Visual Studio .NET is a specially designed Wise product
that operates within the Visual Studio interface, with the full
functionality of the Wise installation authoring environment. Wise
for Visual Studio .NET is the only full-featured installation
product embedded directly into Microsoft® Visual Studio®
.NET. Our participation in the Visual Studio Integration Program
and our close partnership with Microsoft gives us exclusive access
to Microsoft technology. We pass this knowledge on to you by offering
a full-featured Wise installation product specially designed to
work within Visual Studio .NET, making it easy to quickly create
Why is installation development so important?
The installation is the end user's first impression of the application,
so the installation has to be professional, polished, and work flawlessly.
Despite the importance of the installation, most development teams
still treat the installation as an afterthought. Waiting until late
in the development lifecycle to create the installation increases
the risk of errors and the subsequent negative first impression
with users. It's a high risk to take for such an important part
of application development. This is one of the reasons why our integration
into Visual Studio .NET is so important.
How does Wise for Visual Studio .NET improve the installation development
By integrating our installation technology directly into Visual
Studio .NET, we have created a new installation authoring model.
From the first line of code that's written, you will have a working
installation. You can now test the installation as you test the
application. The result is higher quality products, easier internal
testing, earlier beta availability, and a significantly more efficient
Why did Wise develop a product for integration into Visual Studio
Wise is an innovative company always looking for ways to use new
technologies to solve customer's installation problems. We immediately
saw this as an opportunity to change the way installations are created,
and are the first and only installation tool vendor to capitalize
on this opportunity.
How does this integration affect the application development lifecycle?
With this integration, we can merge the installation development
lifecycle with the application development lifecycle. This helps
developers eliminate redundancy in their work, facilitates communication
between developers, and automates manual tasks. Developers experience
a reduced learning curve because our interface is consistent with
Visual Studio .NET, and can create significantly higher quality
installations because the application and its installation are automatically
synchronized during development.
Were users involved in the design of this product?
As a customer-focused company, we always value feedback from our
customers as we design new products. The developer market is very
excited about the benefits of this new technology. From the beginning
they have been very willing to share ideas about how this integration
can be used to solve problems they face. In fact, many of our integration
features are a direct result of feedback offered by our customers.
What is the difference between the .NET support in Wise for Visual
Studio .NET and Wise for Windows Installer 4?
Both Wise for Windows Installer 4 and Wise for Visual Studio .NET
create installations that support the .NET Framework. The difference
is that Wise for Visual Studio .NET is embedded in the Visual Studio
.NET IDE (Integrated Development Environment), while Wise for Windows
Installer 4 is a stand-alone product. Wise for Visual Studio .NET's
complete integration into Microsoft Visual Studio .NET provides
the ability to create the installation as you create the application.
Information is automatically passed from the application to the
installation, such as application name, version and default directory.
This type of synchronization is not a feature of Wise for Windows
Does the integration in Wise for Visual Studio .NET work with previous
versions of Visual Studio?
The integration functionality in Wise for Visual Studio .NET only
works with Visual Studio .NET, as the technology used for the integration
was introduced in this version. The integration features are not
compatible with Visual Studio 6.0 or earlier versions. However,
Wise for Visual Studio .NET does work with all editions of Visual
Studio .NET, including Microsoft Visual Basic® .NET through
Visual Studio .NET Enterprise Architect.
Note that you can use Wise for Visual Studio .NET to create installations
for previous versions of Visual Studio, or even for other development
environments. The difference is that other installations cannot
take advantage of the integration featured accessible when creating
a Visual Studio .NET solution.
What features are different between Wise for Visual Studio .NET
and Wise for Windows Installer?
The macro editor is not a part of Wise for Visual Studio .NET because
Visual Studio has it's own macro editor that can be used to automate
Wise installations. Source control integration has also been removed
as it is not longer necessary due to our interface with the Visual
Studio .NET source control. The Import Visual Basic Product Wizard
has been removed because the integration eliminates the need for
What is the return policy for Wise for Visual Studio .NET?
The normal 30 day return policy applies for Wise for Visual Studio
.NET. The exception to this is if you buy the Wise for Visual Studio
.NET bundle-the Microsoft Visual Studio .NET portion of the bundle
is not returnable.