So, once again, lots of under-the-hood code clean up and UI refinements in this release, which can be found in the full changelog.
But there are a some very cool new features which are designed to enhance your workflow. These deserve more of a spotlight, so here it is:
Refining the new project process
The New Project Window has been redesigned to make the whole process more binary-centric. Now, when you choose to create a new project/solution, you’ll immediately be prompted to select your desired binary (apk/jar/img). The available project types are then filtered according to the binary type, so you are only faced with the relevant options.
You’ll also notice a new tab along the left side of the box:
So you are about to create a new project, and selected the binary to import. You’ve chosen your desired settings (API level, framework tags etc) and you want to quickly apply those same settings to other projects in the solution. The new Presets feature makes this incredibly easy.
Once you’ve selected all your settings, head to the Presets tab and you can save these with whatever name you choose.
Next time you add a new project, all you have to do is choose your desired preset, and the same settings will be applied automagically.
If you forget to save your preset before completing the New project process, or you want to make a preset based on an existing project’s settings, don’t worry. Just right click on the project name in the Solution Explorer and you’ll see the option to create a new preset based on that project.
Whilst presets are useful when adding a single binary, they really become a powerful tool when batch adding binaries:
Dragging and dropping binaries
VTS has always allowed you to drag and drop single binaries (drag the binary over the Document window or the Explorer Ribbon). But now you can also add multiple binaries in one go. Yes, that’s right, batch adding has finally arrived!
Once you’ve opened your solution, just select the binaries you want to add in the Windows Explorer, and drag then over the Document window. You’ll be prompted to choose which preset you’d like to apply to those projects, simply make your choice and VTS will do the rest.
While there is no theoretical maximum to the number of binaries that can be imported in one go, it’s probably best to do them in stages otherwise your computer may slow to a crawl! The only limitation is that you can only batch add binaries of the same type – so no combinations of apk/jar/img. But we can live with that right?!
VTS 2.3.27 introduced the concept of advanced global settings, which could be edited via various xml files. Well, these settings have now been fully brought into the VTS environment.
If you open the Settings page, you’ll see the new Advanced button at the bottom.
There are lots of powerful customisations possible here, and should only be changed if you know what you are doing. The best way to find out what’s possible is to have a look around, but to give you an idea of the UI settings:
So for example, you can now choose whether or not the Projects list is autoexpanded when you open a solution:
There are also Advanced Project settings, which can be found at the bottom of the Project-specific settings window.
Again, it’s worth having a look around, but this is where you can set binary-specific apktool and smali flags, for example:
Not a big thing, but incredibly useful when managing large solutions. You can delete all project backups within a given solution with one click, and also backup all projects.