Home > Software engineering >  Visio studio function right "to define" to jump
Visio studio function right "to define" to jump

Time:11-14

I use VS2013 function right "to define" jump to function declarations, unable to jump into the function implementation,

CodePudding user response:

Install a VAX

CodePudding user response:

The clean off to recompile all try? Or delete some cache files related engineering, arguably vc6

CodePudding user response:

The reconstruction project
Restart VS
Repair or reinstall VS
Restart computer
.

CodePudding user response:

Delete the SDF files, recompile, give it a try

CodePudding user response:

*. DSP (DeveloperStudio Project) : is vc + + Project configuration file, such as your Project which contains files, what is your compiler options, and so on, is according to compile. DSP configuration,
*. DSW (DeveloperStudio Workspace) : is the Workspace file, used to configure the project file, it can point to one or more. DSP file,
*. CLW: is ClassWizard file information, is actually the INI file format, are interested can look at. Sometimes ClassWizard problems and manually modify the CLW file can solve. If the file does not exist, each time by ClassWizard painting tips if you rebuild,
*. Opt: engineering documents about development environment parameters, such as the toolbar position information,
*. The aps (AppStudio File), auxiliary File resources, binary format, generally don't tube he,
*. Rc: a resource file, often in the application to use some of the bitmap, menus such as resources, in the VC to rc for extension of the file is called a resource file, which contains the application used in all the Windows resource, it is to point out that the rc files can be directly in the integrated environment of VC to edit and modify in a visual way,
*. PLG: to compile information file, compile time error and warning information file (in fact is an HTML file, generally useful), in the Tools - & gt; The Options there are Options to control the generation of this file,
*. HPJ: (Help Project) is to generate Help files of the Project, with a sidekick, Help the Compiler can handle,
*. MDP (Microsoft DevStudio Project) is the old version of the Project file, if you want to open this file, it will prompt you whether into a new DSP format,
* : BSC is used to Browse the Project information, if use the Source Brower, you must have this File, if don't use this function, can be in the Project Options inside take out the Generate Browse the Info File, you can speed up the compilation,
*. The map: record file is executable image information, unless very familiar with the underlying system, this file generally don't have to,
*. PCH (Pre - Compiled File) is precompiled files, you can speed up the compilation, but the File is very large,
*. PDB: (the Program Database) record the Program about some of the data and debug information, can be useful when debugging,
*. Exp: only when compile DLL will generate, record some information of the DLL, generally also useless,
*. NCB: no compile browse the file (no compile browser), when autocomplete feature a problem you can delete this file, after the build is automatically generated,
*. Suo (solution user options) solution user option, all records will establish associated with solution options, so that every time in the open, it contains the user Settings, such as v layout and project finally compiled without turn off file is used to open the next time, and among them, VS layout including: a monitor 1234 variables list, breakpoint marker and switch state, output window error window, and the distribution of the suspended state, such as, unloading and project status labels, suo file will occasionally be destroyed, to build and edit applications appear unexpected results, if Visual Studio for each solution is not stable, should be deleted. Suo file, the next time you open the solution, Visual Studio will rebuild it,
*. C: source code files, compiled by c language usage,
*. CPP: source code files, compiled by c + + syntax processing,
*. H is the header file, generally used as a statement and global definition,
*. SLNS: detected in a development environment using the solution file, it will be one or more projects of all elements of the organization into a single solution, the file is stored in the parent project directory. The solution file, he is one or more. Proj (project documents) collection,
*. Vcproj is vc project file
. Vcproj. SLNS were detected VC2002 above project and solution files
. DSP. DSW respectively is VC6 project file and engineering group
Transform VC7 engineering back VC6 project, in other words, is will. SLNS/. Detected vcproj this two files into. DSW/. DSP file,
Vc6 open DSP or DSW, vc2003, 2005 open the SLNS or detected vcproj
VC6 open *. DSW file, click on the toolbar "!" And then in your folder there are more than a DEBUG folder. EXE file
Inside the vc7 open vc6 project, whether it will prompt you to convert the format of the vc7, can use directly after conversion,
Engineering after the transformation, vc6 don't know, I use vc.net 2003 open vc6 project, suggest to upgrade, I also choose yes to all,
But actually vc.net only read vc6. DSW and. The information in the DSP and added. SLNS and detected. Vcproj,
Use vc.net to open a vc6 project DSW and DSP has not changed, so use vc.net opened vc6 project, although have been "upgrade" actually DSW and DSP is not change, then you won't have to DSW and open SLNS was detected,
This do well, just read from vc6 project file information, does not change, still can use vc6 to open the original DSW and DSP

CodePudding user response:

Reinstall the

CodePudding user response:

Unloading, clean junk files, reinstall,

CodePudding user response:

This issue has baffled me too, but I can jump, later have time for a project is found washed-up, at that time still feel confuse the compilation environment, but when I find all references, found a phenomenon, is a function definition and that place is a little different,

Int fun (int, int);//function declaration and called in a file f1. C

Int fun (para1, para2)//function defined in another file f2. C
Int para1, para2;
{
}

This is an old form of C function definition K& R, into a new kind of ANSI, such as int fun (int para1, int para2) {} in f1. C call fun place to jump to f2. The definition in c, if the call and definition of fun in the same file, as if also can call the definition of the old form, on different projects (in a solution), such as project 1 is normal exe project, project 2 is lib project, project 1 call the function in the project 2, also can jump, but this time, I also can't jump, also didn't go to see what reason be, but should is the jump is the same problem in different files, suggested that changed the form of function definition to try new ANSI

CodePudding user response:

Click on the project - & gt; Rescanning solution

CodePudding user response:

Hello, please you solve this problem

CodePudding user response:

It's not that complicated? Is your file is not loaded into the project

CodePudding user response:

In addition to delete can rebuild files, if the computer is slow, just after the open project, engineering information has not been entirely into memory and also will in this way,
In addition the implementation in what place? Is the system of CPP or your own, see if path change
  • Related