.DLL hell II - The Evil Empire Strikes Back

[.DLL hell II - The Evil Empire Strikes Back]

I can't figure out how this side-by-side assembly stuff it
supposed to work.
I have a stack of four assemblies
A has no references
B references A & C
C References A & B
D References A, B and C

During a built I invariably end up with the wrong
assemblies in the final bin directory even though I have
hard-coded the version numbers for each component to avoid
breaking the build. Worse when I copy the correct
versions off the assemblies for A, B and C to the bin
directory for D and then open D in Visual Studio it,
without warning, copies the wrong versions of the files
back to the bin directory. I've wasted weeks with this
stuff - It makes figuring out the cause of problems really
rather tricky. And its not even a terribly complicated
object stack. How do I build it?

[Jay B. Harlow [MVP - Outlook]]

I hope this is a typo:

B references A & C
C References A & B
B references C and C reference B, cannot be done in .NET. As each needs to
be compiled before the other...

I normally have a single solution that has 4 projects A,B,C,D when I build
the solution all the projects get built, and the correct versions of the
dlls are in the correct bin folders. No manual intervention required. I have
solutions with 8 to 12 class libraries each using this method.

Within VS.NET are you referencing the DLL or the project?

Hope this helps
Jay

".DLL hell II - The Evil Empire Strikes Back" <a@b.c> wrote in message
news:0d****************************@phx.gbl... I can't figure out how this side-by-side assembly stuff it
supposed to work.
I have a stack of four assemblies
A has no references
B references A & C
C References A & B
D References A, B and C

During a built I invariably end up with the wrong
assemblies in the final bin directory even though I have
hard-coded the version numbers for each component to avoid
breaking the build. Worse when I copy the correct
versions off the assemblies for A, B and C to the bin
directory for D and then open D in Visual Studio it,
without warning, copies the wrong versions of the files
back to the bin directory. I've wasted weeks with this
stuff - It makes figuring out the cause of problems really
rather tricky. And its not even a terribly complicated
object stack. How do I build it?

[Jay B. Harlow [MVP - Outlook]]

C,
Refer back to your original post you stated:

I can't figure out how this side-by-side assembly stuff it supposed to work.
I have a stack of four assemblies
A has no references
B references A & C
C References A & B
D References A, B and C

To compile B, you will need to have C compiled.
To compile C, you will need to have B compiled.

Given the problem .NET has with cross referencing of
classes within objects is my only option to have a
separate assembly containing the application exceptions I
need which both C and D can reference? IE Instead of having the Exceptions in Assembly B, I would consider having an
Assembly E for the Application Exceptions. Which is a variation of the
Seperated Interface Pattern.

http://www.martinfowler.com/eaaCatal...Interface.html

Although it is not as common, I would consider having Assembly B publish an
Interface that identifies 'custom exceptions of one of the types found in
C'. In other words a single Interface in Assembly B, that all of the
exceptions in C implement, this interface would not need to have any
members. Which is another variation of the Seperated Interface Pattern.

Hope this helps
Jay

"C" <a@b.c> wrote in message news:0b****************************@phx.gbl... No it isn't a typo. Its what I want to achieve:
A) Is an analyser component
B) Is a logger component
C) Is a Server component. C may throw one of several
application exceptions, which have some additional
properties, exposed on them.
These are logged by the logger which may additionally
alert ops to the fact that there is a major problem. It
does this by looking to see if the type of Exception it
has been thrown is a custom exception of one of the types
found in C and then interrogating some of the additional
properties.

Given the problem .NET has with cross referencing of
classes within objects is my only option to have a
separate assembly containing the application exceptions I
need which both C and D can reference? IE
A Is the Analyser Component and has no references
B is the Application Exception Class and has no references
C Is the logger and references B
D Is the Server and references A, B and C
?

-----Original Message-----
I hope this is a typo:

B references A & C
C References A & B

B references C and C reference B, cannot be done in .NET.

As each needs to

be compiled before the other...

I normally have a single solution that has 4 projects

A,B,C,D when I build

the solution all the projects get built, and the correct

versions of the

dlls are in the correct bin folders. No manual

intervention required. I have

solutions with 8 to 12 class libraries each using this

method.

Within VS.NET are you referencing the DLL or the project?

Hope this helps
Jay

".DLL hell II - The Evil Empire Strikes Back" <a@b.c>

wrote in message

news:0d****************************@phx.gbl...

I can't figure out how this side-by-side assembly stuff

it supposed to work.
I have a stack of four assemblies
A has no references
B references A & C
C References A & B
D References A, B and C

During a built I invariably end up with the wrong
assemblies in the final bin directory even though I have
hard-coded the version numbers for each component to avoid breaking the build. Worse when I copy the correct
versions off the assemblies for A, B and C to the bin
directory for D and then open D in Visual Studio it,
without warning, copies the wrong versions of the files
back to the bin directory. I've wasted weeks with this
stuff - It makes figuring out the cause of problems really rather tricky. And its not even a terribly complicated
object stack. How do I build it?

.

[C]

It does - thank you very much.

-----Original Message-----
C,
Refer back to your original post you stated:

>> I can't figure out how this side-by-side assembly stuff

it

>> supposed to work.
>> I have a stack of four assemblies
>> A has no references
>> B references A & C
>> C References A & B
>> D References A, B and C
To compile B, you will need to have C compiled.
To compile C, you will need to have B compiled.

Given the problem .NET has with cross referencing of
classes within objects is my only option to have a
separate assembly containing the application exceptions

I need which both C and D can reference? IE

Instead of having the Exceptions in Assembly B, I would

consider having anAssembly E for the Application Exceptions. Which is a variation of theSeperated Interface Pattern.

http://www.martinfowler.com/eaaCatal...ratedInterface. html
Although it is not as common, I would consider having Assembly B publish anInterface that identifies 'custom exceptions of one of the types found inC'. In other words a single Interface in Assembly B, that all of theexceptions in C implement, this interface would not need to have anymembers. Which is another variation of the Seperated Interface Pattern.
Hope this helps
Jay

"C" <a@b.c> wrote in message news:0b0901c377b5$38f2fba0

$a*******@phx.gbl...

No it isn't a typo. Its what I want to achieve:
A) Is an analyser component
B) Is a logger component
C) Is a Server component. C may throw one of several
application exceptions, which have some additional
properties, exposed on them.
These are logged by the logger which may additionally
alert ops to the fact that there is a major problem. It
does this by looking to see if the type of Exception it
has been thrown is a custom exception of one of the types found in C and then interrogating some of the additional
properties.

Given the problem .NET has with cross referencing of
classes within objects is my only option to have a
separate assembly containing the application exceptions I need which both C and D can reference? IE
A Is the Analyser Component and has no references
B is the Application Exception Class and has no references C Is the logger and references B
D Is the Server and references A, B and C
?

>-----Original Message-----
>I hope this is a typo:
>
>> B references A & C
>> C References A & B
>
>B references C and C reference B, cannot be done

in .NET. As each needs to

>be compiled before the other...
>
>I normally have a single solution that has 4 projects

A,B,C,D when I build

>the solution all the projects get built, and the

correct versions of the

>dlls are in the correct bin folders. No manual

intervention required. I have

>solutions with 8 to 12 class libraries each using this

method.

>
>Within VS.NET are you referencing the DLL or the

project? >
>Hope this helps
>Jay
>
>".DLL hell II - The Evil Empire Strikes Back" <a@b.c>

wrote in message

>news:0d****************************@phx.gbl...
>> I can't figure out how this side-by-side assembly stuff it

>> supposed to work.
>> I have a stack of four assemblies
>> A has no references
>> B references A & C
>> C References A & B
>> D References A, B and C
>>
>> During a built I invariably end up with the wrong
>> assemblies in the final bin directory even though I

have >> hard-coded the version numbers for each component to

avoid

>> breaking the build. Worse when I copy the correct
>> versions off the assemblies for A, B and C to the bin
>> directory for D and then open D in Visual Studio it,
>> without warning, copies the wrong versions of the files >> back to the bin directory. I've wasted weeks with this >> stuff - It makes figuring out the cause of problems

really

>> rather tricky. And its not even a terribly complicated >> object stack. How do I build it?
>>
>
>
>.
>

.