This blog helped me configure a build pipeline for react native iOS build:
https://dev.to/staff0rd/building-a-react-native-pipeline-for-android-and-ios-2bo5
I used the code at https://github.com/staff0rd/react-native-pipeline/blob/master/azure-pipelines-ios.yml
In a strange issue, we would get an error while trying to upload an image using multipart async methods in web api.
Finally we found out that the problem was with System.Net.Http.dll versions not working correctly, the problem and solutions are mentioned at
It was resolved after we added this entry to web.config file
<configuration><runtime><assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="System.Net.Http" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" /><bindingRedirect oldVersion="0.0.0.0-4.2.0.0" newVersion="4.2.0.0" /></dependentAssembly></assemblyBinding></runtime></configuration>
Before initial go-live or during maintenance of a website, we would like the website to not be visible to outside users, but at the same time it should be accessible to internal users for verifying deployments etc.
This can be elegantly handled for users using a custom page displaying the message 'website is temporarily down'. In IIS, there is a feature which makes this task much easier. We can simply create an 'App_offline.htm' page and that will display the custom message for all routes. More information can be found at
https://activedirectoryfaq.com/2015/01/iis-maintenance-page-app_offline-htm/
However for search engines and other bots, it helps if we return a '503 Service Unavailable' message. More general information about a correct (and elegant) way to handle maintenance mode can be found at https://moz.com/blog/how-to-handle-downtime-during-site-maintenance.
In my case I wanted to:
After cloning a git repo of dot net framework website and trying to run it all I could see was this error Turns out the fix was to simply e...
