I was asked once by a client to build some functionality that allowed editors to create forms on the fly without developer effort. EPiServer did the work for us. Here’s an overview on Forms. Out of the box EPiServer Forms boast the following form elements ready to use: Text, Text Area, Number, DateTime, Range, Url,… Continue reading EPiServer Forms – Quick Start
System.InvalidOperationException: Cannot find compilation library location for package ‘Microsoft.AspNetCore’ Most likely you’ve upgraded your aspnetcore version and you have not cleared the existing files before deployment. If you’re using Azure DevOps as your build and release server you can enable “Remove Additional Files at destination” on your release step.
Whilst upgrading from AspNetCore 2.0 to 2.1, some of the StartUp configuration had changed slightly and part of the upgrade required me to refactor code into the webhost builder. However as a result I didn’t quite do everything and after deploying to azure web app, I was hit with a 502 response. An exception being… Continue reading AspNetCore Debugging Startup issue in Azure Web App
Anyone updating to AspNetCore 2.1.3 to an Azure Web App may want to hold off. Azure Deployments hasn’t been updated yet and is scheduled to be completed in a weeks time. Downgrade to Microsoft.AspNetCore.App 2.1.0 for now. Source: https://blogs.msdn.microsoft.com/dotnet/2018/08/21/net-core-august-2018-update/
This particular nugget has screwed with me for a few days. When attempting to run a standard EPiServer Find index, my log files were getting flooded with this: An exception occurred while indexing (Content): MapperParsingException[failed to parse [Blocks.Items.Blocks.Items.DefaultPrice.UnitPrice.Currency]]; nested: ElasticSearchIllegalArgumentException[unknown property [CurrencyCode$$string]]; . Contact episerver support to get them to move your index to a… Continue reading EPiServer Find Index – unknown property
Getting the above issue on your local machine? Install WebSocket Protocol via Windows Add/Remove Features. Should solve your issue.
Visual Studio release notes as of 7th March release notes state that the DotNetCLITools packages cannot currently be managed by the Nuget Package Manager and must be edited manually in the csproj. After migrating my current projects, I finally figured out that it wasn’t just me that was struggling to find the place to manage… Continue reading Visual Studio 2017 – Add, Remove or Update DotNetCLITools references – 7th March 2017