Closed rainabba closed 9 years ago
It'd be a nice addition. Go ahead sending me the PR when it's available.
I actually need this as well. Have you made any progress @rainabba ?
No. Other issues related to combres brought my site down so I had to pull it in a hurry and just setup a Grunt workflow instead that runs with my build. It was no more work than either of the runtime solutions and is far more efficient. On Aug 22, 2014 8:37 AM, "Kyle Merritt" notifications@github.com wrote:
I actually need this as well. Have you made any progress @rainabba https://github.com/rainabba ?
— Reply to this email directly or view it on GitHub https://github.com/buunguyen/combres/issues/35#issuecomment-53076163.
After hours of head-banging, I realized that resource paths cannot contain wildcards and the "*" in my paths (works with every other minifier/concatonator I've used) was causing the exception. Catching this exception and mentioning the literal path causing the issue in the exception data would make this infinitely easier to address.
Also, what about wildcards? No support using the typical characters; what about including all resources (css or js based on the resourceSet type) in a folder; possible? Would only have to detect that the path is a folder then parse all the files matching the appropriate extension and include them.
Looks like it wouldn't take too much work in API/WebExtensions.cs to accomplish both of these things. I will see if I can do it and submit a pull request unless you reply and say otherwise.
See below for stack trace and example combres.xml that will throw the exception
App_Data\combres.xml