22. May 2018
psql ERROR: character with byte sequence in encoding "WIN1252" has no equivalent in encoding "UTF8"
SET CLIENT_ENCODING TO 'utf8';
9. May 2018
<<Reference Include="netstandard, Version=126.96.36.199, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51">
<HintPath>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\Microsoft.NET.Build.Extensions\net461\lib\netstandard.dll</HintPath>
12. April 2018
a 'rewrite' from: https://stackoverflow.com/questions/44844798/could-not-load-file-or-assembly-system-valuetuple-version-0-0-0-0-or-one-of-i
System.IO.FileLoadException: 'Could not load file or assembly "System.ValueTuple, Version=0.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51" or one of its dependencies. The definition of the assembly manifest found does not match the reference to the assembly.
this should result in automated rewrite in ap.config / web.config that is an equivalent to:
<assemblyidentity name="System.ValueTuple" publickeytoken="cc7b13ffcd2ddd51" culture="neutral"></assemblyidentity>
<bindingredirect oldversion="0.0.0.0-188.8.131.52" newversion="184.108.40.206"></bindingredirect>
9. January 2018
Just wasted way too much time for this:
The Entity Framework provider type 'Npgsql.NpgsqlServices, EntityFramework6.Npgsql' registered in the application config file for the ADO.NET provider with invariant name 'Npgsql' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information.
Obvious perhaps, but not so much anymore while being sure EntityFramework6.Npgsql has been installed... My project used to work a while ago and I could swear I had all the refs intact. After all it would not work otherwise, right...
Anyway, apart from making sure DbProviderFactories and providers are configured, just dbl check EntityFramework6.Npgsql is actually installed / output. If not reinstalling from nuget is a good start. Did work for me ;)
18. October 2017
just a reminder
rewrite from: https://stackoverflow.com/questions/6939150/web-deployment-task-build-failed via https://asoftwareguy.com/2012/05/03/msdeploy-and-when-it-just-stops-working/
Error: (build date) An error occurred when the request was processed on the remote computer.
Error: Unable to perform the operation. Please contact your server administrator to check authorization and delegation settings.
I encountered the same issue when building via TFS. When I tried to manually import the website I got a more informative error: "not able to log on the user \WDeployConfigWriter".
Turns out that when you install web deploy it sets up two local accounts WDeployConfigWriter and WDeployAdmin. The passwords on these accounts are set to expire. So reset the passwords on the web server and set to "never expire". Then go to Management Service Delegation in IIS. Each of the presented rules has a UserName field. Where it is WDeployAdmin or WDeployConfigWriter right click and update the credentials to the new passwords.
A full explanation with screenshots can be found here: http://workinghardinit.wordpress.com/2011/07/18/wdeployconfigwriter-account-issues-trouble-shooting-web-deploy-2-0-with-lessons-learned/