.net dll vs vb6 dll

[Guest]

hi,

in vb 6 when i build a dll i have the option to set the binary integrity so
that when i make a change to hat library and binary integrity is changed, i
receive a
warning. is there a way to do it in a .NET class library?

example: i build a class library with one class and one method/function and
a web form application that uses this library. If i change the name of the
method in the library, binary integrity is breaked but i have no warning and
when i execute my application an excepetion is raised.

thanks. dan.

 

[Michel Posseth [MCP]]

You could implement a interface to get the by you required behavior

regards

Michel Posseth

 

[Guest]

hi, thanks for you answer...but with an interface...hummm??? how come??
ok, lets say i have a class library project with a couple of functions; i
deploy it along with the application(s) that uses it; Then later some
developer changes the dll, for example the name of a function within a class,
the developer should be warned that the changes he has made can cause
integrity problems of already deployed applications dependent on the dll. In
vb6.0 i just set an option in the project properties to enable binary
integrity...is there anythin like this under any .NET IDE?

how can i achieve this using an interface??

thanks and regards. dan.

 

[Michel Posseth [MCP]]

Hello dan ,

vb6.0 i just set an option in the project properties to enable binary
integrity...is there anythin like this under any .NET IDE?

VS6 checks this with a reference binary and does nothing else as checking
the class interfaces

I know exactly what you mean , i have been looking for these options in the
begining of my .Net career too ( as a previous VS6 enterprise version
developer )
however it seems that some of the nice thingy`s we had in VS6 yet have to
be reintroduced in the .Net IDE ( probably as big new enhancements to
the IDE )

In dutch we call this selling old wine in new packages

Don`t get me wrong i am verry happy with my .Net IDE but some thingy`s you
could do in the past with just a mouse click , now require some coding
however you also get a lot new features in return.

with a interface you can ensure that your program implements methods and
properties , to ensure compatiblity between projects , if a methods
signature is changed or even removed the project wil not compile , if you
are afraid of co workers messing with the project you could create a
interface dll that you keep in your private workspace .

In this way co workers can extend the project , do maintenance on it but
they can never destroy the required method / property signature ( unless
they remove the interface , but hey in VS6 you could also just set the
compare binary to a newer vesrion of your project )

regards

Michel

 

[Guest]

example: i build a class library with one class and one
method/function and a web form application that uses this library. If
i change the name of the method in the library, binary integrity is
breaked but i have no warning and when i execute my application an
excepetion is raised.

Typically you would do this with a shared interface.

Or you can sign your library - this will add a signature to the library and
the calling app can check for a specific version or signature.