Since about 2010, there is the project of virtual environment with modular structure for developers and users, so that they can use a completely pre-configured environment with all programs, tools and services, without the host environment interfering with the running operating system and devouring resources.
Short setup times, uniform tools with uniform configuration, uniform paths in the file system, centralized maintenance and easy distribution and updating are some of the benefits. The environment is easily customizable, can be quickly switched to use for different projects, and the environment can be easily transferred to other machines where work started can be continued.
The project includes with platform, a tool for the initial creation, use and management of the virtual environment and a module concept for the automatic integration and configuration of tools and programs from any source on the Internet.
The module concept is a successful PoC (proof of concept), but is not currently the focus of the project. So the software has to be set up manually in the virtual environment, but that's easy because it's a normal drive.
Since in large companies the strict use of BitLocker is often required, this is also supported.
What is the difference with PortableApps.com or portapps.io?
The virtual environment focuses on the virtual drive as a platform. It is about the advantages that the platform can be used as a single file and programs and services can be used in it with a complete configuration and with reliable absolute paths.
The integration and distribution of portable applications are not the ambition of this project.
The use of modules for the integration of programs and services is planned, but is more an exemplification of the possibilities for the integration of programs and services. However, it is not the intention of the project to establish a corresponding eco-system or repository.
PortableApps.com and portapps.io complement the virtual environment perfectly and both release very good portable versions of programs that can be used in the virtual environment.
- A virtual drive is used, which contains all data in one file.
- The drives can also be supplied and used via the network.
- Only one large file can be copied faster and also shared.
- Snapshots and versioning are possible.
- Multiple drives with different environments can be used in parallel on one computer.
- Fast switching between different drives and environments is possible.
- Fixed drive letters and paths are used.
- The use of the file system and registry from the host is avoided.
- Environments can be maintained and distributed centrally.
- A team use the same environment with the same paths and configurations, which facilitates automation.
- Supports VHD, VHDX as virtual drive also with Bitlocker
- Functions to create, launch, manage and compact the environment
- The environment is immediately usable after creation
- Integrated program launcher with optimized keyboard support for fast program access
- Personalization of environment and programs through a separate key values file
- Very small and resource-efficient implementation of the platform
- The use of the local file system and the registry is avoided
- Easy customization according to the requirements
- Simplifies centralized maintenance and distribution
- Simplifies automation
LIZENZBEDINGUNGEN - Seanox Software Solutions ist ein Open-Source-Projekt, im Folgenden Seanox Software Solutions oder kurz Seanox genannt.
Diese Software unterliegt der Version 2 der Apache License.
Copyright (C) 2024 Seanox Software Solutions
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
https://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
- Microsoft Windows 10 or higher
- Microsoft .NET 4.8.x or higher (for runtime)
- Microsoft .NET 4.8.x Developer Pack or higher (for development only)
Seanox Virtual Environment 3.4.0
Seanox Virtual Environment 3.4.0 Update for existing environment
Download the master templates as virtual environments (approx 4 GB /
last update 2024-05-20):
https://seanox.com/storage/master-3.5.0.7z
https://seanox.com/storage/master-proxy-3.5.0.7z
Included is a complete development environment with various tools for AWS, Kubernetes, Terraform, Java and Node.js, including a customized Eclipse, a PostgreSQL database and much more.
Start master.exe B: attach.
The host key combination for the launcher: Win + ESC
To exit, use the Detach button at the bottom right of the launcher.
- Download the example(s)
- Rename
master.exe,master.iniandmaster.vhdxto your name
Next steps are optional and after attaching
- Change the label of the virtual disk (properties of disk)
- Change the name of the virtual volume in
AutoRun.inf
- Download the last release of seanox-platform.zip
- Extract the file to any location in the local file system
- Rename platform.exe to the name that will be used for the environment and drive
Then the program can be used as follows::
usage: platform.exe A-Z: [create|attach|detach|compact|shortcuts]
Example
platform.exe B: createto create the initial environment as VHDXplatform.exe B: shortcutsto create the usual calls as shortcutsplatform.exe B: attachto attach the environment
Configure Startup.cmd in the root directory of the virtual environment and add the desired programs and services. It is recommended to use a launcher so that the environment variables are available to the called programs. Detach should also be started via the launcher if programs and services are terminated when detaching and the environment variables are needed for this.
platform.exe B: detachto detach the environmentplatform.exe B: compactto compact the virtual disk
Module integration will come later, but will be similar.
BF: Review: Optimization and corrections
BF: DiskPart: Optimization when attaching disks with the same label
BF: DiskPart: Correction when creating with Windows 11
CR: DiskPart: Optimization of detach if an error occurs
CR: Macros: Optimization of the use of WORKDIR
CR: Macros: Usable as direct short commands
CR: Project: Updated TargetFrameworkVersion to v4.8
CR: Platform: Refactoring of the standard directory structure
CR: Launcher: Updated TargetFrameworkVersion to v4.8
CR: Startup: Updated TargetFrameworkVersion to v4.8