File Link in .NET DLL

[faktujaa]

Hi All,
I have to avoid cyclic reference in my DLLS. One way is to move the code to
the common DLL. But now since i have written a lot of code, it would take a
whole lot of time to do this. The other way i see is to link file to the DLL.
But i have some doubts about taking this approach.
1. Since all my DLLs are on the same server now, its not a problem but what
if later i try to seperate out this DLLs on different servers for load
balancing. Then this link file will be a problem???
2. Actually what do you exactly mean by linking a file to a DLL. Though its
avoid compilation error but what it actually does????
Please help me on this asap.
Thanks in Advance,
faktujaa

[Alex Korchemniy]

If splitting the code into two assemblies is truely beneficial - I recommend
you do the work and properly "refactor" your code.

.... By linking I'm assuming you are talking about al.exe the assemly linker.
Correct?? What you probably read about is called multi-file assembly. Where
you can compile to a module and then link them together. Currently VS.net
(2003 version at least) doesn't have much built-in support for that.

Talking about load balancing. It all depends on how you implement it. You
could get away with something to work using identical assembly on both
machines.

----
This posting is provided "AS IS" with no warranties, and confers no rights.
Alex Korchemniy

"faktujaa" wrote:

Hi All,
I have to avoid cyclic reference in my DLLS. One way is to move the code to
the common DLL. But now since i have written a lot of code, it would take a
whole lot of time to do this. The other way i see is to link file to the DLL.
But i have some doubts about taking this approach.
1. Since all my DLLs are on the same server now, its not a problem but what
if later i try to seperate out this DLLs on different servers for load
balancing. Then this link file will be a problem???
2. Actually what do you exactly mean by linking a file to a DLL. Though its
avoid compilation error but what it actually does????
Please help me on this asap.
Thanks in Advance,
faktujaa

[faktujaa]

Hi,
Thanks. Im not using this command but linking the file through IDE. We have
this option through Add Existing File to Project by right clicking on it and
then instead of opening file we can link file. The file gets linked to the
project and the project gets compiled with no errors. I would try putting the
DLLS in seperate machines and see it by myself but though of asking someone
who already knows abt this as i have to change a lot of code in order to test
this. btw im using remoting to invoke the components through interfaces. All
the components are currently on the same machine in bin folder of IIS with
web.config file. Components in the same folder are invoked directly and not
via remoting but intend to that later to support load balancing. Hope this
helps you in understanding the problem. Any help is highly appreciated.
Thanks in advance.
faktujaa

"Alex Korchemniy" wrote:

If splitting the code into two assemblies is truely beneficial - I recommend
you do the work and properly "refactor" your code.

... By linking I'm assuming you are talking about al.exe the assemly linker.
Correct?? What you probably read about is called multi-file assembly. Where
you can compile to a module and then link them together. Currently VS.net
(2003 version at least) doesn't have much built-in support for that.

Talking about load balancing. It all depends on how you implement it. You
could get away with something to work using identical assembly on both
machines.

----
This posting is provided "AS IS" with no warranties, and confers no rights.
Alex Korchemniy

"faktujaa" wrote:

Hi All,
I have to avoid cyclic reference in my DLLS. One way is to move the code to
the common DLL. But now since i have written a lot of code, it would take a
whole lot of time to do this. The other way i see is to link file to the DLL.
But i have some doubts about taking this approach.
1. Since all my DLLs are on the same server now, its not a problem but what
if later i try to seperate out this DLLs on different servers for load
balancing. Then this link file will be a problem???
2. Actually what do you exactly mean by linking a file to a DLL. Though its
avoid compilation error but what it actually does????
Please help me on this asap.
Thanks in Advance,
faktujaa