Hi,
I have written a class which I intend to use in all of my asp.net
applications. I have wrapped the class in a namesapce.
I now must make my class availible to all of my projects so that they can
use it by writing
imports mynamespce in the aspx.vb file.
I have got as far as figuring out that the dll must go in the global
assembly cache, however I would like a little advice on how to get it there,
preferably the easiest safest way.
these are the alternatives I have figured out so far.
compile the namespace/class into .dll and the use command line tools to give
it a stong name (sn.exe) and the insert into global assembly cache
(gautil.exe)
I must say that i am not keen on command line tools and figure that visual
studio must provide an alternative, which I think is
create a merge module from the namespace (I am assuming the merge module
will give the dll a strong name, although I am not sure) and then add the
merge module to a set up project (not a web set up project) to create a msi
to put it into the global assembly cache.
could anybody tell me if my assumptions above are correct, or not :) , or
even point me to a good article on such things, because so far I have not
managed to be able to reference my new namespace/class from another aspx.vb
page by simply writing
imports mynamespace....
any help is very much appreciated.
cheers
martin
I have written a class which I intend to use in all of my asp.net
applications. I have wrapped the class in a namesapce.
I now must make my class availible to all of my projects so that they can
use it by writing
imports mynamespce in the aspx.vb file.
I have got as far as figuring out that the dll must go in the global
assembly cache, however I would like a little advice on how to get it there,
preferably the easiest safest way.
these are the alternatives I have figured out so far.
compile the namespace/class into .dll and the use command line tools to give
it a stong name (sn.exe) and the insert into global assembly cache
(gautil.exe)
I must say that i am not keen on command line tools and figure that visual
studio must provide an alternative, which I think is
create a merge module from the namespace (I am assuming the merge module
will give the dll a strong name, although I am not sure) and then add the
merge module to a set up project (not a web set up project) to create a msi
to put it into the global assembly cache.
could anybody tell me if my assumptions above are correct, or not :) , or
even point me to a good article on such things, because so far I have not
managed to be able to reference my new namespace/class from another aspx.vb
page by simply writing
imports mynamespace....
any help is very much appreciated.
cheers
martin
Comment