1

Closed

DNNtc also minifies already minified .js

description

When building a DNN-package, DNNtc also minifies .js-files that are already minified. This causes bad behaviour (errors and malfunctioning) when those .js-files are loaded in the module, after installing the generated PA on another DNN-instance.
 
By defacto standards, minified .js-files should always be named <filename>.min.js. It would therefore be a good idea to exclude those whilst copying .js-files to the temporary directory, where they are minified by MSBuild.
 
I have attached an altered Project.targets file to this issue, that does just that. Basically the change implies adding an extra path into the already existing "Exclude"-attribute of the "CreateItem"-element in the copy script section (starting at line 264).

file attachments

Closed Jul 15, 2013 at 2:20 PM by EPT

comments

KP_XCESS wrote Sep 26, 2012 at 2:14 PM

Added an additional attachment, containing an already minified JS-file in it's original minified state, as well as a copy in its DNNtc-reminified state (causing errors).

KP_XCESS wrote Sep 26, 2012 at 2:16 PM

Added another attachment, containing a file in it's original minified form, versus the file after beïng minified again (by DNNtc).

wrote Feb 13, 2013 at 11:20 PM

wrote Jul 15, 2013 at 2:20 PM

wrote Jul 15, 2013 at 2:20 PM