Syncfusion and VS 2003 on Windows Vista

[Bill Langlais]

I installed Syncfusion 4.2.0.37 & 5.1.0.51 on my Windows Vista system. I also have VS 2005. Syncfusion does not show up in 2003 and when I try to open a project that uses it in 2003 it will not open. Everything works fine in 2005.

I am porting an application from 2003 C++ to 2005 C# so I need to see both projects so I can cut and paste stuff.

Anyone know what is wrong?

WJL

[Administrator]

Syncfusion only ships the .Net 2.0 assemblies in the 5.1.0.51 install that is available from the download page of the website. You can download an installation with the 1.1 assemblies from http://www2.syncfusion.com/Installs/v5.1.0.51/syncfusionessentialstudio11setup.exe. It does require the same unlock key that you used for the 2.0 assemblies.

[Bill Langlais]

The link below does not work. Ccan you provide me the correct link?

>Syncfusion only ships the .Net 2.0 assemblies in the 5.1.0.51 install that is available from the download page of the website. You can download an installation with the 1.1 assemblies from http://www2.syncfusion.com/Installs/v5.1.0.51/syncfusionessentialstudio11setup.exe. It does require the same unlock key that you used for the 2.0 assemblies.

[Administrator]

It looks like the hyperlink has a period included for some reason (likely my error in copying it). Here it is without the period and this works for me.

http://www2.syncfusion.com/Installs/v5.1.0.51/syncfusionessentialstudio11setup.exe

[Bill Langlais]

Hi,

That fixed it and the project now opens. The problem now is I always get the licensing error when I try to run. I have tried deleting the debug directory and rebuiling. Exiting VS 2003 before the rebuild. Nothing seems to help.

>It looks like the hyperlink has a period included for some reason (likely my error in copying it). Here it is without the period and this works for me.

http://www2.syncfusion.com/Installs/v5.1.0.51/syncfusionessentialstudio11setup.exe

[Administrator]

Try removing the license.licx file from the project, and then rebuild the project letting the licx file be regenerated in the process as if this were the first time you included any Syncfusion DLLs in the process.

[Bill Langlais]

Where is the file? It is not in my project direcory or where the obj and exe file is

>Try removing the license.licx file from the project, and then rebuild the project letting the licx file be regenerated in the process as if this were the first time you included any Syncfusion DLLs in the process.

[Administrator]

I am not sure how you have included the file in your C++ application. It must be included as an embedded resource in a C# project. So, in Solution Explorer, if you click the Show All Files button, it should show you the licenses.licx file in the C# project files tree.

[Administrator]

Here is a KB on manually adding licensing to a managed C++ application.
http://www.syncfusion.com/Support/article.aspx?id=10464

[Bill Langlais]

The problem with the KB article it refers to a program lc.exe that is not in the Syncfusion directories. I did find a License Enable program and when I run it it says it is doing something but it does nothing. I have also tried to use the console version and I try it with the command arguments for LC.exe and it crashes.

So I cannot get rid of the licensing error in the C++ project on either Windows XP or Windows Vista. I do not have any problems on the C# version.

>Here is a KB on manually adding licensing to a managed C++ application.
http://www.syncfusion.com/Support/article.aspx?id=10464

[Administrator]

The lc.exe is not part of the Syncfusion libraries. It is shipped as part of the Framwwork SDK.
http://msdn2.microsoft.com/en-us/library/ha0k3c9f(vs.80).aspx

If that link does not appear, type lc.exe into a google search screen and click the msdn help screen link that should be among the hits.

On my system, lc.exe is found here:
C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin

If you do not have any luck using lc.exe to embed the license file into your C++ project, you should submit a Direct Trac support incident so an installation support engineer can arrange a remote session to access your computer and check out why things ares not working.