I do the same trick as dan with the extmap file, can't stress how critical that is. Random thought - I'm not 100% certain if the library caching it per app though so potentially maybe I am creating a problem if they go to one website with an existing minimified telerik library and then back to mine.. will it still download my minified version? hopefully otherwise my app could fail. So far no problems! ;)
Anyway, would prefer not to have to rely on a manual, online process do do the job. Much rather have an .exe that runs locally and that can be easily run from the build process, the importantly thing being it is easy to automate into each build.
I think how you position and develop the minifier further
will be quite important and there are strategy implications here. The minifiier is particularly useful for smaller projects or
ones that don't require obfusication as the silverlight bloat problem can be quite bad.
not suggesting it's not useful also for big projects, but considering the marketplace strategically - I really want to see full dead code elimination, there are a number of
tools available that do this like the "ComponentOne XAP Optimizer",
(although personally I'd never buy there ridicously overpriced software given it
doesn't do even half the job)
by half, I mean that decent obfusication (OBF) tools have dead code elimination
(DCE) , and so from my perspective, ideally a product does OBF and DCE in one hit. if I was buying something then I would perceive limited value in something that does just one or the other. hence my
earlier suggestion that if I require obfusication, I'm going to select a
decent tool and thats hopefully going to have DCE built in.
also, you really want DCE and OBF automatically incorporated into the build and
deploy process as a automatic postbuild activity, .. and obfusication tools are
basically post-build anyway so thats good.