H
hgnis_ppc
In one of my recent projects , I am planning to split the work as a
core asp.net application and 3 separate modules (asp.net applications)
that provide other functionalities.
I want to be able to develop the modules independently and then copy
the aspx pages and the dll into a sub directory of the core webapp.
The core application should be able to call those pages.
Currently calling the module page fails since it cannot find the
codebehind logic in the core dll. How do I programmatically make the
module aspx page get its own dll but still work in the http context of
the core web app.?
thanks,
drew
core asp.net application and 3 separate modules (asp.net applications)
that provide other functionalities.
I want to be able to develop the modules independently and then copy
the aspx pages and the dll into a sub directory of the core webapp.
The core application should be able to call those pages.
Currently calling the module page fails since it cannot find the
codebehind logic in the core dll. How do I programmatically make the
module aspx page get its own dll but still work in the http context of
the core web app.?
thanks,
drew