[Message Deleted]
-
First, read this[^] for why this is a bad idea. Next, you need to very that the 3rd party assemblies that you want to install into the GAC are signed and strong named. If not, stop - you're done. You cannot sign and strong name a 3rd party library, unless they give you the source code to recompile it. As for creating an installer package for them, there's a ton of different ways of doing this. Here...[^]
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007 -
First, read this[^] for why this is a bad idea. Next, you need to very that the 3rd party assemblies that you want to install into the GAC are signed and strong named. If not, stop - you're done. You cannot sign and strong name a 3rd party library, unless they give you the source code to recompile it. As for creating an installer package for them, there's a ton of different ways of doing this. Here...[^]
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007 -
Richard Hartness wrote:
Assuming that you have heard of them (which I would assume is likely) you may know that both of your concerns can be addressed.
Yep, I have. I didn't know which libraries you were referring to, sooooo, I couldn't be sure if it was a "good" library. :-D
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007 -
Richard Hartness wrote:
Assuming that you have heard of them (which I would assume is likely) you may know that both of your concerns can be addressed.
Yep, I have. I didn't know which libraries you were referring to, sooooo, I couldn't be sure if it was a "good" library. :-D
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007They are good - for they are code from the mighty Josh. :-D Sing it with me - All hail to Josh.
Deja View - the feeling that you've seen this post before.