Deployment Tool, Different Config Files, Same Results

Question

I should mention that I'm generating App-V 5 packages for Office 2013. Maybe this question belongs in the App-V forums.
I can't seem to create a configuration file for the Office Deployment Tool that does what I want. This configuration:
<Configuration>
<Add SourcePath="D:\Something\Something\Source\Full Suite" OfficeClientEdition="32">
<Product ID="ProPlusVolume">
<Language ID="en-us" />
</Product>
<Product ID="VisioProVolume">
<Language ID="en-us" />
</Product>
<Product ID="ProjectProVolume">
<Language ID="en-us" />
</Product>
</Add>
</Configuration>
generates an App-V package with the "basic" Office apps (Word, Excel, etc.), along with Visio and Project. That part is fine.
If I remove the Product elements for Project and Visio, I expect that a "basic" Office package will be created. However, Visio and Project are still in the package, and they are indeed usable. We have limited licenses for Project and Visio, so
I would like them not to be deployed to every machine.
I have tried giving the two configuration files their own source folders, that is, running the download command once for each configuration file and telling it to download to two different folders... same results.
This is similar to John Marcum's follow-up question at
https://social.technet.microsoft.com/Forums/office/en-US/c9462446-7744-4e3e-8c25-dbcd185a17e4/creating-lync-and-onenote-appv-packages?forum=officesetupdeploy

Answer 1

Kazzan's reply technically does work, and it is a viable option. However, that reply led me to wonder what the Office Deployment Tool (ODT) is doing to a machine that makes generating different packages difficult or impossible.
I found that the ODT leaves files behind in the current user's Temp directory, after the package generation is finished. At least one of these folders (named Microsoft Office 15) contains the file system contents of the App-V package. So, I decided
to clear the Temp directory in between runs of the Office Deployment Tool. Simply clearing this directory was not enough to solve the problem, but I'm still doing it as part of the build process.
Running Process Monitor showed me activity in HKCU\Software\Microsoft\Office\15.0\ClickToRun. Deleting this entire key does not appear to be necessary, and I'm not sure what that would do if you actually used Office Click-To-Run on the same machine on which
you're running ODT.  So, I deleted just these keys:
HKCU\Software\Microsoft\Office\15.0\ClickToRun\Configuration
HKCU\Software\Microsoft\Office\15.0\ClickToRun\ProductReleaseIDs
HKCU\Software\Microsoft\Office\15.0\ClickToRun\Scenario\APPVPACKAGE
Deleting those keys, along with the Temp directory cleanup, is sufficient to let me build multiple Office 2013 App-V 5 packages on the same computer.