ajaxmin Discussions Rss Feed

New Post: Option to ignore warnings per input file when using AjaxMinTask

ronlo — Tue, 07 May 2013 23:10:58 GMT

Just released 4.91. Let me know if you have any issues with it. I'll update the docs shortly.

New Post: Ajax minifier and Visual Studio 2008 with 3.5?

ronlo — Tue, 07 May 2013 23:10:17 GMT

Starting with version 4.91, the .NET 3.5 DLLs (AjaxMin.dll and AjaxMinTask.dll) are included in the NuGet package under the tools\net35 folder.

New Post: Option to ignore warnings per input file when using AjaxMinTask

dflor003 — Mon, 06 May 2013 18:42:44 GMT

Perfect, that sounds like it'd work. I always make it a practice to include 3rd-party libraries first anyways, since our JS files depend on them.

New Post: Option to ignore warnings per input file when using AjaxMinTask

ronlo — Mon, 06 May 2013 18:02:54 GMT

Okay, this will be in the 4.91 release. If you specify the attribute origin="external" on an <input> element of the manifest XML, all warnings will be suppressed while minifying that file (will still throw JavaScript syntax errors, but an external file shouldn't have any of those anyway).

One small ramification is that this could change the groupings of files concatenated together around any external file(s). Before this change, all input files were concatenated together and then the entire combination was minified to the output file - and that behavior will remain the same for any set of input files that contains no origin="external" attributes. After this change, external files will always be minified by themselves, independent of the other files in the group, and all adjacent project files (those not marked as "external") will be concatenated and minified together. Finally, the groups of concatenated input files will be concatenated together into the output file. For example, an output group that contains :

    <input path="file1.js"/>
    <input path="file2.js"/>
    <input path="file3.js"/>
    <input path="external1.js" origin="external" />
    <input path="external2.js" origin="external" />
    <input path="file4.js"/>
    <input path="file5.js"/>

will actually concatenate four sets of minified concatenated code into the output file: minify(file1.js+file2.js+file3.js) + minify(external1.js) + minify(external2.js) + minify(file4.js+file5.js). The order of the minified files in the output remains as specified in the order of the <input> elements; it's just that adding external input files to the mix creates different groupings that get independently minified as they are added to the output file. Those groups will be separated by a newline in the final output file.

New Post: Option to ignore warnings per input file when using AjaxMinTask

dflor003 — Thu, 25 Apr 2013 17:41:05 GMT

Alright, not a problem at all, take your time. Thanks for looking into it!

New Post: Option to ignore warnings per input file when using AjaxMinTask

ronlo — Thu, 25 Apr 2013 16:48:35 GMT

Just FYI: turns out to be more difficult than it appears on the surface. The manifest is used to concatenate the input files and specifies the overall switches and output file to use on that combined input. It then hands off to the parser and visitors, which generate the warnings and don't really know what the manifest says about the various pieces-parts making up the combined input (right now). I think I have an idea on how to do this, though, but it might be further out than the 4.90 release, since I have a couple high-pri bugs that I need to get fixed and released first. But I still love the idea.

New Post: Option to ignore warnings per input file when using AjaxMinTask

dflor003 — Wed, 24 Apr 2013 17:55:20 GMT

Awesome! Thanks!

New Post: Option to ignore warnings per input file when using AjaxMinTask

ronlo — Wed, 24 Apr 2013 15:06:26 GMT

I like it! I'll see if I can add that for 4.90.

New Post: Option to ignore warnings per input file when using AjaxMinTask

dflor003 — Wed, 24 Apr 2013 04:29:37 GMT

I'm trying to get AjaxMin setup in a project I'm working on (utilizing the AjaxMinTask via AjaxMinTask.targets) and here's my scenario:

Ideally, I would like to bundle every JS file in my project into one. This includes 3rd party libraries like knockout & jQuery. However, when including said 3rd party libraries, a bunch of warnings are logged (~800+ warnings). Of course, since the 3rd party libraries are out of my control, it makes no sense to go in and correct the libraries. Furthermore, I would like to enable TreatWarningsAsErrors, to prevent our interns from checking in warning-laden code.

Would it be possible to add property to <input /> tag in the manifest file such as the following:

<output path="Scripts/min/mylib.min.js" type="js" enc="utf-8">
    <input ignorewarnings="true" path="Scripts/lib/modernizr/modernizr-2.6.2.js" />
    <input ignorewarnings="true" path="Scripts/lib/bootstrap/bootstrap.js" />
    <input ignorewarnings="true" path="Scripts/lib/jquery/jquery-2.0.0.js" />
    
    <input path="Scripts/src/myfile1.js" />
    <input path="Scripts/scr/myfile2.js" />
</output>

Setting ignorewarnings to true (false by default), should suppress any warning messages received while processing that particular file.

New Post: Ajax minifier and Visual Studio 2008 with 3.5?

sinsedrix — Tue, 23 Apr 2013 10:14:37 GMT

I fixed this problem using the old AjaxMinSetup-4.19.msi that works with 3.5, see:
https://ajaxmin.codeplex.com/releases/view/65673

New Post: Existing Source Map

olegbl — Tue, 12 Mar 2013 22:17:39 GMT

It actually might be even more useful if the source map was read out of the file rather than passed as a parameter.
This piping of multiple maps is not necessary for the codebase we're working on - but would be a really cool feature!

I.E.

AjaxMin take in FileA, FileB, FileC and produces FileO.
FileA references FileAMap which maps it to FileASource
FileB references FileBMap which maps it to FileBSource
FileC does not have a source map
FileOMap source map will map FileO to FileASource, FileBSource, FileC

New Post: Existing Source Map

olegbl — Mon, 11 Mar 2013 20:15:54 GMT

Yes, exactly! That would be incredibly helpful for working with our TypeScript codebase.

New Post: Existing Source Map

ronlo — Mon, 11 Mar 2013 19:59:47 GMT

As in: take a JS file A and it's existing source map B, and minify it to generate file C and adjusted map D? I hadn't considered that path. Not at the moment, but it sounds like a very useful feature.

New Post: Existing Source Map

olegbl — Mon, 11 Mar 2013 19:55:22 GMT

Is there a way to minify compiled code (and generate sourcemap) without losing the original sourcemap (like from coffeescript or typescript)? (i.e. somethign similar to uglifyjs' --in-source-map flag)

New Post: Suppress conversion of escaped characters in a string

ronlo — Mon, 04 Mar 2013 16:47:30 GMT

I think using the -enc:out ascii switch will get you what you need.

New Post: Minified variables inside function block

Aristos — Fri, 01 Mar 2013 20:55:08 GMT

Thank you for the answer, is works.

I am use direct the dll on the program, so I use the RenamePairs parameter to set that pairs.

New Post: Suppress conversion of escaped characters in a string

mcrossley — Thu, 21 Feb 2013 21:02:10 GMT

Thanks, I guess I should have said I'm using the standalone exe, I'll give this a try.

New Post: Suppress conversion of escaped characters in a string

ronlo — Thu, 21 Feb 2013 20:04:49 GMT

Sure -- don't use the UTF-8 encoding for output. If you use, say, ASCII (-enc:out ascii), then extended characters like that will be output using the \uXXXX encoding pattern. If you are using the DLL, run your minified string through a stream using ASCII Encoding object and the JSEncodingFallback (see http://ajaxmin.codeplex.com/wikipage?title=EncoderFallbacks).

Or you can use a kill-switch to stop all optimizations on all string literals: if you are using the DLL, set your CodeSettings object's KillSwitch property to TreeModifications.MinifyStringLiterals. Or using the command line, -kill:0x100000.

New Post: Suppress conversion of escaped characters in a string

mcrossley — Thu, 21 Feb 2013 18:53:31 GMT

The minifier is handling my UTF-8 files great now.

But is it possible to suppress the conversion of unicode escaped characters into their literal characters.

eg in my source I have "some string \u00B0" gets converted to "some string °"

Cheers
Mark

New Post: Azure support?

AaronFisher3 — Wed, 20 Feb 2013 17:18:03 GMT

Yes, Sorry. I wish to minify Javascript at build time.

I've followed this tutorial: http://www.asp.net/ajaxlibrary/AjaxMinQuickStart.ashx I've added the following code to my web project .csproj, according to the tutorial.

<UsingTask TaskName="AjaxMin" AssemblyFile="$(MSBuildProjectDirectory)\Build\AjaxMinTask.dll" />
  <Target Name="AfterBuild">
    <ItemGroup>
      <JS Include="**\*.js" Exclude="**\*.min.js" />
    </ItemGroup>
    <ItemGroup>
      <CSS Include="**\*.css" Exclude="**\*.min.css" />
    </ItemGroup>
    <AjaxMin JsSourceFiles="@(JS)" JsSourceExtensionPattern="\.js$" JsTargetExtension=".min.js" CssSourceFiles="@(CSS)" CssSourceExtensionPattern="\.css$" CssTargetExtension=".min.css" />
  </Target>

This works fine on my local machine, but it does not work with on the azure environment, the .min.js files are not written on the azure machine.
I've included the AjaxMin.dll and AjaxMinTask.dll in the web project under folder named Build.

I've tried modifying this code to <JS Include="***.js" /> (Removed the exclude) and I can see the .min.js files if i create a deployment package and unzip it, but I still get a 404 error on the azure site when the webpage tries to load the .min.js file.
The solution also has an azure cloud service project, which is used for some configuration settings. I haven't made any changes to that. I don't see any build errors and I'm not sure what i am missing.

thank you.