Include version in filename generated by MakeAppx.exe when using packaging layout

%3CLINGO-SUB%20id%3D%22lingo-sub-1507704%22%20slang%3D%22en-US%22%3EInclude%20version%20in%20filename%20generated%20by%20MakeAppx.exe%20when%20using%20packaging%20layout%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1507704%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20using%20a%20packaging%20layout%20file%20and%20MakeAppx%20to%20generate%20my%20appx%20and%20appxbundle%20files.%20That%20generally%20works%20ok%2C%20but%20one%20problem%20is%20that%20the%20files%20that%20are%20generated%20in%20that%20way%20don't%20include%20the%20version%20number%20in%20their%20filename.%20The%20Visual%20Studio%20Wap%20type%20automatically%20seems%20to%20generate%20output%20files%20that%20include%20the%20version%20in%20the%20filename%2C%20which%20seems%20safer%20so%20that%20one%20doesn't%20have%20to%20overwrite%20previous%20installer%20files.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20a%20way%20to%20tell%20MakeAppx%20to%20generate%20output%20filenames%20that%20include%20the%20version%20in%20the%20filename%20when%20using%20the%20packaging%20layout%20option%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1509602%22%20slang%3D%22en-US%22%3ERe%3A%20Include%20version%20in%20filename%20generated%20by%20MakeAppx.exe%20when%20using%20packaging%20layout%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1509602%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20to%20elaborate%20a%20bit%20more%20on%20this%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20want%20to%20host%20an%20appinstaller%20file%20on%20the%20internet%2C%20say%20at%20%3CA%20href%3D%22https%3A%2F%2Fwww.mycompany.com%2FFoo.appinstaller%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.mycompany.com%2FFoo.appinstaller%3C%2FA%3E.%20My%20impression%20is%20that%20this%20is%20the%20one%20file%20that%20I%20would%20overwrite%20whenever%20I%20publish%20a%20new%20version%20of%20the%20app%2C%20but%20that%20ideally%20all%20other%20files%20would%20get%20distinct%20filenames%20when%20I%20publish%20a%20new%20version%20of%20my%20app.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERight%20now%2C%20MakeAppx.exe%20creates%20the%20following%20files%20for%20me%3A%20Foo.appxbundle%2C%20Foo-x64.appx%20and%20the%20corresponding%20other%20platforms.%20I%20then%20host%20all%20these%20files%20also%20at%20%3CA%20href%3D%22https%3A%2F%2Fwww.mycompany.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.mycompany.com%3C%2FA%3E.%20But%20ideally%2C%20it%20seems%20to%20me%2C%20that%20these%20files%20would%20be%20named%20Foo_1.0.0.0.appxbundle%2C%20Foo-x64_1.0.0.0.appx%20etc%2C%20so%20that%20I%20don't%20need%20to%20overwrite%20the%20previous%20versions%20of%20these%20files%20when%20I%20publish%20a%20new%20release.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

I'm using a packaging layout file and MakeAppx to generate my appx and appxbundle files. That generally works ok, but one problem is that the files that are generated in that way don't include the version number in their filename. The Visual Studio Wap type automatically seems to generate output files that include the version in the filename, which seems safer so that one doesn't have to overwrite previous installer files.

 

Is there a way to tell MakeAppx to generate output filenames that include the version in the filename when using the packaging layout option?

1 Reply

Just to elaborate a bit more on this:

 

I want to host an appinstaller file on the internet, say at https://www.mycompany.com/Foo.appinstaller. My impression is that this is the one file that I would overwrite whenever I publish a new version of the app, but that ideally all other files would get distinct filenames when I publish a new version of my app.

 

Right now, MakeAppx.exe creates the following files for me: Foo.appxbundle, Foo-x64.appx and the corresponding other platforms. I then host all these files also at https://www.mycompany.com. But ideally, it seems to me, that these files would be named Foo_1.0.0.0.appxbundle, Foo-x64_1.0.0.0.appx etc, so that I don't need to overwrite the previous versions of these files when I publish a new release.