S
Sherin george
Hi everybody,
I have got a conceptual issue. I have created a class
application (.dll) with VB.Net and give reference to
another windows application.The dll file got copied to my
windows application file and all went fine and I am able
to execute the methods on the base dll after instantiating
the class application.
But after that I modified base class application (added
some new methods to it) and compile so as to make the next
version of the dll.Then without removng the reference to
the previous version when I tried to execute the windows
application it first gave me the warning that "There are
some errors.Do you want to continue?" After choosing no,
when I tried to see the methods of my objects , to my
surprise, it got automatically changed to the newly buit
version of dll
I had not changed any of the propery (it is supposed to
take the local copy of the assmbly for execution in the
client application).But still I am not able to understand
why the windows application is taking reference of the
physical dll file though the local copy is existing on the
file.
Is there any setting in order to use the previous version
of the dll?
If the physical file is always referenced, then what is
the use of bringing it down to the client's worksapce?
Thanks in advance,
Regards,
Sherin George
I have got a conceptual issue. I have created a class
application (.dll) with VB.Net and give reference to
another windows application.The dll file got copied to my
windows application file and all went fine and I am able
to execute the methods on the base dll after instantiating
the class application.
But after that I modified base class application (added
some new methods to it) and compile so as to make the next
version of the dll.Then without removng the reference to
the previous version when I tried to execute the windows
application it first gave me the warning that "There are
some errors.Do you want to continue?" After choosing no,
when I tried to see the methods of my objects , to my
surprise, it got automatically changed to the newly buit
version of dll
I had not changed any of the propery (it is supposed to
take the local copy of the assmbly for execution in the
client application).But still I am not able to understand
why the windows application is taking reference of the
physical dll file though the local copy is existing on the
file.
Is there any setting in order to use the previous version
of the dll?
If the physical file is always referenced, then what is
the use of bringing it down to the client's worksapce?
Thanks in advance,
Regards,
Sherin George