docs(common): still see trial version

Author: marin-bratanov

upgrade/overview.md

@@ -65,10 +65,36 @@ If you have just purchased a license and you need to migrate from the trial pack
         -->
         <script src="_content/telerik.ui.for.blazor/js/telerik-blazor.js" defer></script>
 
+The Trial version of our assembly has the `Telerik.Blazor Trial version` Title. You can see it by Right clicking the assembly > Properties > File Description. You can find the assembly by extracting the `.nupgk` file like a `.zip` archive, or in the publish location.
+
 ## Troubleshooting
 
+## Microsoft.JSInterop.JSException: Could not find ...
+
 The most common problem you will encounter when upgrading is wrong references to our JS Interop file. You can read more about fixing them in the [Troubleshoot JavaScript Errors]({%slug troubleshooting-js-errors%}) article.
 
+## I Still See the Trial Message
+
+If you have a license, but you still see the trial message, especially after publishing an app to a staging or live server, the `Telerik.Blazor.dll` assembly that the build used is still the trial one.
+
+> Thank you for using the Trial Version of Telerik UI for Blazor to build more powerful applications faster. Purchase the Commercial Version now to get access to all product updates and the Telerik expert support.
+
+The most common reason for the problem is that the framework decides to incorrectly copy a trial version of our assembly into the `dist` folder of the app, even though it puts the correct licensed version at the root of the publish folder. This seems like a problem in the build process of the framework, and hopefully it will get fixed in future versions.
+
+To fix this in the meantime, try the following process (you can try a new test build after each step where you make a change):
+
+1. Ensure that the licensed package is referenced in the project (`Telerik.UI.for.Blazor` instead of `Telerik.UI.for.Blazor.Trial`). Make sure this is also the case on the build machine. Sometimes a failed build or locked files may prevent a file from being updated and so the build machine may be using a trial reference.
+
+1. Uninstall any Trial installations from the build machine, dev PC and live server.
+
+1. If you have created local NuGet feeds, ensure they do not contain Trial versions of our packages.
+
+1. [Clean the NuGet packages](https://docs.microsoft.com/en-us/nuget/consume-packages/managing-the-global-packages-and-cache-folders#clearing-local-folders) on the build machine, dev PC and live server.
+
+1. Clean the projects.
+
+1. Delete the `bin` and `obj` folders where packages and assemblies may be cached.
+
 
 ## See Also