Development Practice: multiple assemblies

[Curtis Justus]

Hello,

We are making a large scale application with numerous assemblies. We have
our business object assemblies, UI assemblies, etc. During the course of
the project, people would be getting errors trying to compile their user
controls. The errors state that the version of the lower-level DLL is not
the right version.

Let's say we have the following structure:

Low-level DLL: LowDLL.DLL

UserControl1 references LowDLL.DLL
UserControl2 references LowDLL.DLL
UserControl3 references LowDLL.DLL

Main application (myapp.exe) refers to all three user controls.

Is the best way to make sure LowDLL.DLL is the right version to make sure
everybody has the "right version?" I know this is probably a very simple
question, but please humor me ;-).

Thank you in advance,
cj

[Nicholas Paldino [.NET/C# MVP]]

Re: Development Practice: multiple assemblies

Curtis,

I think that if you strong name the LowDLL.DLL assembly, then the
version number must match when making references to it. The strong name
changes when the assembly version changes.

Hope this helps.


--
- Nicholas Paldino [.NET/C# MVP]
- nicholas.paldin o@exisconsultin g.com

"Curtis Justus" <donotspamme@no spam.ruurjv.com > wrote in message
news:e4Ea3$5SDH A.3144@tk2msftn gp13.phx.gbl...[color=blue]
> Hello,
>
> We are making a large scale application with numerous assemblies. We have
> our business object assemblies, UI assemblies, etc. During the course of
> the project, people would be getting errors trying to compile their user
> controls. The errors state that the version of the lower-level DLL is not
> the right version.
>
> Let's say we have the following structure:
>
> Low-level DLL: LowDLL.DLL
>
> UserControl1 references LowDLL.DLL
> UserControl2 references LowDLL.DLL
> UserControl3 references LowDLL.DLL
>
> Main application (myapp.exe) refers to all three user controls.
>
> Is the best way to make sure LowDLL.DLL is the right version to make sure
> everybody has the "right version?" I know this is probably a very simple
> question, but please humor me ;-).
>
> Thank you in advance,
> cj
>
>[/color]

[Curtis Justus]

Re: Development Practice: multiple assemblies

That's what I thought. Thanks.

"Nicholas Paldino [.NET/C# MVP]" <nicholas.paldi no@exisconsulti ng.com> wrote
in message news:uhvnq86SDH A.2256@TK2MSFTN GP11.phx.gbl...[color=blue]
> Curtis,
>
> I think that if you strong name the LowDLL.DLL assembly, then the
> version number must match when making references to it. The strong name
> changes when the assembly version changes.
>
> Hope this helps.
>
>
> --
> - Nicholas Paldino [.NET/C# MVP]
> - nicholas.paldin o@exisconsultin g.com
>
> "Curtis Justus" <donotspamme@no spam.ruurjv.com > wrote in message
> news:e4Ea3$5SDH A.3144@tk2msftn gp13.phx.gbl...[color=green]
> > Hello,
> >
> > We are making a large scale application with numerous assemblies. We[/color][/color]
have[color=blue][color=green]
> > our business object assemblies, UI assemblies, etc. During the course[/color][/color]
of[color=blue][color=green]
> > the project, people would be getting errors trying to compile their user
> > controls. The errors state that the version of the lower-level DLL is[/color][/color]
not[color=blue][color=green]
> > the right version.
> >
> > Let's say we have the following structure:
> >
> > Low-level DLL: LowDLL.DLL
> >
> > UserControl1 references LowDLL.DLL
> > UserControl2 references LowDLL.DLL
> > UserControl3 references LowDLL.DLL
> >
> > Main application (myapp.exe) refers to all three user controls.
> >
> > Is the best way to make sure LowDLL.DLL is the right version to make[/color][/color]
sure[color=blue][color=green]
> > everybody has the "right version?" I know this is probably a very[/color][/color]
simple[color=blue][color=green]
> > question, but please humor me ;-).
> >
> > Thank you in advance,
> > cj
> >
> >[/color]
>
>[/color]