C++ Visual Studio 2022 Shows suggestions for completely removed functions - c++

Function 'IsSubscribed' was there long time ago. Now it is removed but Visual Studio still shows this message.
Even after restart, even after project reload.
How to fix this?

Related

Sleep() function causes the program to crash in Visual Studio 2015

I tried to use Winsock to implement a socket, and added a Sleep(40) statement after WSACleanup(). After the compilation, when I click on the Local Windows Debugger button, Visual Studio reports an error:
But, when Sleep(40) statement is deleted,the program works well.
I searched the user guide of the Sleep() function and found no restrictions.
Did I miss some settings in Visual Studio 2015? How do I solve this?

If you have Visual Studio 2017 Preview 2 update can you provide me with include/iosfwd file?

I just run into a bug inside Visual Studio 2017 C++ Preview 3; The include file include/iosfwd is missing member seekpos() in class fpos, therefore boost no longer compiles with error error C2039: 'seekpos': is not a member of 'std::fpos<_Mbstatet>'
Microsoft already knows the issue ( https://developercommunity.visualstudio.com/content/problem/282567/member-seekpos-in-class-fpos-is-missing.html?inRegister=true ) with last update 2 days ago.
By reporter, the file include/iosfwd inside VS 2017 Preview 2 is not corrupted. But downgrade is impossible.
If you, by any chance, still have VS 2017 Preview 2 can you post that file (located here: C:\Program Files (x86)\Microsoft Visual Studio\Preview\Community\VC\Tools\MSVC\{Build}\include\iosfwd ) on some gist and post link to it?
The inability to compile boost program is a blocking issue for our project.
Got it on the linked issue (as solution): https://developercommunity.visualstudio.com/content/problem/282567/member-seekpos-in-class-fpos-is-missing.html?inRegister=true

Visual Studio 2015 hangs when compiling and linking projects

I recently made the change to Visual Studio 2015 from Visual Studio 2012 as my compiler for my c++ projects. After making this change I have noticed that visual studio will frequently hang in the build process.
This never occurred with Visual Studio 2012. The hangups are at random points and do not occur at the same build points in my projects.
When I ran VS in administrator mode and got all of the cl.exe's and link.exe's to appear as command prompts I was able to see when they hung. And there were no errors thrown or anything.
The only way I have successfully worked around this issue is by setting Visual Studio's build process to only process one project at a time and use only one compilation simultaneously. However I cant maintain this as my build time is somewhere around 3-4 hours (Yes, this is a HUGE project).
I think this is a duplicate of Visual Studio 2015 Win64 hangs during solution build. I posted an answer there. In short, there may be a patch that resolves the issue:
https://www.microsoft.com/en-us/download/details.aspx?id=51161

Visual Studio 2012 Stuck Initialising

I've had this message for awhile in Visual Studio 2012.
I have installed RxCpp via Nuget. When i use rxcpp::from(merged).merge(i) Visual Studio spends a good hour parse solution files. I am now stuck on this, it started at 0 of 7 files, it'now 0 of 11.... a number of hours later.
https://rxcpp.codeplex.com/
Any clues what i going on here?
The include is in the project's main.cpp is fine until i use a function from this library.
Some sources have suggested Project C++ options and changing Disable Database to false. Which it already is. Others, suggest restarting solution, but we get the same thing.
Totally lost.

BEGIN_MSG_MAP_EX breaks Visual Studio 2005 intellisense?

I have a C++ application using WTL/ATL BEGIN_MSG_MAP_EX macros for message handling. I use some macros from atlcrack.h.
When we upgraded the projects to Visual Studio 2005, intellisense acts crazy. I've tracked the behavior down to the BEGIN_MSG_MAP_EX macro not behaving correctly with intellisense. However, I can not find a way to continue using BEGIN_MSG_MAP_EX and Visual Studio 2005.
Do I have to rewrite all my old message handlers and stop using BEGIN_MSG_MAP_EX or is there another fix?
I've been using WTL for years and haven't come across this issue, but I also find the default Intellisense in VS2005/2008 next to useless - it stops working for no apparent reason. If you want Intellisense to work the way God intended, I recommend you try Visual Assist X (free 30 day trial) - it might make your problem disappear - got to be better than changing your code to work around IDE problems?
http://www.wholetomato.com/