I am not a VS IDE develoepr and hence cant say whther it is intentinal or not.

 What I told earlier was typing and compilimg are the two seperate process embedded ina  single application and hence this problem is arising.
 May eb you are right, somethign to do with the programming.
 But I dont see any reason in the need that one want to type something while compiling.

   Microsoft did not intentionally disable the text editor in Visual Studio
   while compiling.  I know this because sometimes you can type in the editor
   while it is compiling and sometimes you cannot.  As a matter of fact, most
   of the time you can type while compiling.  It is the occasional lock up that
   last a few seconds that is annoying.

   The editor is blocked during the final phase of creating the .obj file, just
   before it is written to disk.  I believe this is due to poor use of
   semaphores on the part of the VS IDE developers.

   "Saradhi" <upadrasta@inooga.com> wrote in message
   news:%23lpPq2f%23DHA.2524@TK2MSFTNGP10.phx.gbl...
     It is not required to prove that to edit text and compile at the same time
   using a computer.

     Compiling means compiling and checking whatever you typed so far for
   syntaxing & syntactical errors.
     Both are two processes and compilation depends on what you typed so far
   and hence it is restricted not to type while ehcking the correctness of what
   you typed so far.

     Thats the main reason behind this architecture.
     Again, its not a bug. Its the functionality.

     And coming to your comparision of vi/gcc to VS IDE, Both vi and gcc are
   seperate applications where as typing and compiling are two seperate
   processes embedded in a  single application (VS IDE).
     If Process B (Compiling) depends on Process A (Typing) , its always better
   to restrict Process A while Process B is running.
     Its the design VS follows.

     Hope this clears your doubt.

     "Rudy Ray Moore" <rudymoore@hotmail.com> wrote in message
   news:e8Qx26L9DHA.696@tk2msftngp13.phx.gbl...

       The purpose for comparing the products was to prove that it is possible
   for
       a computer to edit text and compile at the same time.

       VS doesn't let people type and compile at the same time .  This is not
       because "there is not use to type something while compiling."  The real
       reason is because VS was written without care being taken into ensuring
   that
       different components don't unnecessarily block others' functionality.

       Unfortunately, I believe that this is so fundamental a flaw in the way
   VS
       was created, that there is no hope in it being fixed.

       I find it ironic that the simpler approach (vi and gcc on seperate
       processes) works better than the "fancy expensive IDE" in this regard.
   (In
       other regards, like debugging, VS wins hands down.)

       Rudy

       "Saradhi" wrote
       > One cant compare different products.
       > Also there is no use if you want to type soemthing
       > while compiling.
       > I cant understand the reason why you want to add more
       > code while compiling.