Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Languages / Managed C++ / March 2005

Tip: Looking for answers? Try searching our database.

licensing

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Ray Hayes - 13 Feb 2005 22:19 GMT
I was having a really annoying problem getting some components I bought from
ComponentOne to work. I found this posting in their knowledge base which
seems to fix the problem. Is there a better workaround from Microsoft though
? It's a pain to keep adding these custom build steps.

It seems there is a bug in VC++ 2003. The licenses.licx is ignored during
the build process, therefore the licensing information is not included in
VC++ applications.

To fix this problem, extra steps must be taken to compile the licensing
resources and link them to the project. Note the following:

1.   Build the C++ project as usual. This should create an exe file and also
a licenses.licx file with licensing information in it.

2.   Copy the licenses.licx file from the app directory to the target folder
(Debug or Release).

3.   Copy the C1Lc.exe utility and the licensed dlls to the target folder.
(Don't use the standard lc.exe, it has bugs.)

4.   Use C1Lc.exe to compile the licenses.licx file. The command line should
look like this:

c1lc /target:MyApp.exe /complist:licenses.licx /i:C1.Win.C1FlexGrid.dll

5.   Link the licenses into the project. To do this, go back to Visual
Studio, right-click the project, select properties, and go to the
Linker/Command Line option. Enter the following:

/ASSEMBLYRESOURCE:Debug\MyApp.exe.licenses

6.   Rebuild the executable to include the licensing information in the
application.



Signature

Ray Hayes
http://www.rhbe.net

Severian - 14 Feb 2005 05:35 GMT
>I was having a really annoying problem getting some components I bought from
>ComponentOne to work. I found this posting in their knowledge base which
[quoted text clipped - 30 lines]
>6.   Rebuild the executable to include the licensing information in the
>application.

While I'm not an expert on licx or lc at all, it would seem to me that
you could do this with custom build steps in the IDE.

--
Sev
Tarek Madkour [MSFT] - 16 Feb 2005 01:07 GMT
>>I was having a really annoying problem getting some components I
>>bought from ComponentOne to work. I found this posting in their
[quoted text clipped - 8 lines]
> While I'm not an expert on licx or lc at all, it would seem to
> me that you could do this with custom build steps in the IDE.

Yes, the only workaround in VS2003 is to use custom build steps.
In VS2005 Beta2 we added IDE support for this feature.

Thanks,
Signature

Tarek Madkour, Visual C++ Team
This posting is provided "AS IS" with no warranties, and confers
no rights.

Ray Hayes - 16 Feb 2005 01:29 GMT
Thanks. I'll take a look at it.

> >>I was having a really annoying problem getting some components I
> >>bought from ComponentOne to work. I found this posting in their
[quoted text clipped - 13 lines]
>
> Thanks,
Blake Mizerany - 10 Mar 2005 19:38 GMT
I have been looking for C1Lc.exe online, my hard-disk, my C1FlexGrid
install CD.  Does anyone know where I can get it?  

-Blake Mizerany

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.