plugins - DLL mess in .NET, how to split one solution to multiple DLLs? -


I have got a large VSNet project with 5-6 projects and one of these projects is core DLL is. / P>

Now I have removed an interface to add some plug-in support, but the interface was necessary to use some other classes and Core.dll needed the interface, so they had to separate. (I am not in the context of each other)

After this my day was wasted because even after spending four hours, I could not separate them! Finally I made 20+ projects and still does not work ( actually not closed ) It seems that I am going to end with 50 projects and need to change a lot of code to correct it.

I knew that my code was very coupled, and a little back.

Am I doing this right? Now I have to pay my bills and I have to suffer due to my highly coupled code? Or am I forgetting something?

If you have to work with the interface, then you should be able to draw your interface to the original DLL , And interface for any requirements on that interface, it is a bit painful.

If you have excessive coupled dependencies through your interface, then you will need to re-apply a small amount. Try to remove the interface or base class from the dependencies of the main interface (which would be easy to pull in a new project), it should help prevent the circular dependency problems running properly.

Normally, though, before I think about it and thinking about my project, project layout should work more than fragmentation - if you are doing your classes properly, then Most of the issues of dependence clean themselves.

Before I try to remove it, I will actually try to re-implement it.


Comments

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

html - CSS autoheight, but fit content to height of div -

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -