The type 'WordDocument' exists in both 'Syncfusion.DocIO.Base, Version=16.2460.0.46, Culture=neutral, PublicKeyToken=3d67ed1f87d44c89' and 'Syncfusion.DocIO.Portable, Version=16.2200.0.46, Culture=neutral, PublicKeyToken=3d67ed1f87d44c89'
The type 'FormatType' exists in both 'Syncfusion.DocIO.Base, Version=16.2460.0.46, Culture=neutral, PublicKeyToken=3d67ed1f87d44c89' and 'Syncfusion.DocIO.Portable, Version=16.2200.0.46, Culture=neutral, PublicKeyToken=3d67ed1f87d44c89'
|
Target framework |
|
Package Name |
NuGet feed source |
|
.NET Framework |
|
Syncfusion.DocIO.Base
Syncfusion.Pdf.Base
Syncfusion.Presentation.Base
Syncfusion.XlsIO.Base |
Issue still not resolved
In your last all latest chat you gave reference for asp.net core and we are not suing asp.net core.
We have application in asp.net MVc net framewprk in C#.
As per your initial conversion you gave one link. we can not convert our existing application with below given link which sent by you.
Getting Started with ASP.NET MVC Component | Syncfusion
But we are planning sample application using your given link to compare reference difference with our existing application.
But we can not create even application using snfusion as.net mvc . since last 30 minb my screen it stuck at creating project application. please check the screenshot in zip file
Hopefully you can understand our concern as give you best support to us which encourage us to buy your product.
Thas
Hi Jolly,
Please find the response to the query you mentioned above:
Query 1: The issue is still not resolved.
There is already a support ticket open under your account for this query. Please follow the support ticket.
Query 2: In your last chat, you referenced ASP.NET Core, but we are not using ASP.NET Core.
We have created a separate ticket for your query under your account. Please follow the ticket for further updates.
Regards,
Kalavathi Nallathambi
That error usually happens when the Syncfusion. Licensing assembly isn’t properly referenced or the version mismatch occurs. Installing the exact matching version of the licensing package normally fixes it, but sometimes doing a clean rebuild and clearing the NuGet cache helps too. I ran into something similar while testing tool for Roblox executor, and making sure all dependencies were aligned solved it.
Hi Sara,
Thank you for the update regarding the licensing issue, and for the insights
and troubleshooting steps shared.
Regards,
Kathiresan.