Hello
I have some class library projects and the client-application project that I want to deploy.
So when building the setup project, VS.net add automatically the dll of my class libraries. Good.
However, i want my dll to be installed in the gac. So do what's needed, give them strong name, modyfying the assembly info file with something like :
And my deployment is ok, working nice....
HOWEVER, I am wondering something.
The project is "stored" under Source Safe so another developper can easily get it and update it. And i am wondering what's happening with the assemblies strong name. Will the new developper have to copy my keys in the same folder ?
Can't we put the snk files under the project (visible in VS.NET), at the root, and giving the assembly a local path ?
I have tried
but I get an error, not finding the key file
I have some class library projects and the client-application project that I want to deploy.
So when building the setup project, VS.net add automatically the dll of my class libraries. Good.
However, i want my dll to be installed in the gac. So do what's needed, give them strong name, modyfying the assembly info file with something like :
Visual Basic:
<Assembly: AssemblyKeyFile("c:\SN\myKey.snk")>
And my deployment is ok, working nice....
HOWEVER, I am wondering something.
The project is "stored" under Source Safe so another developper can easily get it and update it. And i am wondering what's happening with the assemblies strong name. Will the new developper have to copy my keys in the same folder ?
Can't we put the snk files under the project (visible in VS.NET), at the root, and giving the assembly a local path ?
I have tried
Visual Basic:
<Assembly: AssemblyKeyFile("myKey.snk")>