Wise Install Maker was a version 8 release if I recall correctly. The Wise installer is named Wise So I guess the thread I pointed to won't help with this product. What I keyed-in on and made me hopeful was this quote from that thread: " I now have a lots of.
The subdirectories: Include and Runtime. INI file in there. So where did these come from on our old build PC? These are not something that Wise distributed back in the day? Sure, I can copy the files from the old build PC, but we are trying to source everything as much as possible back to their roots. Our apps indeed do run on WinXP all the way up to Win8 using these old runtimes, amazingly they do work. If you have any insight into where files in the Runtime and Include directories come came from, that would help immensely.
Like: was there an installer at some point in the past that was used to populate these directories? If not, how was one, back in the day, instructed on how to populate these directories? We lament daily our necessity to deal with old software. The basic software installation for Wise Installation System 9. These could be downloaded individually from the Wise website as it was in those days.
The product had reached end of life even before Altiris acquired Wise so there was no real motivator to migrate these downloads to the Altiris web servers. By the time Symantec acquired Altiris and eventually killed off the entire Wise product family, these runtimes were just a distant memory to those who were involved with the original products back in the 's. That's the history bit. Therefore, if you have populated Runtime and Include folders on your old machine, copy them over to the new machine.
I think that is all that is required. After all this time I don't recall whether the downloadable runtimes had any kind of installer or you were just prompted to unzip them and drop them in the appropriate folder.
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.
Why was the product renamed? 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 them:. 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 administrator. 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. 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 user security. 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 application.
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. 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 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 to repackage? 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 or Windows XP will want to repackage installations to take advantage of the benefits of Windows Installer technology.
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 ownership. What is conflict management? How does it work? Conflict management refers to minimizing potential software conflicts competing.
DLL files, registry entries, etc. 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 logo specifications. Package validation is available in all three editions of Package Studio. 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. All you need is a valid Wise product ID. Our InstallAware setup dynamically defines the features and files to be installed. Instead of building, maintaining, and shipping separate installers for all the languages, IDEs, and product editions that we offer, we are now able to build and deliver a single install image.
This has dramatically reduced our integration workload along with reducing our costs. I know absolutely nothing about creating Windows Installer installations but with InstallAware I don't need to.
It's so easy to get quickly up and running with InstallAware. David Clegg, eBetOnline. InstallAware is a one-of-a-kind product. I searched high and low for a solution to provide the ability to download and install runtimes from the Internet only if they are needed. InstallAware was the only program I could find that offered this for all the runtimes needed. Chris Hoffman, Mystik Media.
0コメント