Hi Paul,
I think you can just ignore that. I mean, although the files are shown uppercase,
the installed files should be in proper case; they are just shown that way in the publishing tool.
According to my experience, a good tool to create MSI for Visio-related stuff is
WIX, which be downloaded from the
codeplex.
The major advantage over VS Setup project is flexibility (you can customize user interface for example)
The Visio publishing tool does not seem to do rocket science actually, the magic is documented:
http://support.microsoft.com/kb/832029/en-ushttp://msdn.microsoft.com/en-us/library/bb677166.aspxI've attached a sample wix-based setup with source code to this post;
It does not use Visual studio setup project or Visio publishing tool; it publishes templates and stencils for Visio directly using Windows Installer's PublishComponent.
This sample setup installs 2 stencils and 2 templates; after installation they should show up in Visio UI (see the screenshot).
To build the project you should have WIX 3.5 installed.
Note that the publishing tool from Visio 2010 SDK seems to have a flaw when creating setups for Visio x32 installed on x64 windows -
the MSI generated by the tool may not work in this environment. That is, the "ConfigChangeID" registry key in this case will not be updated.
See here:
http://visguy.com/vgforum/index.php?topic=1619.0