Today's frustration comes in two parts. Expect my thoughts on x64 implementations shortly. But first, over the last week, I have been trying to shoehorn a legacy app into an AppV package. This thing is so ancient, it's trying to install, not to some handy directory like "C:\Program Files\BLAH" but directly to C:\
No directory. No. Just going to scatter my own directories directly to the root. So it comes as no surprise that this application does log management and launching via batch files.
So the good old .bat gets thrown on the temporal scrap heap. Until I have to get this thing running on WindowsRecentx64.
This is where I learned that when using AppV, you have to explicitly name what program the .bat file should run under in a shortcut. This means changing the target from
C:\BLAH\go.bat -fconfig /appvve:AGUID-WITH-A-BUNCHOFHEX_ANOTHER-GUID-WITH-MOREHEX
cmd.exe /C"C:\BLAH\go.bat -fconfig" /appvve:AGUID-WITH-A-BUNCHOFHEX_ANOTHER-GUID-WITH-MOREHEX
The same goes with .vbs and .js scripts, exept the engine changes to cscript or wscript if you like an abundance of pop ups.
Expect more ranting once I've finished documenting this legacy BLAH.