I already fixed this

@SLaks, now it will log the exception message. AFAICR, it was throwing NullReferenceException.

When / why?

@am11 These fixes for the LESS source maps are different from the ones @SLaks committed earlier. Should this still be merged as is?

@SLaks, This

@madskristensen, I pulled and rebased the changes. Now its ready for merging. :)

@madskristensen, @SLaks,

I have a question regarding C# syntax.

Is there a way to add parameter Alias to function via decorator / attribute? Like for PowerShell, we have [Alias()].

Case in point is JsHintCompiler. If we make it node driven, then the second parameter of NodeExecutorBase.Compile(string, string); namely targetFileName would act like configurationFileName (c:\path\to\WEsettingsDirectory.jshintrc): Ditto signature but the parameter is multipurpose (as we immediately pass it to GetArguments method; an abstract method which is overridden by derived classes and this is where we have the context to resolve the purpose / meanings of parameters.

Rarely we get into such situations. I was hoping if language supports it? Instead we can use a method overload and a third parameter. But logically, it would always be parameter2 XOR parameter3.

Not very ideal, but is aliasing parameters a legit design from the OO patterns POV? I guess this will not violate any Language Design or Code Analysis rule either.

If its not supported, I am planning to make a feature request with .NET team. Is it a good idea?

No such feature exists.

You could create a public new CompilerResult Compile(string, string) with different parameter names that calls the base version, and misuses the base parameter.

@SLaks, thanks for your input. I have submitted this request on Connect. https://connect.microsoft.com/VisualStudio/feedback/details/812838/parameter-name-aliases-in-c