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. General Programming
  3. WPF
  4. VS2010 SL4 Debugging [SOLVED]

VS2010 SL4 Debugging [SOLVED]

Scheduled Pinned Locked Moved WPF
debugginghelpwpfcombeta-testing
12 Posts 5 Posters 2 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.
  • realJSOPR Offline
    realJSOPR Offline
    realJSOP
    wrote on last edited by
    #1

    I installed VS2010 and SL4 (with tools and toolkit), and I can't get the debugger to stop anywhere in the code in a silverlight (v4) app - not even the first line of the constructor in App.xaml.cs. Can anyone help? (and before anyone asks, yes, the solution configuration is set for debug) SOLUTION ====================== It seems that it's because FireFox executes plug-ins out-of-process, so the debugger can't attach to the appropriate process. The fix is described here: On MSDN Connect[^]

    .45 ACP - because shooting twice is just silly
    -----
    "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
    -----
    "The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001

    modified on Sunday, July 4, 2010 9:45 AM

    RaviBeeR M M A 4 Replies Last reply
    0
    • realJSOPR realJSOP

      I installed VS2010 and SL4 (with tools and toolkit), and I can't get the debugger to stop anywhere in the code in a silverlight (v4) app - not even the first line of the constructor in App.xaml.cs. Can anyone help? (and before anyone asks, yes, the solution configuration is set for debug) SOLUTION ====================== It seems that it's because FireFox executes plug-ins out-of-process, so the debugger can't attach to the appropriate process. The fix is described here: On MSDN Connect[^]

      .45 ACP - because shooting twice is just silly
      -----
      "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
      -----
      "The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001

      modified on Sunday, July 4, 2010 9:45 AM

      RaviBeeR Offline
      RaviBeeR Offline
      RaviBee
      wrote on last edited by
      #2

      John Simmons / outlaw programmer wrote:

      the solution configuration is set for debug

      But perhaps it's missing this[^]? /ravi

      My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com

      realJSOPR 1 Reply Last reply
      0
      • realJSOPR realJSOP

        I installed VS2010 and SL4 (with tools and toolkit), and I can't get the debugger to stop anywhere in the code in a silverlight (v4) app - not even the first line of the constructor in App.xaml.cs. Can anyone help? (and before anyone asks, yes, the solution configuration is set for debug) SOLUTION ====================== It seems that it's because FireFox executes plug-ins out-of-process, so the debugger can't attach to the appropriate process. The fix is described here: On MSDN Connect[^]

        .45 ACP - because shooting twice is just silly
        -----
        "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
        -----
        "The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001

        modified on Sunday, July 4, 2010 9:45 AM

        M Offline
        M Offline
        Mycroft Holmes
        wrote on last edited by
        #3

        Ran across something similar in VS2008 where the start project was set to the .web project, changing the start project to the main project fixed the problem - just a thought

        Never underestimate the power of human stupidity RAH

        realJSOPR 1 Reply Last reply
        0
        • realJSOPR realJSOP

          I installed VS2010 and SL4 (with tools and toolkit), and I can't get the debugger to stop anywhere in the code in a silverlight (v4) app - not even the first line of the constructor in App.xaml.cs. Can anyone help? (and before anyone asks, yes, the solution configuration is set for debug) SOLUTION ====================== It seems that it's because FireFox executes plug-ins out-of-process, so the debugger can't attach to the appropriate process. The fix is described here: On MSDN Connect[^]

          .45 ACP - because shooting twice is just silly
          -----
          "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
          -----
          "The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001

          modified on Sunday, July 4, 2010 9:45 AM

          M Offline
          M Offline
          Mamta D
          wrote on last edited by
          #4

          Do you have Visual Web Developer installed? When you install VS 2010, it includes this but in case you have chosen a different mode of install and omitted the Visual Web developer then it could be an issue. Do check and see. -Mamta

          realJSOPR 1 Reply Last reply
          0
          • RaviBeeR RaviBee

            John Simmons / outlaw programmer wrote:

            the solution configuration is set for debug

            But perhaps it's missing this[^]? /ravi

            My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com

            realJSOPR Offline
            realJSOPR Offline
            realJSOP
            wrote on last edited by
            #5

            Nope, that's checked.

            .45 ACP - because shooting twice is just silly
            -----
            "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
            -----
            "The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001

            1 Reply Last reply
            0
            • M Mamta D

              Do you have Visual Web Developer installed? When you install VS 2010, it includes this but in case you have chosen a different mode of install and omitted the Visual Web developer then it could be an issue. Do check and see. -Mamta

              realJSOPR Offline
              realJSOPR Offline
              realJSOP
              wrote on last edited by
              #6

              I have "Visual Studio Web Authoring Component", but that was installed with VS2008.

              .45 ACP - because shooting twice is just silly
              -----
              "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
              -----
              "The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001

              1 Reply Last reply
              0
              • M Mycroft Holmes

                Ran across something similar in VS2008 where the start project was set to the .web project, changing the start project to the main project fixed the problem - just a thought

                Never underestimate the power of human stupidity RAH

                realJSOPR Offline
                realJSOPR Offline
                realJSOP
                wrote on last edited by
                #7

                It still doesn't stop (and I get a warning that if I don't set the web project as startup, I can't debug the RIA services stuff.

                .45 ACP - because shooting twice is just silly
                -----
                "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
                -----
                "The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001

                1 Reply Last reply
                0
                • realJSOPR realJSOP

                  I installed VS2010 and SL4 (with tools and toolkit), and I can't get the debugger to stop anywhere in the code in a silverlight (v4) app - not even the first line of the constructor in App.xaml.cs. Can anyone help? (and before anyone asks, yes, the solution configuration is set for debug) SOLUTION ====================== It seems that it's because FireFox executes plug-ins out-of-process, so the debugger can't attach to the appropriate process. The fix is described here: On MSDN Connect[^]

                  .45 ACP - because shooting twice is just silly
                  -----
                  "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
                  -----
                  "The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001

                  modified on Sunday, July 4, 2010 9:45 AM

                  A Offline
                  A Offline
                  Abhinav S
                  wrote on last edited by
                  #8

                  Found this thread - it might help you. Note: The workaround suggests that if VS2010 is run in administrator mode, this problem goes away.

                  realJSOPR 1 Reply Last reply
                  0
                  • A Abhinav S

                    Found this thread - it might help you. Note: The workaround suggests that if VS2010 is run in administrator mode, this problem goes away.

                    realJSOPR Offline
                    realJSOPR Offline
                    realJSOP
                    wrote on last edited by
                    #9

                    Nope - it has no effect. I wonder if it's because I have VS2008 and all the SL3 stuff installed...

                    .45 ACP - because shooting twice is just silly
                    -----
                    "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
                    -----
                    "The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001

                    A 1 Reply Last reply
                    0
                    • realJSOPR realJSOP

                      Nope - it has no effect. I wonder if it's because I have VS2008 and all the SL3 stuff installed...

                      .45 ACP - because shooting twice is just silly
                      -----
                      "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
                      -----
                      "The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001

                      A Offline
                      A Offline
                      Abhinav S
                      wrote on last edited by
                      #10

                      John Simmons / outlaw programmer wrote:

                      VS2008 and all the SL3

                      I had VS2008 installed and debugging VS 2008 did not create any issues for me. I was however using SL3 even in VS2010 - so it could be something to do with having the SL3 and SL4 tools installed together.

                      The funniest thing about this particular signature is that by the time you realise it doesn't say anything it's too late to stop reading it.

                      realJSOPR 1 Reply Last reply
                      0
                      • A Abhinav S

                        John Simmons / outlaw programmer wrote:

                        VS2008 and all the SL3

                        I had VS2008 installed and debugging VS 2008 did not create any issues for me. I was however using SL3 even in VS2010 - so it could be something to do with having the SL3 and SL4 tools installed together.

                        The funniest thing about this particular signature is that by the time you realise it doesn't say anything it's too late to stop reading it.

                        realJSOPR Offline
                        realJSOPR Offline
                        realJSOP
                        wrote on last edited by
                        #11

                        Look at the OP - I found out what was wrong.

                        .45 ACP - because shooting twice is just silly
                        -----
                        "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
                        -----
                        "The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001

                        A 1 Reply Last reply
                        0
                        • realJSOPR realJSOP

                          Look at the OP - I found out what was wrong.

                          .45 ACP - because shooting twice is just silly
                          -----
                          "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
                          -----
                          "The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001

                          A Offline
                          A Offline
                          Abhinav S
                          wrote on last edited by
                          #12

                          Cool. Thanks for posting the solution here.

                          The funniest thing about this particular signature is that by the time you realise it doesn't say anything it's too late to stop reading it.

                          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