Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
tools
vsnet.act
vsnet.debugging
vsnet.documentation
vsnet.enterprise.tools
vsnet.general
vsnet.ide
vsnet.jlca
vsnet.servicepacks
vsnet.setup
vsnet.vsip
vsnet.vss
vsnet.vstools.office
vstudio.development
vstudio.extensibility
vstudio.general
vstudio.helpauthoring
vstudio.setup
vstudio.sourcesafe
  
 
date: Wed, 24 Sep 2008 22:04:01 -0700,    group: microsoft.public.vstudio.general        back       


Migration to VS2008 problem   
I've just migrated from VS2003 to VS2008.  Using C/C++ environment.

On any source text tab, there are two drop-downs.  The left shows the scope 
and the right shows the functions in the scope.

This worked fine for me in VS2003 but exactly the same cpp files in VS2008 
show "unknown scope" to the left and no functions (cause of no scope) to the 
right.

I also notice that, if I right click on a function name and choose 
"definition", nothing happens, because the function is not known to the 
development environment.  This is a manifestation of the same problem, I am 
guessing.

What do I have to do to get scopes and functions recognized again in VS2008? 
 (Note that my code is fairly much generic C and there might be some 
requirements with C++ to make this work that I do not know about).

Thanks,
Tony Duff
date: Wed, 24 Sep 2008 22:04:01 -0700   author:   Tony Duff

Re: Migration to VS2008 problem   
>I've just migrated from VS2003 to VS2008.  Using C/C++ environment.
>
>On any source text tab, there are two drop-downs.  The left shows the scope 
>and the right shows the functions in the scope.
>
>This worked fine for me in VS2003 but exactly the same cpp files in VS2008 
>show "unknown scope" to the left and no functions (cause of no scope) to the 
>right.
>
>I also notice that, if I right click on a function name and choose 
>"definition", nothing happens, because the function is not known to the 
>development environment.  This is a manifestation of the same problem, I am 
>guessing.

Tony,

Ensure that the solution view contains all the relevant source and
header files for your project. Following that, try closing the
solution and deleting the .ncb file.

Dave
date: Thu, 25 Sep 2008 08:16:05 +0100   author:   David Lowndes lid

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us