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,
We would like to make some changes to the source for the Syncfusion grid/formula code to make it work better within our application. Specifically we have issues with the use commas in the GetCellsFromArgs method of the GetFormulaCell class etc, but this may not be our only change.
My question is, if we make changes to the source code (which I presume we''re allowed to do after having purchased it, since we have bought the source), should we rename all the assemblies/namespaces so we''re not deploying something that looks like the original Syncfusion code but behaves differently ? My concern is that, should the assemblies be shared during deployment (i.e loaded in the GAC or shared path etc) then we could break other apps.
Of course we could place our specific copies of the Syncfusion assemblies in our own install folder and that would avoid sharing them, but since they''d still have the same name I''m still concerned it may cause confusion when trying to support our clients.
What is the recommended practice in this case ? Does the license agreement allow for any of this ?
Thanks in advance.
ADAdministrator Syncfusion Team December 6, 2005 10:45 PM UTC
Not sure what issues you have with commas, but the GridFormulaEngine class has static members GridFormulaEngine.ParseArgumentSeparator and GridFormulaEngine.ParseDecimalSeparator members that may be useful to you.
If you purchased the source code, you can modify it and rebuild the modified code. But to deploy the DLLs, you will have to sign the assemblies with your own keys. You can look in the AssemblyInfo files for comments on how to do this. You can also check out this forum thread. http://www.syncfusion.com/Support/Forums/message.aspx?MessageID=9496