ODBC Drivers + No Shortcut Apps

Siva116 

Starting off with the easy stuff:

You can create a package without any shortcuts.  Your "ODBC Driver" consists of registry settings, plus optionally something like an oracle client that acts as middleware.  The question is how to tie that to the primary app that will use it?  Assuming that the primary app is also MSIX:

• Under the currently released OS's, your only choice is to create your driver package as a "Modification Package", which in essence is a layered add-on to the primary package.  This is a great use when you have a primary package that must work with several back-ends (such as dev/test/prod) and you deploy the primary app plus the modification package with settings that you need.
• In 21H2 we expect to see (it is available in preview versions) "Shared Package Containers".  This would allow a different workflow for creating your settings package, potentially allowing more flexibility (such as applying these settings to multiple main packages).

But ultimately, it would be best to have A package contain a shortcut, even if it uses a natively installed app under the covers. 

There are some other obscure options involving the Powershell cmdlet to start a native process in a container, but those only work on 20H2 and above and are a kludge at best and should be avoided.

In regard to AppData.  As long a your package(s) don't specify any AppData files and they are generated by running the app, you probably don't need the PSF.  If you do, PsfTooling 4.10 is the latest version.  Using the Psf requires a shortcut in that package, but you could make that work whether or not the target exe is inside of a package.  The details are complicated, but the tool has in-built help.  The missing part for you might be how to create the overall scenario before running the tool.

I understand this might not be a complete answer for you, but start with this and come back with specific questions and more details on the scenario.