BoxedApp Blog

BoxedApp: Tips'n'Tricks, Examples, Use Cases etc.

BoxedApp Packer 2019.2, BoxedApp SDK 2019.1

We are excited to announce that we’ve just released BoxedApp Packer 2019.2 and BoxedApp SDK 2019.1:

  • FIX: GetFinalPathNameByHandle() failed for virtual files located on virtual drive.
  • FIX: if input exe required administrative privileges, packed exe didn’t require administrative privileges.

New tutorial is ready: packaging .NET Core application into a single executable file package.

BoxedApp SDK 2.1, BoxedApp Packer 2.2

Released new versions of products of the BoxedApp series: BoxedApp SDK 2.1, BoxedApp Packer 2.2.
[ Download demo versions ]

What’s new?

Launching .NET Applications From Memory

We’ve issued new update of the BoxedApp SDK and BoxedApp Packer, which includes new function BoxedAppSDK_ExecuteDotNetApplication

BoxedApp SDK 2.0.1, BoxedApp Packer 2.1.1

We’ve tested BoxedApp under new Windows from MS, Windows 7. A few issues found and fixed.

[FIXED] ShellExecute doesn’t run virtual EXE under Windows 7
[FIXED] ActiveX registering in a virtual registry may not work properly under Windows 7

A small fix for all Windows:

[FIXED] Launching a lot of child processes cause memory and handles leak

New feature of the BoxedApp Packer:

[NEW] Environment variables are supported in a virtual path.

[ Download demo version ]

BoxedApp SDK 2.0, BoxedApp Packer 2.1

Finally, we have made available the new releases with two extremely interesting features:

Let’s take a closer look at them