It doesn't look like the snk is in the beta7 distribution. It
should not be.
The snk identifies the publisher of the software. This is
an 'issue' for open source software. The snk is used to
establish a trust relationship. If the snk (i.e. the private key)
is publicly available then it is available for everyone to use to
sign any code they write, therefore it is useless for creating a
trust relationship. Therefore the snk which identifies me
personally will be held privately.
To build strongly named versions of log4net you will need to
create your own snk file (this will identify you, rather than
me). Use the sn tool in the .net sdk to generate a new snk
file.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=222270
it used to be there in beta7...
Logged In: YES
user_id=278872
It doesn't look like the snk is in the beta7 distribution. It
should not be.
The snk identifies the publisher of the software. This is
an 'issue' for open source software. The snk is used to
establish a trust relationship. If the snk (i.e. the private key)
is publicly available then it is available for everyone to use to
sign any code they write, therefore it is useless for creating a
trust relationship. Therefore the snk which identifies me
personally will be held privately.
To build strongly named versions of log4net you will need to
create your own snk file (this will identify you, rather than
me). Use the sn tool in the .net sdk to generate a new snk
file.