Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Web Development
  3. ASP.NET - Debugging User Control in Visual Studio 2008

ASP.NET - Debugging User Control in Visual Studio 2008

Scheduled Pinned Locked Moved Web Development
csharpdebugginghelpjavascriptasp-net
1 Posts 1 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A Offline
    A Offline
    AssemblySoft
    wrote on last edited by
    #1

    I have an ASP.NET (2.0) site. I am on my dev box using V Studio 2008 and IIS. I have a separate User Control project that gets called from a javascript function in the default.aspx page. The User Control project is in another solution. The application is running as expected. The user control is being called and all is well. Well not quite. I am unable to step into the User Control project, i.e debug it. I can set breakpoints but they never get trapped. I can debug all other areas of the site both in script and code behind without any problems. The User control gets built in DEBUG to the same location as the default.aspx page. Things i have already tried: Enabled script debugging in IE. Added the User Control project to the same web site solution Attached debugger to running instance of IE from Visual Studio Enabled debugging on the site. Below is some sample code which should help: default.aspx: (Cut down for brevity)

    <body onload="LoadMethod()"style="background-color:#f4eedf; font-size: 12px; font-family: Verdana;margin:0 0 0 0;">

    <object id="LoadControl" style="width: 1px; height: 1px" classid="Nice.Inform.Client.WebLoad.dll#Nice.Inform.Client.WebLoad.LoadControl">
    <param name="ApplicationPath" value="ClientApps/NiceInform.exe" />
    <asp:Literal ID="NewCodecVersion" runat="server"></asp:Literal>
    <asp:Literal ID="CodecProductCode" runat="server"></asp:Literal>
    </object>

    <script type="text/javascript">
    function LoadMethod()
    {
    try
    {
    LoadControl.Ping();

    		}
    		catch (e) //if the DLL didn't run assume there is a trust problem.
    		{	 
    		}
    	}
    

    Please only give feedback if you have actually done this in practice.

    1 Reply Last reply
    0
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • World
    • Users
    • Groups