Today Flexera Software released a new version of Installshield. As a package engineer I’m very delighted with this news. Let’s have a quick look at some new features of Installshield 2013:
- Support for New Microsoft Technologies – Support for Windows® 8, Windows Server 2012 and Visual Studio 2012. For Windows 8, sideloading of Windows Store Apps is possible!
- Microsoft® System Center 2012 Configuration Manager Support enables application producers to provide required deployment metadata to their Enterprise customers, reducing the burden in managing their application
- PowerShell Support offers application producers the ability to streamline installation scripting requirements and support best practices of their Enterprise customers
- Create Pure 64-Bit Installations–Deploy 64-bit applications using 64-bit installations that support Windows Server configurations where WoW64 has been disabled
- Create Microsoft App-V Installations – Build both physical and virtual application packages from the same build process. Includes new support for App-V 5!
For further details, please follow the link below. Happy Packaging!
I’ve been using vbScript for a long time to write (simple) tools to make life a little easier. Because I’m so at home with vbScript I’ve put off using Powershell for al long time, but since App-V 5.0 uses Powershell extensively there’s no escaping it any more. I have to learn Powershell.
Lately I’ve been busy with running external executables inside an App-V 5 virtual environment (see my previous posts). Doing this requires you to find the packageID en VersionID of an App-V package and type a very long command line. So to set myself al least a bit of a challenge I decided to create my first Powershell script tool to make this a little easier. Read More…
We know that it is possible to launch a external (non virtualized) executable inside a App-V 5 virtual environment by using the /appvve parameter and supplying the PackageID and VersionID of the sequence that you want to launch the executable into.
So what happens if the sequence that you want to launch the executable into is part of a Connection Group? Will the launched executable have access to the complete virtual environment of the connection group? Well the answer is a simple “Yes”.
So I started to wonder if is it possible to connect directly to the Connection Group instead of to a sequence that is part of the Connection Group. Read More…
Microsoft has just released App-V 5.0 SP1.
This service pack contains the following changes:
- The App-V 5.0 sequencer and App-V 5.0 client now support twenty-four languages. You can download the additional language packs using the Volume Licensing Service Center.
- The App-V 5.0 server now supports eleven languages. You can download the additional language packs using the Volume Licensing Service Center.
- Support has been added for the App-V 5.0 Volume Shadow Copy Service (VSS) Writer feature.
Also support for sequencing Microsoft Office 2010 has now been added. The Microsoft Office 2010 Sequencing Kit for Application Virtualization 5.0 and the Microsoft Office 2010 Deployment Kit for App-V are required for this.
More information can be found here:
Consider these scenario’s
1. You have an application that has its main executable located on a network share but it also requires files installed on the local computer. You want to use App-V 5 to create a virtual package/sequence of the locally installed files and launch the network executable while making use of the created sequence.
2. You already have an App-V 5 sequence of an application and want to run another executable located on a network share while making use of this sequence.
This post has been revised. Please See Launching a network executable inside an App-V 5 virtual environment (Revised)
This blog about application packaging and virtualization has just been created. We’re currently working on content and layout.
Please come back soon.