« Previous Next »

Thread: IIS 7 - FRAMEWORK 3.5 - Debug fails to see javascript breakpoints (WIN XP Pro)

Last post 03-05-2009 1:08 AM by DomNotDOM. 2 replies.

Average Rating Rate It (5)

RSS

Page 1 of 1 (3 items)

Sort Posts:

  • 02-04-2009, 6:24 PM

    • DomNotDOM
    • Not Ranked
    • Joined on 06-03-2003, 12:38 PM
    • Posts 5

    IIS 7 - FRAMEWORK 3.5 - Debug fails to see javascript breakpoints (WIN XP Pro)

    .
    I am in a soup of weak understanding.

    May save yourself some time, by reading the next reply... as IE 8 seems to be the source of the problem.

    SETUP:
    I installed 3.5 ajax, IIS 7, 3.5 framework, and Visual Studio 2008, on XP PRO.
    All good all functioning well, debugging (javascript, HTML, VB).
    Intellisense working in all 3 languages, isn't that simply beautiful.

    • This is on a startup project with 4 html/aspx pages accessing my SQLServer 2005 without any problems, and doing postbacks via the ajax ScriptManager mechanism, sweetly.  Couldn't be better!

    ERROR:
    ...after weeks of working great, problem with breakpoints in javascript being ignored.

    TROUBLESHOOTING:
    I have done everything suggested in 1 million forums, to no avail.

    • Yes, I do place a breakpoint in the VB codebehind, and it hits that one.
    • Partial list of things that I checked, or ran:
      • IE Intenet Options - Advanced
        • Disable script debugging (IE) unchecked
        • Disable script debugging (Other) unchecked
      • IIS Virtual Directory TAB
        • Local path... points to folder where project is
          \MydevArea\MyProjects\ProjectName\(all files here)
          \inetpub\wwwroot\ProjectName\(no files here)
        • IIS Application Protection Medium Pooled
        • Configuration/Mappings
          • C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\****
        • Configuration/Debugging
          • Enable ASP server-side script debugging checked
          • Enable ASP client-side script debugging checked
      • web.config
        • Debug = true
      • ran both commands in command window
        • C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 - aspnet_regiis -i
        • C:\WINDOWS\Microsoft.NET\Framework\v3.5 - WFServicesReg.exe /c
      • Project Properties, Compile
        • Debug(Active)... it keeps reverting to that even though I keep setting it to 'Debug'
        • I have had it see the breakpoints in javascript while switching this setting to Debug, while in a debug session. ???  was not able to duplicate that.
      • Project Properties, Compile - Advanced
        • Set Debug Constant checked
        • Set Trace Constant checked
        • Target CPU AnyCPU
        • Target Framework 3.5 (All configurations)
      • Project Properties, WEB
        • Use IIS web server - checked
        • debuggers - ASP.NET checked (Native and SQL unchecked)
        • Noticed the Visual Studio Development server does not see javascript
          ...but I faintly remember that when I used it when I first installed, I believe it did...(may be wrong on that one)

    DISCREPANCIES(The only reason I became aware of these discrepancies is thru troubleshooting the breakpoints issue.)

    1. The ASP.NET version in IIS shows 2.xxxxxx, was expecting 3.5.
      Ok! I now know that 3.5 is an extension thus 2.xxx is still the base (aspnet_isapi.dll).
    2. Even though I have installed IIS 7.0(and is shows correctly in the Add Programs), when I check the version under the Help-About of the IIS console, it shows 5.1
      Is 7 not installed? or is the version on the IIS panel the version of the console?

    QUESTIONS:

    1. Did either of the commands I ran under the command window do any damage?
    2. How do I know IIS 7.0 is really installed?  ...given discrepancy 2.
    3. Can you see anything I need to check that might resolve the issue of the breakpoints in javascript?
      I am praying the answer is here, not in 4. below.
    4. I am at the end of my wits on this one, and I am contemplating reinstalling!
      1. I will first create a new project and rebuild one page at a time to see if I get success.
      2. If 1 fails, and I do reinstall:
        1. what should I UNINSTALL, ZAP, in WHAT order?
          be clear as to exactly what, including whether a folder is to be removed along with its contents.
        2. ...and what should I INSTALL in WHAT ORDER!
        3. DO I HAVE TO reINSTALL all of:
          Framework(s), IIS, Visual Studio?

    I can only thank you in advance.
    NicMartel

  • 02-07-2009, 12:34 AM In reply to

    • DomNotDOM
    • Not Ranked
    • Joined on 06-03-2003, 12:38 PM
    • Posts 5

    Re: IIS 7 - FRAMEWORK 3.5 - Debug fails to see javascript breakpoints (WIN XP Pro)

    I may have found the answer...

    I recently upgraded my IE 8 Beta to the production version IE 8.
    When I take some of my initial pages out of the sequence, all is good.
    It seems that some of the commands I use to resize and manipulate the browser window
    in those initial pages are the source(not forcefully the cause) of the problem.

    No errors in compilation, nor any errors in runtime.
    ONLY the debugger fails when these pages are in the flow. ???
    Worked great on IE 8 Beta...  Microsoft ???

    ...thus I do all my testing without those pages, but instate them once everything debugged!

  • 03-05-2009, 1:08 AM In reply to

    • DomNotDOM
    • Not Ranked
    • Joined on 06-03-2003, 12:38 PM
    • Posts 5

    Re: IIS 7 - FRAMEWORK 3.5 - Debug fails to see javascript breakpoints (WIN XP Pro)

    See my other post that may be related.

    Migrating from IIS 5.0 to IIS 7.0

Page 1 of 1 (3 items)
Microsoft Communities