DLL Post Build Events

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

Please do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.

This forum is for discussing mojoPortal development

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

You can monitor commits to the repository from this page. We also recommend developers to subscribe to email notifications in the developer forum as occasionally important things are announced.

Before posting questions here you might want to review the developer documentation.

Do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.
This thread is closed to new posts. You must sign in to post in the forums.
8/27/2009 2:03:06 PM
michael.jew
Gravatar
Total Posts 26
View Posts

DLL Post Build Events

Hello Joe & Community,

Question: What is the logic behind using post-build events to copy the following to the /Web/ directory:

  • mojoPortal.Features.UI.dll
  • mojoPortal.Features.Business.dll
  • mojoPortal.Features.Data.dll

as opposed to calling them as References from mojoPortal.Web?

 

Yes, I understand that copying aspx & ascx files is necessary from *.UI projects to /Web/ directory. But, my question's focus is on copying the DLLs. Is it just a slick way to get around circular dependencies?

 

thank you!

Michael

8/27/2009 2:28:35 PM
Asad Samarian
Gravatar
Total Posts 550
View Posts

Re: DLL Post Build Events

Hi  Michael,

In this way you no need rebuild all solution after any change in one of other features projects. In other hand any developers that get updates of code form SVN lost added references to mojoPortal web project. Other reason the mojoPortal.Web is an independent core project that other features add to it by copying DLLs to bin folder and others files(*.aspx,*.ascx,*.resx,..) to specific folders.

I hope helps

Best,

Asad

8/27/2009 2:33:37 PM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: DLL Post Build Events

Its a matter of both avoiding circular references and separation of concerns. The core web has no dependencies on external features (nor should it) but external features do depend on the mojoPortal.Web project. Post build is a deployment mechanism for external projects, nothing more nothing less.

Hope it helps,

Joe

8/27/2009 2:46:48 PM
michael.jew
Gravatar
Total Posts 26
View Posts

Re: DLL Post Build Events

Thanks Joe & Asad.

Ok, here are the reasons:

  • Avoid circular references
  • Separation of concerns (the core shouldn't depend on extremities)

Thank you.  It's clear now.

-Michael

You must sign in to post in the forums. This thread is closed to new posts.