Bob
Tue Apr 05 03:21:06 CDT 2005
What you're seeing is an intended behaviour of .NET that permits
side-by-side installation of many different versions of a program.
If you don't want this sort of thing to happen you should...
#1 remove the asterisks from the version number generation string in
AssemblyInfo.xx and lock the version to a number that you decide. This will
prevent many different versions being generated.
#2 Give your DLL a strong name and deploy it to the Global Assembly Cache
(GAC) where it will be used to provide ALL applications with services as
opposed to just the application that was build for the specific version
x.x.x.x.
--
Bob Powell [MVP]
Visual C#, System.Drawing
Find great Windows Forms articles in Windows Forms Tips and Tricks
http://www.bobpowell.net/tipstricks.htm
Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/faqmain.htm
All new articles provide code in C# and VB.NET.
Subscribe to the RSS feeds provided and never miss a new article.
"Chris Zopers" <test123test12@12move.nl> wrote in message
news:OZII9RbOFHA.3296@TK2MSFTNGP15.phx.gbl...
> Hello,
>
> I would like to know the following:
>
> In VB 6 I could create a dll file, place it on a server and register the
> dll file on each client computer, so all client computers know that the
> dll file is on the server.
> This way, I could make small changes to the dll, without having to
> reïnstall components on the client.
>
> In VB.NET, each dll is automatically being copied to the /bin directory
> in the directory where the executable file is located. This means that
> the dll file also is located on the client machine. When I have made
> small changes to the dll, I have to recompile the executable file and
> install a new version of the executable and the dll file to each client.
> Isn't there a way to make changes to a dll without having to recompile
> and redistribute to client machines?
>
> Greetings,
> Chris
>
>
>
> *** Sent via Developersdex
http://www.developersdex.com ***