J
Joe Kovac
Hi!
I have two Web Application Projects. The main Web Application Project
and the additional WAP.
The main WAP has many features build in, like DataAccess, Login, a.s.o.
The additional WAP shall just extend the main WAP with 2 or 3 more ASPX
pages. The additional WAP references the main WAP. It can access the
objects of the main WAP without problems. But when I run the solution
(with the addional WAP being the start up project) I can't access the
main WAP's ASPX pages. How can I make the main WAP's aspx pages
accessable??? (So that I can easily debug the application and not with
some extra steps like deploying..)
Thanks
Joe
I have two Web Application Projects. The main Web Application Project
and the additional WAP.
The main WAP has many features build in, like DataAccess, Login, a.s.o.
The additional WAP shall just extend the main WAP with 2 or 3 more ASPX
pages. The additional WAP references the main WAP. It can access the
objects of the main WAP without problems. But when I run the solution
(with the addional WAP being the start up project) I can't access the
main WAP's ASPX pages. How can I make the main WAP's aspx pages
accessable??? (So that I can easily debug the application and not with
some extra steps like deploying..)
Thanks
Joe