Command "csc" is not valid.

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Thom Little

    Command "csc" is not valid.

    Under Visual Studio .NET 2003 I went to

    View | Other Windows | Command Window and issued

    csc /t:module StringLib.cs

    It responded with ...

    Command "csc" is not valid.

    What do I need to correct?


    --
    -- Thom Little -- www.tlaNET.net -- Thom Little Associates, Ltd.
    --



  • Morten Wennevik

    #2
    Re: Command "csc&qu ot; is not valid.

    Yes, the command window has nothing to do with the command prompt. For
    that you can use Start->Programs->Visual Studio->Tools->Visual Studio
    Command Prompt (or some similar looking path)
    Or you could use a regular command window Start->Run->"cmd" and make sure
    you have the path to csc.exe written in your path statement under
    environment options.

    The command window is something you use while debugging. Like entering
    the name of a global variable in the command window will give you it's
    current value.


    --
    Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
    For a laugh, try web browsing with Opera's User Mode and Nostalgia enabled

    Comment

    • Thom Little

      #3
      Re: Command "csc&qu ot; is not valid.

      I found it ... it is a separate tool ... "but the light is so much brighter
      over there"

      --
      -- Thom Little -- www.tlaNET.net -- Thom Little Associates, Ltd.
      --

      "Thom Little" <thom@tlanet.ne t> wrote in message
      news:e2NJRPC4DH A.488@TK2MSFTNG P12.phx.gbl...[color=blue]
      > Under Visual Studio .NET 2003 I went to
      >
      > View | Other Windows | Command Window and issued
      >
      > csc /t:module StringLib.cs
      >
      > It responded with ...
      >
      > Command "csc" is not valid.
      >
      > What do I need to correct?
      >
      >
      > --
      > -- Thom Little -- www.tlaNET.net -- Thom Little Associates, Ltd.
      > --
      >
      >
      >[/color]


      Comment

      • Miha Markic

        #4
        Re: Command &quot;csc&qu ot; is not valid.

        Hi Thom,

        I guess you'll have to add "C:\WINDOWS\Mic rosoft.NET\Fram ework\v1.1.4322 "
        (assuming .net 1.1 is installed in that folder) to PATH command environment
        varaible.

        --
        Miha Markic - RightHand .NET consulting & software development
        miha at rthand com


        "Thom Little" <thom@tlanet.ne t> wrote in message
        news:e2NJRPC4DH A.488@TK2MSFTNG P12.phx.gbl...[color=blue]
        > Under Visual Studio .NET 2003 I went to
        >
        > View | Other Windows | Command Window and issued
        >
        > csc /t:module StringLib.cs
        >
        > It responded with ...
        >
        > Command "csc" is not valid.
        >
        > What do I need to correct?
        >
        >
        > --
        > -- Thom Little -- www.tlaNET.net -- Thom Little Associates, Ltd.
        > --
        >
        >
        >[/color]


        Comment

        • Morten Wennevik

          #5
          Re: Command &quot;csc&qu ot; is not valid.

          On Wed, 21 Jan 2004 14:48:47 +0100, Morten Wennevik
          <MortenWennevik @hotmail.com> wrote:
          [color=blue]
          > Or you could use a regular command window Start->Run->"cmd" and make
          > sure you have the path to csc.exe written in your path statement under
          > environment options.[/color]

          That should read "Or you could use a regular command prompt ..." not
          window.


          --
          Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
          For a laugh, try web browsing with Opera's User Mode and Nostalgia enabled

          Comment

          • Thom Little

            #6
            Re: Command &quot;csc&qu ot; is not valid.

            If you run it from the shortcut provided in the Tools Folder it takes care
            of the configuration when you load it. If you launch it this way you do not
            have to manipulate the Path statement.

            --
            -- Thom Little -- www.tlaNET.net -- Thom Little Associates, Ltd.
            --

            "Miha Markic" <miha at rthand com> wrote in message
            news:OxcDzYC4DH A.3944@tk2msftn gp13.phx.gbl...[color=blue]
            > Hi Thom,
            >
            > I guess you'll have to add "C:\WINDOWS\Mic rosoft.NET\Fram ework\v1.1.4322 "
            > (assuming .net 1.1 is installed in that folder) to PATH command[/color]
            environment[color=blue]
            > varaible.
            >
            > --
            > Miha Markic - RightHand .NET consulting & software development
            > miha at rthand com
            > www.rthand.com[/color]


            Comment

            Working...