-
Notifications
You must be signed in to change notification settings - Fork 654
Failure to deploy DLLs copied into \bin with a pre/post build event for .NET application #943
Comments
This is not really a Kudu issue, but an issue with how this package deploys its native binaries. See these steps to repro the same issue on your local machine. The Microsoft.SqlServer.Compact package also installs native binaries, but does it in a way that works correctly during deployment. Maybe the LibGit2Sharp package can do something similar? /cc @nulltoken |
@davidebbo Thanks for keeping me in the loop! I've found this (thanks to a google search). Is this the workaround you're referring to? I'd be happy to make LibGit2Sharp apply some similar magic, but, from a licencing perspective, am I allowed to /cc @martinwoodward |
From the licensing stand-point I wouldn't have concerns with this getting added to LibGit2Sharp |
Yes, this is the exact Microsoft.SqlServer.Compact example I was referring to, and I verified that it works correctly with VS deployment (and Kudu). |
We're working on tackling this in libgit2/libgit2sharp#700 |
Fixed in libgit2/libgit2sharp#821 |
Great, closing this one then! |
I've noticed that when deploying a new .NET application that has unmanaged DLLs copied in via a pre/post build event (tried both), kudu does not include those files in the list of files synced to an Azure Website.
Repository reproducing this:
http://github.com/MattDavies/KuduSyncReproduction.git
Created as follows:
Generating deployment script output:
Running deployment command output:
@Gissues:{"order":61.53846153846134,"status":"backlog"}
The text was updated successfully, but these errors were encountered: