Having a bit of problems with the studio after installing it. First, when using C++, I get these "numbers" before each row in the output window when compiling.
Eg,
1>------ Rebuild All started: Project: Quicklinks Dll, Configuration: Debug Win32 ------
2>------ Rebuild All started: Project: Tooltips, Configuration: Debug Win32 ------
1>Deleting intermediate and output files for project 'Quicklinks Dll', configuration 'Debug|Win32'
2>Deleting intermediate and output files for project 'Tooltips', configuration 'Debug|Win32'
1>Compiling...
Second is IntelliSense. It's acting all stupid again. For example, in the main file where the startup code is (using MFC), it detects all GLOBAL functions, but it does NOT detect the CLASS that is in there. That's one example. Deleting the intellisense file so that visual studio rebuilds it does not help.
Third, IntelliSense FAILS to resolve almost anything. So typing "pOptionsDlg->" brings up NOTHING (pOptionsDlg is a dialog). Deleting the intellisense file so that visual studio rebuilds it does not help.
I haven't had any beta versions installed on this machine.
Visual Studio Issues
Hot Topic
- time.h(145) : error C2144: syntax error : 'int' should be preceded by ';'
- Can't play games on Club Pogo
- LNK2005 from a C++/CLI dll linking against a non-CLR C++ static library
- 2005 Resource Editor trashes non-English languages when you edit any dialog
- Project fatal error LNK1120: 296 unresolved externals
- create binary file
- PostQuitMessage Issue
- Visual C++ 2005 MFC support
- help for Errors in VC 6.0
- Scanning a Database???
Visual C++
- using DLLs
- Handling Running Processes
- #pragma comment manifestDependency
- random numbers that does not start at 1
- help creating a .dbg file
- Win32 File Writing Problem
- 64Bit-Unable to Register COM dll using regsvr32.exe on WinXP64 bit and AMD64bit machine
- How to use different compiler versions with same VC6 IDE
- PRJ0003 : Error spawning 'cl.exe' and resulting error question
- Moving CDialog with the parent window
Visual Studio Issues
Josh L
Rothariger
on the first issue: the numbers are the number of the thread that performed the associated build action, when multi-threaded build is enabled (when you have a multi-processor machine it is enabled by default). you can turn off multi-threaded build (in the tools->options dialog on the projects and solutions page) if you so desire.
I don't know what the intellisense issue is exactly, but when intellisense fails to provide information it is sometimes because it failed to parse your code at some point prior to where it is failing. sometimes you can locate where the failure to parse has occurred (by finding the point where intellisense stops working) and determine what code caused it to fail. sometimes changing that code around may "fix" the parse and re-enable intellisense. of course, this isn't always possible...
josh
vc++ project system developer
Niko331
interesting. are you building the configuration with /ZI (capital "i") and is the checkbox at "tools->options->debugging->edit and continue->enable edit and continue" set
I don't know what is causing the problem with the .ilk file. you are correct, it is used for incremental linking. you can turn incremental linking off (linker->general property page, set "enable incremental linking" to "no"), but that will mean your link times will probably be longer.
perhaps someone else knows what might be going on with the .ilk file
josh
VC++ project system developer
Paul Johansen
But the thing is that it won't let me apply ANY change at all. Even if I simple change the value assigned to a varaible (which should work), it will not allow me to apply the new changes. It requires that I stop debugging and rebuild.
Also, I noticed that Visual Studio tends to complain that the "ilk" file, I think, is invalid each time it builds. I think it is used for faster linking Even if I would delete it (rebuild), the next time it builds, it would complain it is invalid.
tbiggins
Edit & Continue doesn't seem to work. It's enabled for C++, but it doesn't seem to be able to do it. When I modify the code when debugging, it simply tells me that the source has changed and is not matching the exe. The apply code changes command is always disabled. And the project is built for edit & continue to work.
David Kelsall
IntelliSense seems to have kicked in again for some strange reason. It works again.
However...
Some things that modify the code (like adding a member variable to an MFC dialog) takes a long time and C# projects (well, at least the one I tested) refused to run. I will further if I can see any other problems.