Split assemblies for server side use

[Scott Waye]

Hi,

 

I'd like to suggest you split your assemblies so they are more efficient for server side use.  Currently if you want to do some PDF processing on the server from the namespace `Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Streaming` you end up loading presentation framework dlls on the server which is unnecessary.  If you look at the manifest for Telerik.Windows.Documents.Core.dll you will see

 

.assembly extern PresentationFramework
{
  .publickeytoken = (31 BF 38 56 AD 36 4E 35 )                         // 1.8V.6N5
  .ver 4:0:0:0
}
.assembly extern System.Xaml
{
  .publickeytoken = (B7 7A 5C 56 19 34 E0 89 )                         // .z\V.4..
  .ver 4:0:0:0
}
.assembly extern System.Drawing
{
  .publickeytoken = (B0 3F 5F 7F 11 D5 0A 3A )                         // .?_....:
  .ver 4:0:0:0
}
.assembly Telerik.Windows.Documents.Core
{

This ends up loading unnecessary dlls, including System.Windows.Forms in IIS (if you are hosting the server in IIS).

[Dimitar]

Hi Scott,

For such cases, you can use the assemblies for NET Standard because they do not depend on any Windows assemblies. You will need a .NET Core application as well. The difference is that the .NET Standard assemblies do not have Windows in their name.  Detailed information is available here: NuGet packages.

Let me know how this works for your case.

Regards,
Dimitar
Progress Telerik

[Scott Waye]

Thanks, not sure how the password for the nuget feed is going to work in CI/Azure Devops, but that's a different question.

[Dimitar]

Hello Scott,

You can download the assemblies from your account as well. The NET Standard assemblies are shipped with the products they are used with (Xamarin, Blazor).

Let me know if I can assist you further.

Regards,
Dimitar
Progress Telerik