Darren Kopp

@marinswk as far as I know, libsass still doesn't support unc paths. Usually azure web applications have acess to local file system though, so if you are deploying the scss...

Where are you using this at (http handler, etc). The first thing that stands out is the static variable `_customImportDelegate`. I don't think that is re-usable across multiple requests /...

I'm sure I could reproduce this problem if I tried as this happens with basically all native interop and I have encountered this issue before with the sql server binaries...

You are correct. In defense of that statement I'm sure it was last modified when libsass-net was being updated actively. However, libsass-net has not been updated since a point where...

You can get it from the error properties from [SassResult](https://github.com/sass/libsass-net/blob/master/LibSass.NET/Compiler/SassResult.cs)

@nschonni That's how it did it in the past, but it really makes the nuget packaging story pretty painful for downstream libraries that then had to split their packages into...

Are you using the handler exclusively? I hadn't considered adding caching as it's usually only used in the debugging scenario, but I guess it's possible people are using it directly.

So, the biggest difficulty here would be knowing if the file was still good or not when you are using partials because unfortunately we don't know what's going into the...

Are you using the handler directly, or are you using the bundling stuff? I think it's probably possible to add cache watching like that in general for development purposes. things...

> > there can be issues when people run off a network share > To be honest, I didn't think about it. Are you sure it would be an issue?...