I don't believe that anything in my post could be considered a 'rant'. And I believe I was totally 'on topic'. Please point out where you believe I was ranting or off-topic and I will attempt to prevent it happening again.
You can even use multiple URLs in your web media block URL fields. This will work. Does this mean that InstallAware should extrapolate and create one copy of the web media block file for each URL entered?
Well, obviously not, because as you said earlier, Installaware is a Windows tool and that wouldn't work even if that was desired, which it isn't.
Can we just take one step back?
When I create my own web blocks, if I use multiple URLS and muck up my Installation hosted on a linux server by creating one with a declaration of upper and lower case and one with all lower case, then so be it - I'm the dill who mucked up and has to fix it. I don't expect Installaware to create multiple web blocks, I don't expect Installaware to do anything differently to what it does now.
But I wasn't referring to web blocks created by the end user.
My issue is with the Installaware tool automatically adding declarations for pre-requistes such as the .Net framework that are known not to work on Linux hosting.
When I check the box to add the .net framework I see that 2 scripts are added to the project (checknet20 and setupnet20). At that point the Web Block declarations also appear in the project.
It surely would not be difficult to change those declarations when they are generated, so that they match the output file.
Please explain to me how that specific point (italicized above) is not in the best interest of your customers at large. My perception is that it makes no difference to people hosting on Windows and helps those hosting on Linux. Is that perception incorrect?
Wouldn't this "generating the .net framework declaration in the same casing as the web block file" actually assist more customers than the current method? Despite your comment to the contrary, I have thought this through and cannot see how it can be construed as a negative.
If I come back to my project and add additional URLs for the framework and am silly enough to muck up the casing then as I said, thats my fault.
I am not suggesting any change to the way web blocks are created.
I'm simply saying that the declaration created automatically by Installaware when adding a pre-requisite should be consistent in casing with the file created.