TECH TIP: Break - Edit - Continue alternatives - Page 2


DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Page 2 of 2 FirstFirst 12
Results 16 to 20 of 20

Thread: TECH TIP: Break - Edit - Continue alternatives

  1. #16
    Jeff Pipes Guest

    Re: TECH TIP: Break - Edit - Continue alternatives


    Also -

    ?1+1
    The expression cannot be evaluated while in run mode.
    ?Len("hello world")
    The expression cannot be evaluated while in run mode.

    -Jeff

    "Jeff Pipes" <JeffP622@msn.com> wrote:
    >
    >What good is the immediate window if you can't run code?
    >
    >?len("asdf")
    >The expression cannot be evaluated while in design mode.
    >?22/7
    >The expression cannot be evaluated while in design mode.
    >
    >-Jeff


  2. #17
    Phil Weber Guest

    Re: TECH TIP: Break - Edit - Continue alternatives

    > ? Len("hello world")

    Jeff: The above works in run mode in my (RC) copy of VS.NET. So does "? 1 +
    1". I find the Command Window quite useful for examining/changing the values
    of variables at runtime, for debugging purposes.
    ---
    Phil Weber



  3. #18
    Jeff Pipes Guest

    Re: TECH TIP: Break - Edit - Continue alternatives


    I've tried this on three different PCs, 2 running RC1 and 1 running beta 2,
    and everytime VS.NET tells me "the expression cannot be evaluated." Is there
    some kind of trick to get this to work?

    -Jeff

    "Jeff Pipes" <JeffP622@msn.com> wrote:
    >
    >What good is the immediate window if you can't run code?
    >
    >?len("asdf")
    >The expression cannot be evaluated while in design mode.
    >?22/7
    >The expression cannot be evaluated while in design mode.
    >
    >-Jeff
    >
    >"Rob Teixeira" <RobTeixeira@@msn.com> wrote:
    >>
    >>"Larry Serflaten" <serflaten@usinternet.com> wrote:
    >>>
    >>>To change a variable, select View/Other Windows/Command Window from
    >>>the IDE menu, then enter 'immed' after the prompt in the command window.
    >>>You can then issue commands from the current development language by
    >>>typing in the command and pressing Enter. (Help says '>' is needed ahead

    >>of
    >>>the command, I found otherwise using VB.Net.)
    >>>

    >>
    >>The Command and Immediate functionality share the same window. The '>'

    character
    >>appears automatically in front of any line under Command mode, but does

    >not
    >>appear (and is not used) in Immediate mode.
    >>VS commands (such as SaveAll, etc.) can only be invoked while in Command
    >>mode.
    >>
    >>To switch from Command mode to Immediate mode: immed[enter]
    >>
    >>To switch from Immediate mode to Command mode: >Cmd[enter]
    >>
    >>-Rob

    >



  4. #19
    Larry Serflaten Guest

    Re: TECH TIP: Break - Edit - Continue alternatives


    "Jeff Pipes" <JeffP622@msn.com> wrote
    >
    > What good is the immediate window if you can't run code?
    >
    > ?len("asdf")
    > The expression cannot be evaluated while in design mode.
    > ?22/7
    > The expression cannot be evaluated while in design mode.
    >
    > -Jeff


    They work for me (Beta 2). I set a breakpoint, ran to the break, and
    then entered 'immed' on a new line in the Command window. That
    put it in Immediate mode (noted in its Caption), where I could type
    in your statements and see the responses...

    LFS



  5. #20
    Jeff Pipes Guest

    Re: TECH TIP: Break - Edit - Continue alternatives


    I think I may have figured it out. It only works in run-mode when you hit
    a breakpoint? In VB6, you could run code in the immediate window pretty much
    whenever you wanted, even at design time. I guess this is better than nothing.


    -Jeff

    "Larry Serflaten" <serflaten@usinternet.com> wrote:
    >
    >"Jeff Pipes" <JeffP622@msn.com> wrote
    >>
    >> What good is the immediate window if you can't run code?
    >>
    >> ?len("asdf")
    >> The expression cannot be evaluated while in design mode.
    >> ?22/7
    >> The expression cannot be evaluated while in design mode.
    >>
    >> -Jeff

    >
    >They work for me (Beta 2). I set a breakpoint, ran to the break, and
    >then entered 'immed' on a new line in the Command window. That
    >put it in Immediate mode (noted in its Caption), where I could type
    >in your statements and see the responses...
    >
    >LFS
    >
    >



Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center