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 / Windows Forms / WinForm General / February 2007

Tip: Looking for answers? Try searching our database.

programmatically adding resx file to project.

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Solitude - 14 Feb 2007 07:24 GMT
So in my class constructor I am trying to programmatically create a .resx
file to be included in our project file if it does not exist and add some
strings to it.

Has anyone done similar functionallity and if so how did you do it?

Thanks,
Matt
Kevin Spencer - 14 Feb 2007 12:00 GMT
A resx file is a project resource, not part of the final application. So
there is not point in creating one at runtime, unless I'm missing something
here.

Signature

HTH,

Kevin Spencer
Microsoft MVP
Software Composer
http://unclechutney.blogspot.com

The shortest distance between 2 points is a curve.

> So in my class constructor I am trying to programmatically create a .resx
> file to be included in our project file if it does not exist and add some
[quoted text clipped - 4 lines]
> Thanks,
> Matt
Solitude - 14 Feb 2007 22:40 GMT
What we are trying to do is license our controls and embed this license in
the final application that the user includes are control in. .licx is too
buggy and not sufficient for our needs so we want to create an embedded
resource in their final app with our licensing in it.

> A resx file is a project resource, not part of the final application. So
> there is not point in creating one at runtime, unless I'm missing something
[quoted text clipped - 8 lines]
> > Thanks,
> > Matt
Kevin Spencer - 15 Feb 2007 13:12 GMT
I'm not sure what you mean by "not sufficient for our needs," but I think I
would go with the built-in licensing in the Framework. It is based on the
.Net Framework licensing model, which is identical for all components and
controls. In addition, while it would certainly be possible to implement
your own method of embedding a license in an assembly as a resource during
installation, you're talking about a lot more trouble then figuring out how
to use the .Net Framework components to do the same thing.

Signature

HTH,

Kevin Spencer
Microsoft MVP
Software Composer
http://unclechutney.blogspot.com

The shortest distance between 2 points is a curve.

> What we are trying to do is license our controls and embed this license in
> the final application that the user includes are control in. .licx is too
[quoted text clipped - 16 lines]
>> > Thanks,
>> > Matt

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.