Richard Szalay

Interesting. Looking the NuGet.targets, the content files _should_ get published. I wonder if it doesn't follow that path when running via a legacy (non-SDK) csproj

In which case, solving it for _Website_ should be simple enough as we can trigger the same target and/or Task that gets used by sdk projects. Modules will be more...

I'll look into it again as soon as I can. If either of you want to do the same, to figure it what's executing I recommend the MSBuild binary log...

I've had a little time to investigate this further: Files in `content/` are not supported at all in the PackageReference model. Since the're used by Unicorn and pretty much every...

My only issue is that supporting it _properly_ (ie. without breaking a bunch of packages), we'd have to reimplement all of the tokenisation transform support. `content/` is much easier to...

Here's my plan for the implementation: 1. Create a custom task that: 1. Parses the lock file (from `$(ProjectLockFile)`) 2. Finds packages that haven't been excluded (possibly via a custom...

Hi Neil, I unfortunately don't have the capacity at the moment to work on HPP (since I'm no longer in the Sitecore space, I don't even use it at work)....

As an alternative, what if write fails were caught and the contents were instead saved to a temp file (the location of which was included in the error message)?

I'm starting to look into this now and I don't actually think the `FileSystem` publish actually supports URLS. In `Microsoft.Web.Publishing.Deploy.FileSystem.targets`, you can see this: ``` http:// True ``` Which seems...

The intention of `-Loopback` isn't to block the host, it's to route it to the local machine via the loopback address. I wasn't aware of using `0.0.0.0` to block hosts,...