If the user wish he/she can replace $(TargetFileName) with $(TargetName) and we got old behavior.
Look: It is not as simple as this.
If a user selects "App.Plugin" as a library name you don't know if (s)he wants to have a "Ap.Plugin.dll" or really just "App.Plugin". So querying any extension (by using
GetExt()) will not work reliable as for a file like "App.Plugin" it will return "Plugin" as extension which is most likely not intended. Ceniza once posted a solution with another checkbox option that would really enable to setup
exactly how the file name should look like and TDragon once posted how GCC "expects" the library extensions. However, I don't find these posts anymore, so I asked Ceniza to have a look at his history here:
Ceniza once proposed a good UI way how to handle this. TDragon proposed how to "tell" the MinGW/GCC compiler what to do. We can continue the discussion once we re-collected this information.
...but he didn't answer yet. :-(
From my point of view that was the only acceptable solution so far as it allows for any file naming scheme.