troubleshooting Question

Circular reference impact...

Avatar of davism
davismFlag for United States of America asked on
Programming Languages-Other.NET ProgrammingVisual Basic.NET
26 Comments2 Solutions707 ViewsLast Modified:

I have a question...I'm porting something from VB over to VB.NET. My solution is comprised of 1 executable with references to other dll's.

The dll's are categorized based on content of the functions. For example: I have a dll (i.e. DateProcess) that contains seveal date related specific functionality including but not limited to calling another date related dll and the functiona are to be callable from DateProcess. I have another dll (i.e. CoreCommon) that peforms other "common" components such as a file creation.

The problem is - in the CoreCommon I am creating a file and I am using a function in the DateProcess dll.

Since, CoreCommon includes "common" functions the DateProcess has a reference to the CoreCommon.

Now, I understand the reasoning with the memory leak what existed from VB6 but I believe I was handling it appropriately then. Whereas I would set the object created for the function of the DateProcess to nothing. (Basically, destroy it).

However, I cannot even add the reference in DateProcess due to the circular reference item.

Anybody have any thoughts on this?
Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 2 Answers and 26 Comments.
Join the Community
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 2 Answers and 26 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros