-
Hi,
When I make some changes to a dll that my application uses, shouldn't the application be able to use that updated dll without having to specify the new dll in the application itself? My thought was that it would be much easier to make changes to a dll and give that to the end user to use rather than have to redistribute the whole application each time I make a change to a dll..
It doesn't seem to work because I did a little test with the famous "Hello World!" project. I created a dll named HelloWorld.dll with the following code:
Code:
MsgBox "Hello World!"
I then referenced that dll in a new project and it worked fine. Then, I went back to the dll and put a few extra letters in the MsgBox string and saved the changes and created the dll file. However, now the application doesn't seem to recognize the dll any more.. It says:
"Run-time error 430:
Class does not support automation or does not support expected interface."
Any help or ideas would be greatly appreciated..
Dan
Any help would be appreciated..
Dan
-
One side note that I left out.... Within the VB6 design environment, there seems to be no problem with what I'm trying to do. In other words, I can make changes to the dll and then run the program and it has no problem using the updated dll.
It just seems to happen when I have already compiled the program and then try to use the updated dll.
Thanks,
dan
