Home > Archive > Visual Studio > July 2004 > VC++ 6.0 "not a valid browse information file" error
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
VC++ 6.0 "not a valid browse information file" error
|
|
|
| I am using Visual Studio C++ 6.0. I have had not problem up until
today. Now I can no longer use "Go to definition" from the context
menu. I get the error message box "This is not a valid browse
information file". I have removed the Debug and Release dirs, closed
the app, reboot my system and I still get this message when I try to
use "Go to definition".
I have searched the internet and groups and have only found questions
but no answers to this issue. Does any one know the cause or a
solution to this problem? Any help is greatly appreciated.
| |
|
| I found why the BSC file is not rebuilt. I am getting the following
error when building in Debug which has the Project, Settings, Browse
Info, Build Browse Info check box checked. This has always been check
and I use the "Go to definition" often. Starting today so some reason
I am receiving this error
Creating browse info file...
BSCMAKE: warning BK4502 : truncated .SBR file '.\Debug\StdAfx.sbr' not
in Debug/P1.bsc
BSCMAKE: error BK1513 : nonincremental update requires all .SBR files
Error executing bscmake.exe.
P1.exe - 1 error(s), 1 warning(s)
The StdAfx.sbr is only 1345KB. There are other SBR files bigger than
this one. Does anyone know why I might be getting this error and how I
can fix it?
Thanks,
mark@financialzinc.com (Mark) wrote in message news:<c0f5de8d.0407211001.696ff386@posting.google.com>...
> I am using Visual Studio C++ 6.0. I have had not problem up until
> today. Now I can no longer use "Go to definition" from the context
> menu. I get the error message box "This is not a valid browse
> information file". I have removed the Debug and Release dirs, closed
> the app, reboot my system and I still get this message when I try to
> use "Go to definition".
>
> I have searched the internet and groups and have only found questions
> but no answers to this issue. Does any one know the cause or a
> solution to this problem? Any help is greatly appreciated.
|
|
|
|
|