Question about deployment with strong name

[Ray]

Dear all,
Now, I have 3 projects of class library and 1 project of window
application. The window application will call the 3 class librarys. So
should I make 4 .snk files for each project? Or one .snk file linked by
Assemblyinfo.vb of each class library?
The main target of me is that I can install the window application once
in the client PC, then the client PC can update its version after I compile
in the program in the server. Please advice me some comments or provides
some references for that.
Thanks a lot,
Ray

 

[Peter Proost]

Hi,

maybe you can do it like this, add a reference in your windows application
to all your class library projects, then after you've changed something to
the windows application or one of your class library projects also build the
windows application and increase the version number in your config file (
You always have to build your windows application so that the new dll's of
your class library projects get copied). Place the bin of your windows
application on a server share. Than when your client starts his application
you can check to see if his version number (version number in his local
config file) is lower than the one on the server, if his version number is
lower start a small app to copy the new files and which closes the current
running app otherwise you can't copy the new files and after the copy is
done, let copy app restart your windows app. If you do it like this every
time the version number from the app on the server is changed the user
automaticaly gets an update the next time he starts the app.

hth
Peter

 

[Ray]

Dear Peter,
Thanks for your help.
I would like to ask should I write program by myself to check the Version
of the dll and download the dll from the server? Is there any function in
vb.net that while the dll in the server update, client will automatically
download the dll from the server?
Moreover, some reference book says that I have to update the dll using in
the client PC manually after the dll is downloaded. Is there any method that
the client PC can download the dll and update the dll using automatically?
Thanks a lot,
Ray

 

[Carlos J. Quintero [MVP]]

You should use the same .snk for all your proyects, referencing it in the
assemblyinfo.vb file of each project. The .snk contains your private key to
sign assemblies and generally there is no reason to have more than one
private key.