How to stop incrementing the DLL version number?

I have written a VB.NET DLL that is called by a third party program. If
I make any changes in the DLL and then try to replace my DLL file the
third party program will abort, saying that the DLL version number does
not match to the DLL that it was linked against. How can I recompile my
DLL without incrementing the version number? I don't see where this
"version number" is stored in the project. The version number, under the
"Assembly Information..." button, is not being incremented. I therefore
assume that the DDL version number is stored somewhere else.

John

Tom
Fri May 09 11:16:13 CDT 2008

In your assembly.info file, there's a line that might look something like
this:

<Assembly: AssemblyVersion("1.0.0.*")>

The asterisk gives the builder permission to increment the version number on
each build. To fix the version number, specify it without an asterisk, such
as:

<Assembly: AssemblyVersion("1.0.0.0")>

Tom Dacon
Dacon Software Consulting


"John" <me@nospam.com> wrote in message
news:MPG.228e15348a7d806d989687@newsgroups.comcast.net...
>I have written a VB.NET DLL that is called by a third party program. If
> I make any changes in the DLL and then try to replace my DLL file the
> third party program will abort, saying that the DLL version number does
> not match to the DLL that it was linked against. How can I recompile my
> DLL without incrementing the version number? I don't see where this
> "version number" is stored in the project. The version number, under the
> "Assembly Information..." button, is not being incremented. I therefore
> assume that the DDL version number is stored somewhere else.
>
> John

John
Fri May 09 11:37:31 CDT 2008

Tom,

Thanks for your reply. It appears that assembly.info file is already set
that way, i.e. <Assembly: AssemblyVersion("1.0.0.0")>. If I look at the
properties of the DLL both the Assembly Version and File Version are set
to "1.0.0.0". Is there something else going on?

John

In article <ubqa8$esIHA.1240@TK2MSFTNGP02.phx.gbl>,
tdacon@community.nospam says...
> In your assembly.info file, there's a line that might look something like
> this:
>
> <Assembly: AssemblyVersion("1.0.0.*")>
>
> The asterisk gives the builder permission to increment the version number on
> each build. To fix the version number, specify it without an asterisk, such
> as:
>
> <Assembly: AssemblyVersion("1.0.0.0")>
>
> Tom Dacon
> Dacon Software Consulting
>
>
> "John" <me@nospam.com> wrote in message
> news:MPG.228e15348a7d806d989687@newsgroups.comcast.net...
> >I have written a VB.NET DLL that is called by a third party program. If
> > I make any changes in the DLL and then try to replace my DLL file the
> > third party program will abort, saying that the DLL version number does
> > not match to the DLL that it was linked against. How can I recompile my
> > DLL without incrementing the version number? I don't see where this
> > "version number" is stored in the project. The version number, under the
> > "Assembly Information..." button, is not being incremented. I therefore
> > assume that the DDL version number is stored somewhere else.
> >
> > John
>
>
>

Tom
Fri May 09 12:41:54 CDT 2008

Beats me, John. This is all it's ever taken for me.

Good luck,
Tom


"John" <me@nospam.com> wrote in message
news:MPG.228e1d94e0b38672989688@newsgroups.comcast.net...
> Tom,
>
> Thanks for your reply. It appears that assembly.info file is already set
> that way, i.e. <Assembly: AssemblyVersion("1.0.0.0")>. If I look at the
> properties of the DLL both the Assembly Version and File Version are set
> to "1.0.0.0". Is there something else going on?
>
> John
>
> In article <ubqa8$esIHA.1240@TK2MSFTNGP02.phx.gbl>,
> tdacon@community.nospam says...
>> In your assembly.info file, there's a line that might look something like
>> this:
>>
>> <Assembly: AssemblyVersion("1.0.0.*")>
>>
>> The asterisk gives the builder permission to increment the version number
>> on
>> each build. To fix the version number, specify it without an asterisk,
>> such
>> as:
>>
>> <Assembly: AssemblyVersion("1.0.0.0")>
>>
>> Tom Dacon
>> Dacon Software Consulting
>>
>>
>> "John" <me@nospam.com> wrote in message
>> news:MPG.228e15348a7d806d989687@newsgroups.comcast.net...
>> >I have written a VB.NET DLL that is called by a third party program. If
>> > I make any changes in the DLL and then try to replace my DLL file the
>> > third party program will abort, saying that the DLL version number does
>> > not match to the DLL that it was linked against. How can I recompile my
>> > DLL without incrementing the version number? I don't see where this
>> > "version number" is stored in the project. The version number, under
>> > the
>> > "Assembly Information..." button, is not being incremented. I therefore
>> > assume that the DDL version number is stored somewhere else.
>> >
>> > John
>>
>>
>>

FamilyTreeMike
Fri May 09 13:58:31 CDT 2008

The error message seems a little strange in that the third party app seems to
know about the versioning of your product. Do you provide code/dll/libraries
to the third party that they compile against? When we have created plugins
for external apps in our group we are usually matching an interface spec via
COM as a plug-in. When versioning was important for book keeping, Tom's
answer was all we had to do as well.

"John" wrote:

> I have written a VB.NET DLL that is called by a third party program. If
> I make any changes in the DLL and then try to replace my DLL file the
> third party program will abort, saying that the DLL version number does
> not match to the DLL that it was linked against. How can I recompile my
> DLL without incrementing the version number? I don't see where this
> "version number" is stored in the project. The version number, under the
> "Assembly Information..." button, is not being incremented. I therefore
> assume that the DDL version number is stored somewhere else.
>
> John
>

John
Fri May 09 15:02:10 CDT 2008

Yes. I supplied the DLL to the third party who then compile and link
their code against my DLL.

John

In article <6741D8C2-2781-457B-A113-555191AF8288@microsoft.com>,
FamilyTreeMike@discussions.microsoft.com says...
> The error message seems a little strange in that the third party app seems to
> know about the versioning of your product. Do you provide code/dll/libraries
> to the third party that they compile against? When we have created plugins
> for external apps in our group we are usually matching an interface spec via
> COM as a plug-in. When versioning was important for book keeping, Tom's
> answer was all we had to do as well.
>
> "John" wrote:
>
> > I have written a VB.NET DLL that is called by a third party program. If
> > I make any changes in the DLL and then try to replace my DLL file the
> > third party program will abort, saying that the DLL version number does
> > not match to the DLL that it was linked against. How can I recompile my
> > DLL without incrementing the version number? I don't see where this
> > "version number" is stored in the project. The version number, under the
> > "Assembly Information..." button, is not being incremented. I therefore
> > assume that the DDL version number is stored somewhere else.
> >
> > John
> >
>

FamilyTreeMike
Fri May 09 21:34:00 CDT 2008

Then I would make sure both the AssemblyVersion and FileVersion numbers are
identical between builds. The other builder may be comparing those. They
may even be looking at some form of checksum on the dll.

"John" wrote:

> Yes. I supplied the DLL to the third party who then compile and link
> their code against my DLL.
>
> John
>
> In article <6741D8C2-2781-457B-A113-555191AF8288@microsoft.com>,
> FamilyTreeMike@discussions.microsoft.com says...
> > The error message seems a little strange in that the third party app seems to
> > know about the versioning of your product. Do you provide code/dll/libraries
> > to the third party that they compile against? When we have created plugins
> > for external apps in our group we are usually matching an interface spec via
> > COM as a plug-in. When versioning was important for book keeping, Tom's
> > answer was all we had to do as well.
> >
> > "John" wrote:
> >
> > > I have written a VB.NET DLL that is called by a third party program. If
> > > I make any changes in the DLL and then try to replace my DLL file the
> > > third party program will abort, saying that the DLL version number does
> > > not match to the DLL that it was linked against. How can I recompile my
> > > DLL without incrementing the version number? I don't see where this
> > > "version number" is stored in the project. The version number, under the
> > > "Assembly Information..." button, is not being incremented. I therefore
> > > assume that the DDL version number is stored somewhere else.
> > >
> > > John
> > >
> >
>