SetLicense in .Net Core



Upon converting our project that uses Aspose Total to .Net Core (2.2), we have discovered that we are unable to set the Aspose license on any associated libraries (Words, Cells, etc). The original project is an Azure Function product, however, we have since rolled a most basic .Net Core console project to test the issue with same results.

The error we are receiving is:

Could not load type ‘System.Runtime.Remoting.RemotingServices’ from assembly…

Remoting has been removed from .Net Core so my question is whether Aspose is aware of the issue and preferably that there is a fix available.

Thank you.



It seems that the reason of your problem is that minificator does not see code in virtualized methods and as a result it does not include libraries required by this code into the final build. To work the problem around the you can include this option into the project:

      <TrimmerRootAssembly Include="mscorlib" />
      <TrimmerRootAssembly Include="System.Xml" />

Hope this helps you. If you still face problem, please share your working environment along with complete detail of your use case? We will then provide you more information about this query.


Thank you for your reply Tahir. Unfortunately the suggestion given herein does not resolve the issue (in the Azure Function project nor in the standard console one). I’m not sure what further information I may provide other than that I’m using Visual Studio 2017 for this.

Thanks again



Could you please create separate application for Aspose.Words and Aspose.Cells and check for which product you are facing this issue? Thanks for your cooperation.


Hello Tahir,

The first product we’re facing the issue with is Aspose.Words. Its as basic a test application as possible. The main cause for concern is that Remoting Services have been removed from .Net Core (please refer to and Aspose licensing attempts to reference said tech. Have you guys been successful at running .Net Core apps with licensing? If so, may I have a sample to ensure I’m not missing anything obvious.

Thank you for your continued support.



We have logged this problem in our issue tracking system as WORDSNET-19384. We will inform you via this forum thread once there is an update available on it. We apologize for your inconvenience.