Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I was running npgsql 2.0.13 beta (December 2013) on <strong>AppHarbor</strong> and was getting hosed by this issue for a little while, till I discovered that it's not needed if you're running the latest assembly and don't care about bindingRedirects - it's a dll generated by the .net AL.exe/assembly linker tool to roll up the contents of the policy.2.0.Npgsql.config file (check out <a href="https://github.com/npgsql/Npgsql/blob/master/src/policyFileBuild.bat" rel="nofollow">https://github.com/npgsql/Npgsql/blob/master/src/policyFileBuild.bat</a> to see how that's compiled). </p> <p>MY CONFIGURATION:<br> VS2012<br> .net 4.5<br> MVC4<br> Entity Framework 6 (<em>installed via nuget package restore</em>)<br> npgsql - 2.0.13.91 (<em>installed via nuget package restore</em>) </p> <p>THE HACKY FIX:<br> By Deleting it from the build as a post build event (Project Menu --> Properties --> Build Events --> Post Event Command Line), you can bypass the error (which I don't know why doesn't work on <strong>AppHarbor</strong>). </p> <p>So add this nonsense: </p> <pre><code>del $(TargetDir)policy.2.0.Npgsql.dll /F del $(TargetDir)policy.2.0.Npgsql.config /F dir $(TargetDir) del $(TargetDir)_PublishedWebsites\&lt;appname/&gt;\bin\policy.2.0.Npgsql.dll del $(TargetDir)_PublishedWebsites\&lt;appname/&gt;\bin\policy.2.0.Npgsql.config dir $(TargetDir)_PublishedWebsites\&lt;appname/&gt;\bin\ </code></pre> <p>This is probably over-kill, but note that the <strong>dir</strong> dos command statement gives you feedback on the contents of your directories to make sure the files have actually been deleted. This is viewable from Show Log of build activities in <strong>AppHarbor</strong>. </p> <p>Regarding the 2 sets of deletes on dll and config from that god awful msbuild packaging routine (/output directory and the /output/_PublishedWebsites) - IMHO - it's better to be thorough if you're killing stuff, but it may be sufficient to simply delete only from _publishedwebsites...</p> <p>When it gets built in <strong>AppHarbor</strong>, this will chuck it from the targeted deployment. You might have to wait for a few minutes for the deploy to complete, but it's absence from the deploy will unblock you. </p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload