What is your companies policy on putting it in the Global Assembly Cache
(GAC) ?
You will probably need a strong name, but once it is in there, you should be
able to access it from both places.
If you built your .net dll with visual studio, there is probably an
AssemblyInfo.cs file. At the end of that file is an AssemblyKeyFile
attribute.
[assembly: AssemblyKeyFile("")]
you change the line above to include the filename of the .snk file
[assembly: AssemblyKeyFile("mySName.snk")]
you use the sn.exe tool to create a .snk file.
sn -k mySName.snk // check that my syntax is correct here
this file needs to be included with your .net dll when you distribute it.
then you say gacutil -i your_dotNet_dll_file.dll
The location where your .net dll and .snk file 'live' do not need to be (an
probably shouldn't be) in the gac directory.
Now you should be able to get at the component from both the asp and vb app.
I hope this helps you out,
sincerely,
John Scalco
"Ian" <an*******@discussions.microsoft.com> wrote in message
news:6A**********************************@microsof t.com...
Help!!!
I have created a .net DLL which is accessed by both a .Net VB Application
as well as A .Net ASP Page. The only way I can seem to make it work is if
this DLL is in the WinNT\System32 Directory. Our Company Policy is not to
permit any custom code in the System32 Directory. I cant get either of my
apps to work if the code is in a seperate Directory. Any help would be
greatly appreciated.
Thanks