The Syncfusion native Blazor components library offers 70+ UI and Data Viz web controls that are responsive and lightweight for building modern web apps.
.NET PDF framework is a high-performance and comprehensive library used to create, read, merge, split, secure, edit, view, and review PDF files in C#/VB.NET.
Hi,
after some hours of digging through my resx/licx files and sources I have finally had the chance to run our system compiled against the 3.0.1.0 release of the suite.
What I''d like to know is whether there is any chance of getting some utility with future releases that will:
- Walk through resx files and fix assembly references if assemblies are broken up into pieces or renamed
- Do the same to licx files
- Perform the required Grid updates
- Accept VS.NET Solution files as input etc.
I had a very bad time walking through our 61 projects solution of which around half of the projects are referencing Syncfusion components only to find out that there seem to be a couple of issues with the 3.0.1.0 release. I do not want to go back to 2.1.0.15 as I do not feel the need to go through the migration hassle again.
Any help/thoughts on this would be highly appreciated
Regards
Kai Iske
ADAdministrator Syncfusion Team January 4, 2005 05:34 PM UTC
I went through the same situation. I took me hours to manually fix the resx files and license files.
It will be highly appreciated if such utility will be available in the future.
Regards,
Jinlin
>Hi,
>
>after some hours of digging through my resx/licx files and sources I have finally had the chance to run our system compiled against the 3.0.1.0 release of the suite.
>
>What I''d like to know is whether there is any chance of getting some utility with future releases that will:
>
>- Walk through resx files and fix assembly references if assemblies are broken up into pieces or renamed
>- Do the same to licx files
>- Perform the required Grid updates
>- Accept VS.NET Solution files as input etc.
>
>I had a very bad time walking through our 61 projects solution of which around half of the projects are referencing Syncfusion components only to find out that there seem to be a couple of issues with the 3.0.1.0 release. I do not want to go back to 2.1.0.15 as I do not feel the need to go through the migration hassle again.
>
>Any help/thoughts on this would be highly appreciated
>
>Regards
>
>Kai Iske
