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.
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