Skip to content

Commit b53fe5a

Browse files
ntachevaikoevska
andauthored
docs(common): update intro docs to mention trial watermark and banner (#1838)
* docs(common): update intro docs to mention trial watermark and banner * Update introduction.md Co-authored-by: Iva Stefanova Koevska-Atanasova <[email protected]> * Update introduction.md Co-authored-by: Iva Stefanova Koevska-Atanasova <[email protected]> * Update upgrade/overview.md Co-authored-by: Iva Stefanova Koevska-Atanasova <[email protected]> * chore(common): address feedback * chore(common):final fixes --------- Co-authored-by: Iva Stefanova Koevska-Atanasova <[email protected]>
1 parent 4f2b3a5 commit b53fe5a

File tree

2 files changed

+9
-3
lines changed

2 files changed

+9
-3
lines changed

introduction.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,9 @@ Use [our feedback portal](https://feedback.telerik.com/blazor) to tell us which
6363

6464
## Trial Version and Commercial License
6565

66-
UI for Blazor is a commercial UI library. You are welcome to explore its full functionality and get technical support from the team when you register for a free 30-day trial. To use it commercially, you need to <a href="https://www.telerik.com/purchase/blazor-ui" target="_blank">purchase a license</a>. Feel free to review the Telerik UI for Blazor <a href="https://www.telerik.com/purchase/license-agreement/blazor-ui" target="_blank">License Agreement</a> to get acquainted with the full terms of use.
66+
UI for Blazor is a commercial UI library. You are welcome to explore its full functionality and get technical support from the team when you register for a free 30-day trial. While using the trial package, a watermark and banner will appear over the rendered components.
67+
68+
To use UI for Blazor commercially, you need to <a href="https://www.telerik.com/purchase/blazor-ui" target="_blank">purchase a license</a>. Feel free to review the Telerik UI for Blazor <a href="https://www.telerik.com/purchase/license-agreement/blazor-ui" target="_blank">License Agreement</a> and get acquainted with the full terms of use.
6769

6870

6971
## Support Options

upgrade/overview.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -101,12 +101,14 @@ The Trial version of our assembly has the `Telerik.Blazor Trial version` Title.
101101

102102
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.
103103

104-
## I Still See the Trial Message
104+
## I Still See the Trial Watermark and Banner
105105

106-
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.
106+
While using a trial license, a watermark will be rendered over the components and you will see a banner with the following message:
107107

108108
> 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.
109109
110+
If you have a commercial license, but you still see the trial watermark and banner, especially after publishing an app to a staging or live server, your build has used the trial `Telerik.Blazor.dll` assembly.
111+
110112
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.
111113

112114
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):
@@ -123,6 +125,8 @@ To fix this in the meantime, try the following process (you can try a new test b
123125

124126
1. Delete the `bin` and `obj` folders where packages and assemblies may be cached.
125127

128+
1. Re-build your project.
129+
126130

127131
## See Also
128132

0 commit comments

Comments
 (0)