When building an e-commerce solution it is important to have the correct delivery details of your customers. By doing so you ensure the orders are being sent to the correct address, decreasing the number of lost parcels and returns. Your customers will be happy and in turn, you will be happier. There are a number of service providers that can help you complete and validate your customers details. The most typical application is to lookup an address from a partial entry, helping a user complete their details, speeding up the process of registration.
When we are implementing an EPiServer web site (or any other software solution) it is imperative to have good error handling. EPiServer uses log4net for its error handling so it is natural to use it as the logging framework for your application. If your website is not behaving properly, you want to know about it and act accordingly. This is a good habit to have and it is a best practice in software development.
Recently we faced a problem where an application would build and run in debug mode but it would not do the same in release, throwing the following error at the end of a build. sgen = http://msdn.microsoft.com/en-us/library/bk3w6240(v=VS.100).aspx Knowing that sgen is responsible for generating the xml serialisation assembly for the application, the error was most likely related to an assembly that was injected during runtime into the AppDomain, in release mode.
some pages would randomly fail to load and a deadlock exception would be thrown from EPiServer.DataAccess.DatabaseFactory: “Failing because of deadlock.”
