Quantcast
Channel: ajaxmin Issue Tracker Rss Feed
Viewing all 683 articles
Browse latest View live
↧

Edited Unassigned: Build task fails if arguments are specified and in/out paths are the same [20189]

September 16, 2013, 2:23 pm
$
0
0
Steps taken -

* Installed the 4.96 MSI
* Removed cleanup task from AjaxMin.targets in $(MSBuildExtensionPath)\\....
* Added .targets reference to .csproj - <Import Project="$(MSBuildExtensionsPath)\Microsoft\MicrosoftAjax\AjaxMinTask.targets" Condition="'$(Configuration)|$(Platform)' == 'QA|AnyCPU' Or '$(Configuration)|$(Platform)' == 'Release|AnyCPU'" />
* Added build.ajaxmin to project as follows -

```
<root>
<arguments>-global:jQuery</arguments>

<output path="scripts\module\f1.js">
<input path="Content\scripts\module\f1.js" />
</output>
<output path="scripts\module\f2.js">
<input path="Content\scripts\module\f2.js" />
</output>
</root>
```


The build target fires, but the files are not minified. No error is given.

Remove the <arguments/> node and everything works as expected.
Leave the <arguments/> node and change the output path(s) and everything works as expected.
Comments: ** Comment from web user: ronlo **

This should now be fixed in any v5 release.

↧
Search

Commented Issue: Microsoft Ajax Minifier 5.0 problems [20199]

September 17, 2013, 1:38 am
$
0
0
During using the Microsoft Ajax Minifier 5.0 in ASP.NET MVC 4 (.NET 4.0), the following error occurs:

```
Could not load file or assembly 'AjaxMin' or one of its dependencies. An attempt was made to load a program with an incorrect format.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.BadImageFormatException: Could not load file or assembly 'AjaxMin' or one of its dependencies. An attempt was made to load a program with an incorrect format.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Assembly Load Trace: The following information can be helpful to determine why the assembly 'AjaxMin' could not be loaded.


WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].


Stack Trace:


[BadImageFormatException: Could not load file or assembly 'AjaxMin' or one of its dependencies. An attempt was made to load a program with an incorrect format.]
System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) +0
System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) +210
System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection) +242
System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +17
System.Reflection.Assembly.Load(String assemblyString) +35
System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +122

[ConfigurationErrorsException: Could not load file or assembly 'AjaxMin' or one of its dependencies. An attempt was made to load a program with an incorrect format.]
System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +12761078
System.Web.Configuration.CompilationSection.LoadAllAssembliesFromAppDomainBinDirectory() +503
System.Web.Configuration.AssemblyInfo.get_AssemblyInternal() +142
System.Web.Compilation.BuildManager.GetReferencedAssemblies(CompilationSection compConfig) +334
System.Web.Compilation.BuildManager.CallPreStartInitMethods(String preStartInitListPath) +203
System.Web.Compilation.BuildManager.ExecutePreAppStart() +152
System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException) +1151

[HttpException (0x80004005): Could not load file or assembly 'AjaxMin' or one of its dependencies. An attempt was made to load a program with an incorrect format.]
System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +12881540
System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +159
System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +12722601


Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.17929
```

In addition, during building issued the following warning:

```
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1578,5): warning MSB3270: There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "AjaxMin, Version=5.0.5007.14579, Culture=neutral, PublicKeyToken=21ef50ce11b5d80f, processorArchitecture=x86", "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
```
Comments: ** Comment from web user: Taritsyn **

Thanks, everything works!

↧
↧

Closed Issue: Microsoft Ajax Minifier 5.0 problems [20199]

September 17, 2013, 8:15 am
$
0
0
During using the Microsoft Ajax Minifier 5.0 in ASP.NET MVC 4 (.NET 4.0), the following error occurs:

```
Could not load file or assembly 'AjaxMin' or one of its dependencies. An attempt was made to load a program with an incorrect format.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.BadImageFormatException: Could not load file or assembly 'AjaxMin' or one of its dependencies. An attempt was made to load a program with an incorrect format.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Assembly Load Trace: The following information can be helpful to determine why the assembly 'AjaxMin' could not be loaded.


WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].


Stack Trace:


[BadImageFormatException: Could not load file or assembly 'AjaxMin' or one of its dependencies. An attempt was made to load a program with an incorrect format.]
System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) +0
System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) +210
System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection) +242
System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +17
System.Reflection.Assembly.Load(String assemblyString) +35
System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +122

[ConfigurationErrorsException: Could not load file or assembly 'AjaxMin' or one of its dependencies. An attempt was made to load a program with an incorrect format.]
System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +12761078
System.Web.Configuration.CompilationSection.LoadAllAssembliesFromAppDomainBinDirectory() +503
System.Web.Configuration.AssemblyInfo.get_AssemblyInternal() +142
System.Web.Compilation.BuildManager.GetReferencedAssemblies(CompilationSection compConfig) +334
System.Web.Compilation.BuildManager.CallPreStartInitMethods(String preStartInitListPath) +203
System.Web.Compilation.BuildManager.ExecutePreAppStart() +152
System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException) +1151

[HttpException (0x80004005): Could not load file or assembly 'AjaxMin' or one of its dependencies. An attempt was made to load a program with an incorrect format.]
System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +12881540
System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +159
System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +12722601


Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.17929
```

In addition, during building issued the following warning:

```
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1578,5): warning MSB3270: There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "AjaxMin, Version=5.0.5007.14579, Culture=neutral, PublicKeyToken=21ef50ce11b5d80f, processorArchitecture=x86", "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
```
Comments: lesson learned: leave the DLLs as "Any CPU"
↧

Commented Unassigned: Manifest files are not closed properly when using the AjaxMinManifestTask [20273]

October 4, 2013, 7:58 am
$
0
0
I tried using the AjaxMinManifestTask in my SharePoint project in the AfterLayout target in MSBuild in order to minify my scripts in the "pkg" folder structure that is later packaged into deployable WSP-files. This caused the build process to fail with an error message saying that the manifest file was being used by "another process".
I downloaded the code and noticed when debugging and monitoring the file handles with process monitor that the file handle for the manifest file isn't closed when the XmlReader is disposed. After changing the try-catch to a using-block for the StreamReader object, the file handle is closed properly when exiting the outer using-block.
This does, however, cause the code analysis to warn about objects getting disposed twice.
Comments: ** Comment from web user: ronlo **

Well, crud. I had changed from a using a while back because of that warning and how it suggest it be fixed. That'll teach me to pay attention to documentation. I'll put it back to a using; not only does it seem to work better, it's far easier to read and maintain.

↧

Created Unassigned: AjaxMinManifestTask does not respect the -clobber argument [20298]

October 10, 2013, 5:08 am
$
0
0
Sice the SwitchParser doesn't parse the -clobber argument but instead fires the UnknownParameter event that is handled correctly in the MainClass class, but isn't handled in AjaxMinManifestTask.

We are using the AjaxMinManifestTask in our SharePoint projects. To include the minified files in our SharePoint deployment packages (.WSP-files), we need to keep empty versions of the minified files in our projects. This causes the AjaxMinManifestTask to fail with some access denied exception on the TFS Build server since the target files retrieved from the code repository are read-only.

To solve our immediate problem, I changed the AjaxMinManifestTask to always remove the read-only attribute from target files. Not the most elegant solution, but it's good enough for us.
↧
↧

Commented Unassigned: AjaxMinManifestTask does not respect the -clobber argument [20298]

October 10, 2013, 6:59 am
$
0
0
Sice the SwitchParser doesn't parse the -clobber argument but instead fires the UnknownParameter event that is handled correctly in the MainClass class, but isn't handled in AjaxMinManifestTask.

We are using the AjaxMinManifestTask in our SharePoint projects. To include the minified files in our SharePoint deployment packages (.WSP-files), we need to keep empty versions of the minified files in our projects. This causes the AjaxMinManifestTask to fail with some access denied exception on the TFS Build server since the target files retrieved from the code repository are read-only.

To solve our immediate problem, I changed the AjaxMinManifestTask to always remove the read-only attribute from target files. Not the most elegant solution, but it's good enough for us.
Comments: ** Comment from web user: ronlo **

That was done on purpose because I felt it was too dangerous to accidentally clobber source files. But if you have a valid scenario, I'll add the -clobber switch to the task as well.

↧

Commented Unassigned: AjaxMinManifestTask does not respect the -clobber argument [20298]

October 11, 2013, 3:25 am
$
0
0
Sice the SwitchParser doesn't parse the -clobber argument but instead fires the UnknownParameter event that is handled correctly in the MainClass class, but isn't handled in AjaxMinManifestTask.

We are using the AjaxMinManifestTask in our SharePoint projects. To include the minified files in our SharePoint deployment packages (.WSP-files), we need to keep empty versions of the minified files in our projects. This causes the AjaxMinManifestTask to fail with some access denied exception on the TFS Build server since the target files retrieved from the code repository are read-only.

To solve our immediate problem, I changed the AjaxMinManifestTask to always remove the read-only attribute from target files. Not the most elegant solution, but it's good enough for us.
Comments: ** Comment from web user: chipz **

That would be fantastic!
I think the risk for accidental clobbering i pretty low since you have to specify the -clobber switch in the manifest files (if using manifests like we do). In our case, the risk is very close to zero since the output path for the AjaxMinManifestTask is set to the target folder of our build. That way, the source files always remain intact and we eliminate merge issues for minified files since the minified versions of the files are never checked in.

↧

Created Unassigned: Named anonymous function is renamed incorrectly [20309]

October 13, 2013, 7:37 pm
$
0
0
In AjaxMin 4.x, named anonymous function is renamed incorrectly so my code doesn't work after minified. For example:

Before minification:

```
setTimeout(function test() {
dosomething();
setTimeout(test, 1000);
}, 1000);
```

After minification:

```
setTimeout(function () {
dosomething();
setTimeout(f, 1000); // <-- but f is undefined now, so it won't work.
}, 1000);
```

Thanks,
↧
Search

Commented Unassigned: Named anonymous function is renamed incorrectly [20309]

October 13, 2013, 8:45 pm
$
0
0
In AjaxMin 4.x, named anonymous function is renamed incorrectly so my code doesn't work after minified. For example:

Before minification:

```
setTimeout(function test() {
dosomething();
setTimeout(test, 1000);
}, 1000);
```

After minification:

```
setTimeout(function () {
dosomething();
setTimeout(f, 1000); // <-- but f is undefined now, so it won't work.
}, 1000);
```

Thanks,
Comments: ** Comment from web user: ronlo **

That function name is referenced - it shouldn't have been removed. What version, exactly, are you using?

↧
↧

Commented Unassigned: Named anonymous function is renamed incorrectly [20309]

October 13, 2013, 10:37 pm
$
0
0
In AjaxMin 4.x, named anonymous function is renamed incorrectly so my code doesn't work after minified. For example:

Before minification:

```
setTimeout(function test() {
dosomething();
setTimeout(test, 1000);
}, 1000);
```

After minification:

```
setTimeout(function () {
dosomething();
setTimeout(f, 1000); // <-- but f is undefined now, so it won't work.
}, 1000);
```

Thanks,
Comments: ** Comment from web user: Tiendq **

It's 4.67.4639, from ajaxmin.exe file.

↧

Commented Unassigned: Named anonymous function is renamed incorrectly [20309]

October 14, 2013, 8:52 am
$
0
0
In AjaxMin 4.x, named anonymous function is renamed incorrectly so my code doesn't work after minified. For example:

Before minification:

```
setTimeout(function test() {
dosomething();
setTimeout(test, 1000);
}, 1000);
```

After minification:

```
setTimeout(function () {
dosomething();
setTimeout(f, 1000); // <-- but f is undefined now, so it won't work.
}, 1000);
```

Thanks,
Comments: ** Comment from web user: ronlo **

That's a pretty old version. Have you tried a newer one?

↧

Commented Unassigned: Named anonymous function is renamed incorrectly [20309]

October 14, 2013, 8:56 am
$
0
0
In AjaxMin 4.x, named anonymous function is renamed incorrectly so my code doesn't work after minified. For example:

Before minification:

```
setTimeout(function test() {
dosomething();
setTimeout(test, 1000);
}, 1000);
```

After minification:

```
setTimeout(function () {
dosomething();
setTimeout(f, 1000); // <-- but f is undefined now, so it won't work.
}, 1000);
```

Thanks,
Comments: ** Comment from web user: ronlo **

Also, I can't get a repro on 4.67. In a command prompt I typed "ajaxmin -js" and pasted in the code you have above, but the name does not get removed -- it's not renamed, either, since older versions of IE will [incorrectly] put the function expression name in the global namespace. I also tried wrapping the code in a function declaration so that it gets renamed. I pasted in this code:
```
function foo(){
setTimeout(function test() {
dosomething();
setTimeout(test, 1000);
}, 1000);
}
```
and got back:
```
function foo(){setTimeout(function n(){dosomething(),setTimeout(n,1e3)},1e3)}
```

Is there a minimum repro you can send me that I can debug to make _sure_ that this is fixed in later versions?

↧

Commented Unassigned: Named anonymous function is renamed incorrectly [20309]

October 14, 2013, 9:28 am
$
0
0
In AjaxMin 4.x, named anonymous function is renamed incorrectly so my code doesn't work after minified. For example:

Before minification:

```
setTimeout(function test() {
dosomething();
setTimeout(test, 1000);
}, 1000);
```

After minification:

```
setTimeout(function () {
dosomething();
setTimeout(f, 1000); // <-- but f is undefined now, so it won't work.
}, 1000);
```

Thanks,
Comments: ** Comment from web user: Tiendq **

I forgot to tell you that I put it in a function, your test is correct but in my case anonymous function no longer had its (renamed) name. This issue happened when I concat and minified several JS files and got a 180K (minified) JS file.

↧
↧

Commented Unassigned: AjaxMinManifestTask does not respect the -clobber argument [20298]

October 14, 2013, 12:50 pm
$
0
0
Sice the SwitchParser doesn't parse the -clobber argument but instead fires the UnknownParameter event that is handled correctly in the MainClass class, but isn't handled in AjaxMinManifestTask.

We are using the AjaxMinManifestTask in our SharePoint projects. To include the minified files in our SharePoint deployment packages (.WSP-files), we need to keep empty versions of the minified files in our projects. This causes the AjaxMinManifestTask to fail with some access denied exception on the TFS Build server since the target files retrieved from the code repository are read-only.

To solve our immediate problem, I changed the AjaxMinManifestTask to always remove the read-only attribute from target files. Not the most elegant solution, but it's good enough for us.
Comments: ** Comment from web user: ronlo **

This will be in the 5.3 release.

↧

Commented Unassigned: Named anonymous function is renamed incorrectly [20309]

October 23, 2013, 7:11 am
$
0
0
In AjaxMin 4.x, named anonymous function is renamed incorrectly so my code doesn't work after minified. For example:

Before minification:

```
setTimeout(function test() {
dosomething();
setTimeout(test, 1000);
}, 1000);
```

After minification:

```
setTimeout(function () {
dosomething();
setTimeout(f, 1000); // <-- but f is undefined now, so it won't work.
}, 1000);
```

Thanks,
Comments: ** Comment from web user: TheDeeds **

@Tiendq, is it reproducible with Microsoft Ajax Minifier 5.2?

If so then note:

- Your scenario is very unclear.
- Repost the steps to reproduce the bug explicitly.

↧
Search

Commented Issue: Adv. minification suggestions - 2 [19504]

November 2, 2013, 12:04 pm
$
0
0
It would be possible to minify calls to static namespaced methods by replacing the namespaced method into a variable that would be moved to the topmost scope in a function? This of course will only work for explicit static namespaced calls inside function scopes (not on the global scope), so for example:

```
function(){//topmost scope
var a = call.to.another.method();
var j = call.to.another.method;
var b = function(){
var c = call.to.another.method();
var i = j();
}
}

vad d = call.to.another.method();
```
Should be minified as:
```
function(){//topmost scope
var x = call.to.another.method;
var j = call.to.another.method;//not replaced, as it is not a method call...
var a = x();
var b = function(){
var c = x();
var i = j();
}
}
vad d = call.to.another.method();
```

What do you think? Do you believe that would be possible? I'm not sure if you can detect some common patterns that may look similar but are not, like:

```
...
var that = this;
var a = that.method();
...
```
Comments: ** Comment from web user: SoopahMan **

Google's Closure Compiler does exactly this.

http://b9dev.blogspot.com/2013/06/getting-started-with-google-closure-on.html

You should probably just switch to that.

↧

Created Unassigned: NullreferenceException [20417]

November 13, 2013, 5:46 am
$
0
0
In case of invalid syntax JS like something.call(),.call() (see more complete example below) a NullReferenceException is throws (see callstack below).
Code sample
```
if (window.FileReader) {
$(".j_drop", this.get_element()).on("dragover", RFERL.UI.Web.Controls.FileUploaderBehavior._cancel)
.on("dragenter", RFERL.UI.Web.Controls.FileUploaderBehavior._cancel),
.on("drop", Function.createDelegate(this, this._onDrop));
}
```
Call stack
```
Error 363 The "AjaxMin" task failed unexpectedly.
System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.Ajax.Utilities.JSParser.ParseMemberExpression(AstNode expression, List`1 newContexts)
at Microsoft.Ajax.Utilities.JSParser.ParseLeftHandSideExpression(Boolean isMinus)
at Microsoft.Ajax.Utilities.JSParser.ParseUnaryExpression(Boolean& isLeftHandSideExpr, Boolean isMinus)
at Microsoft.Ajax.Utilities.JSParser.ParseExpression(AstNode leftHandSide, Boolean single, Boolean bCanAssign, JSToken inToken)
at Microsoft.Ajax.Utilities.JSParser.ParseExpressionStatement(Boolean fSourceElement)
at Microsoft.Ajax.Utilities.JSParser.ParseStatement(Boolean fSourceElement, Boolean skipImportantComment)
at Microsoft.Ajax.Utilities.JSParser.ParseBlock()
at Microsoft.Ajax.Utilities.JSParser.ParseStatement(Boolean fSourceElement, Boolean skipImportantComment)
at Microsoft.Ajax.Utilities.JSParser.ParseIfStatement()
at Microsoft.Ajax.Utilities.JSParser.ParseStatement(Boolean fSourceElement, Boolean skipImportantComment)
at Microsoft.Ajax.Utilities.JSParser.ParseFunctionBody(Block body)
at Microsoft.Ajax.Utilities.JSParser.ParseFunction(FunctionType functionType, Context fncCtx)
at Microsoft.Ajax.Utilities.JSParser.ParseLeftHandSideExpression(Boolean isMinus)
at Microsoft.Ajax.Utilities.JSParser.ParseUnaryExpression(Boolean& isLeftHandSideExpr, Boolean isMinus)
at Microsoft.Ajax.Utilities.JSParser.ParseObjectLiteralProperty(Boolean isBindingPattern)
at Microsoft.Ajax.Utilities.JSParser.ParseObjectLiteral(Boolean isBindingPattern)
at Microsoft.Ajax.Utilities.JSParser.ParseLeftHandSideExpression(Boolean isMinus)
at Microsoft.Ajax.Utilities.JSParser.ParseUnaryExpression(Boolean& isLeftHandSideExpr, Boolean isMinus)
at Microsoft.Ajax.Utilities.JSParser.ParseExpression(AstNode leftHandSide, Boolean single, Boolean bCanAssign, JSToken inToken)
at Microsoft.Ajax.Utilities.JSParser.ParseExpressionStatement(Boolean fSourceElement)
at Microsoft.Ajax.Utilities.JSParser.ParseStatement(Boolean fSourceElement, Boolean skipImportantComment)
at Microsoft.Ajax.Utilities.JSParser.ParseStatements(Block block)
at Microsoft.Ajax.Utilities.JSParser.InternalParse()
at Microsoft.Ajax.Utilities.JSParser.Parse(DocumentContext sourceContext)
at Microsoft.Ajax.Utilities.Minifier.MinifyJavaScript(String source, CodeSettings codeSettings)
at Microsoft.Ajax.Minifier.Tasks.AjaxMin.MinifyJavaScript(String sourceCode, String sourceName, String outputPath, String mapFilePath)
at Microsoft.Ajax.Minifier.Tasks.AjaxMin.MinifyJavaScript()
at Microsoft.Ajax.Minifier.Tasks.AjaxMin.Execute()
at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__20.MoveNext() D:\Code\common\RFERL.WebControls\RFERL.UI.WebControls.csproj 617 5 RFERL.UI.WebControls

```
↧
↧

Created Unassigned: Unicode problem [20420]

November 14, 2013, 10:01 am
$
0
0
Hello,

Ajaxmin throws exceptions when minifying a Unicode value:
$.Constant({Static:true , Public:false}, "HIGH_SURROGATE_START", "\ud800");
Error : Invalid hexadecimal escape sequence: "\ud800

It seems to process as a string instead of Unicode.

Thanks in advance for your help.
↧

Commented Unassigned: Unicode problem [20420]

November 14, 2013, 1:45 pm
$
0
0
Hello,

Ajaxmin throws exceptions when minifying a Unicode value:
$.Constant({Static:true , Public:false}, "HIGH_SURROGATE_START", "\ud800");
Error : Invalid hexadecimal escape sequence: "\ud800

It seems to process as a string instead of Unicode.

Thanks in advance for your help.
Comments: ** Comment from web user: ronlo **

I'm sorry, but that _IS_ an invalid string. You have a high surrogate with no low surrogate -- it is an invalid Unicode sequence. The error is correct. What is it you're trying to do there? I'd love to suggest a better way to you, but I'm not quite sure what your goal is here.

↧

Commented Unassigned: Unicode problem [20420]

November 15, 2013, 6:56 am
$
0
0
Hello,

Ajaxmin throws exceptions when minifying a Unicode value:
$.Constant({Static:true , Public:false}, "HIGH_SURROGATE_START", "\ud800");
Error : Invalid hexadecimal escape sequence: "\ud800

It seems to process as a string instead of Unicode.

Thanks in advance for your help.
Comments: ** Comment from web user: ronlo **

How about I create a separate error for this condition with a lower severity, so it doesn't show up unless you're analyzing the code or have otherwise bumped the warning threshold up?

↧
Viewing all 683 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>