mitesh114
asked on
Debugging ascx pages
HI,
I am working with the dnn gallery which consists of a number of ascx pages and vb code behind pages. I want to debug the gallery as a standalone application without first uploading to dotnetnuke as doing this removes the code behind files. How would I do this? Would I set up a button in an aspx page and call the gallery methods in the button click event? Not quite sure how to do this.
Hope someone can help.
Thanks
I am working with the dnn gallery which consists of a number of ascx pages and vb code behind pages. I want to debug the gallery as a standalone application without first uploading to dotnetnuke as doing this removes the code behind files. How would I do this? Would I set up a button in an aspx page and call the gallery methods in the button click event? Not quite sure how to do this.
Hope someone can help.
Thanks
ASKER
so do I just add an aspx page to the solution?
yes
Add the aspx page.
you need the line right at the top of the page to register your custom tag and implement it. like so:
<%@ Register TagPrefix="ARDesigns" TagName="ICaptcha" Src="CAPTCHA.ascx" %>
then use your tag, here is an example of a web control I made:
<ARDesigns:ICaptcha ID="Secure1" runat="server" />
Add the aspx page.
you need the line right at the top of the page to register your custom tag and implement it. like so:
<%@ Register TagPrefix="ARDesigns" TagName="ICaptcha" Src="CAPTCHA.ascx" %>
then use your tag, here is an example of a web control I made:
<ARDesigns:ICaptcha ID="Secure1" runat="server" />
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
whityum, nice
I will now use that myself in some projects, very useful indeed
Andrew :-)
I will now use that myself in some projects, very useful indeed
Andrew :-)
ASKER
What do you mean load it in the backend?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
the "code behind" page is what I meant, or on a server side script tag.
Andrew