We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy. (Last updated on : Nov 16th 2018).
Unfortunately, activation email could not send to your email. Please try again.
Syncfusion Feedback

Deploying my custom built libraries in v4.4.0.51

Thread ID:

Created:

Updated:

Platform:

Replies:

57786 Mar 11,2007 12:59 PM UTC Mar 20,2007 08:30 PM UTC General Discussion 4
loading
Tags: General Discussion
Radmand
Asked On March 11, 2007 12:59 PM UTC

Hi
I am working with Syncfusion v4.4.0.51 and i have modified and build some of its projects.
When we were using Essential Suite v2.1.0.9 the following item of your Knowledge-Base helped us to resign assemblies:
http://www.syncfusion.com//support/kb/studio/Default.aspx?ToDo=view&questId=16
but it seems that in v4.4.0.51, and in .net framework SDK v2.0, the structure of licensing is totally changed.
What should we do now?

Kumaresh [Syncfusion]
Replied On March 12, 2007 09:58 PM UTC


Hi Radmad,

Please refer the following KB article for some tips on deploying the application.

http://www.syncfusion.com/support/kb/studio/Default.aspx?ToDo=view&questId=40

Kindly try this and let me know if this helps.

Thank you for using Syncfusion products.

Regards,
Kumaresh.

Radmand
Replied On March 13, 2007 05:34 AM UTC

Dear Kumaresh
I do not have any problem with prebuilt syncfusion libraries. My problem starts when i want to change some of Syncfusion codes and use my custom built Syncfusion dlls. in Essential Suite we were signing Syncfusion libraries with our Public keys. but What should i do with v4.4.0.51 to be able to Change some of your codes and use them in my Application?

>
Hi Radmad,

Please refer the following KB article for some tips on deploying the application.

http://www.syncfusion.com/support/kb/studio/Default.aspx?ToDo=view&questId=40

Kindly try this and let me know if this helps.

Thank you for using Syncfusion products.

Regards,
Kumaresh.

Ramu [Syncfusion]
Replied On March 16, 2007 11:50 AM UTC

Hi Radmad,

Please refer to ‘Important licensing changes (if you are migrating from a version lesser than 3.2)’ topic in online documentation about licensing changes in 4.4 version from prior version 3.2.

http://www2.syncfusion.com/library/default.aspx

Kindly navigate to the following topic (Essential studio -> Essential started -> what’s new?) to view the licensing.

You could follow the same KB article as you mentioned in forum, to create your custom built Syncfusion dlls.

Please let me know if you have any queries.

Regards,
Ramu

Daniel Jebaraj [Syncfusion]
Replied On March 20, 2007 08:30 PM UTC

Hi Radmand,

You will need to set DelaySign to false in AssemblyInfo.cs. You will also need to change key information provided in the same file.

[assembly: AssemblyDelaySign(true)]
[assembly: AssemblyKeyFile("../../../sf.publicsnk")]

Other than this no other changes should be required. Please note that you should rebuild all dependencies in the same manner.

Best regards,
Daniel
Syncfusion, Inc

>Dear Kumaresh
I do not have any problem with prebuilt syncfusion libraries. My problem starts when i want to change some of Syncfusion codes and use my custom built Syncfusion dlls. in Essential Suite we were signing Syncfusion libraries with our Public keys. but What should i do with v4.4.0.51 to be able to Change some of your codes and use them in my Application?

>
Hi Radmad,

Please refer the following KB article for some tips on deploying the application.

http://www.syncfusion.com/support/kb/studio/Default.aspx?ToDo=view&questId=40

Kindly try this and let me know if this helps.

Thank you for using Syncfusion products.

Regards,
Kumaresh.

CONFIRMATION

This post will be permanently deleted. Are you sure you want to continue?

Sorry, An error occured while processing your request. Please try again later.

Warning Icon You are using an outdated version of Internet Explorer that may not display all features of this and other websites. Upgrade to Internet Explorer 8 or newer for a better experience.Close Icon

;