Re: VB.NET Assembly Compatability

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Nak (a_at_a.com)
Date: 01/04/05 

Date: Tue, 4 Jan 2005 14:53:31 -0000

Hi Carlos,

    Excellent! Cheers.

Nick.

"Carlos J. Quintero [.NET MVP]" <carlosq@NOSPAMsogecable.com> wrote in
message news:O$nhuim8EHA.2452@TK2MSFTNGP14.phx.gbl...
> If you are sure that you are not breaking compability (VS.NET, on the
> contrary to VB6, does not offer yet a tool to verify this), you need to
> keep the value of the AssemblyVersion attribute of the AssemblyInfo.vb
> file, because by default it is changed on each build:
>
> <Assembly: AssemblyVersion("1.0.*")>
>
> So, change it to, say:
>
> <Assembly: AssemblyVersion("1.0.0.0")>
>
> and don´t change it until you break compatibility.
>
> You should also add another attribute that is not added by default:
>
> <Assembly: AssemblyFileVersion("1.0.0.5")>
>
> which is the classic Win32 file version (shown in Windows Explorer), not
> the assembly version (shown in GAC viewer), and you change this on each
> build, to be able to distinguish each build now that the assembly version
> is the same (if ommited, the assembly file version is set to the assembly
> version).
>
> --
>
> Carlos J. Quintero
>
> MZ-Tools 4.0: Productivity add-ins for Visual Studio .NET
> You can code, design and document much faster.
> http://www.mztools.com
>
>
> "Nak" <a@a.com> escribió en el mensaje
> news:%230E6VSm8EHA.1524@TK2MSFTNGP09.phx.gbl...
>> Hi there,
>>
>> I was wondering if anyone knew of a way to maintain compatability with
>> assemblies providing the interfaces remains the same? At the moment if I
>> re-compile an assembly without actually changing an interface it breaks
>> compatability, forcing all of my consuming assemblies to need
>> recompiling. I know this could be done with VB6, what about .NET?
>>
>> Nick.
>>
>
>

Relevant Pages

  • Re: Security of .NET Framework 2.0 assembly signing...
    ... What is a reasonably good way of protecting c# assemblies against crackers and such? ... Nick Z. wrote: ... Is version 2.0 better at signing assemblies? ... Can you point me in the right direction towards protecting my .NET applications in general? ...
    (microsoft.public.dotnet.framework)
  • Re: IIS 5.0 bin directory loses default document definition and pe
    ... Nick ... "Ken Schaefer" wrote: ... > assemblies for your .NET web applications. ...
    (microsoft.public.inetserver.iis)
  • Re: .NET how to check binary compatability
    ... suite of products that have a number of shared assemblies. ... In VB6 we had the ability to verify components by using binary compatability ... In .NET increment the AssemblyVersion when compatibility has been broken. ...
    (microsoft.public.dotnet.languages.vb)
  • Problem with SaveAs4 using swSaveAsOptions_SaveReferenced
    ... Using Solidworks 2005 SP3 API for saving/exporting an Assembly File ... and parts) in both assemblies and drawings. ...
    (comp.cad.solidworks)
  • Handling security of dynamically generated code?
    ... The code is stored in a database, and is at runtime compiled to an assembly file. ... One idea I was thinking about was to sign my generated assembly with a specific key-file, and then adjust the framework configuration to give assemblies signed with this specific key limited permissions. ... Assembly assembly = CompileScript(Script); ...
    (microsoft.public.dotnet.framework)