They are basically no different, they are used to store and manage references. Just as Lex said, the Dependencies is a better way to represent different types of references, we can clearly know where the reference comes from, SDK, nuget, etc. so that we can manage our references more efficiently.
After selecting All Configurations and All Platforms, navigate to Configuration Properties > Linker > Input > Additional Dependencies. If the list of Additional Dependencies does not contain ws2_32. lib and crypt32. lib, add them.
Your symptoms sound very similar to those I experienced a while ago. Ensure that the projects are set to build with your current active
solution configuration
and active solution platform under Build->Configuration Manager
.
Try by removing project references
and adding them again (path to follow: References ->
(right click) Add reference -> Solution -> Project
). Before giving another try Save All
. This is how I solved it.
This happens when the .suo file for the solution becomes locked and Visual Studio is no longer able to write to it. Another symptom of this problem is that you will see temp suo files being created next to the solution when you open it. Try closing Visual Studio and deleting all *.suo files in your working area. Then reopen Visual Studio and rebuild all. No need to manually rebuild your solution. This will fix the issue when it is caused by a locked .suo, as happened to a colleague of mine today.
In his case, the cause seemed to be that he shutdown his laptop while Visual Studio was still open. Maybe the shutdown of Windows didn't complete cleanly? We can only speculate on how the .suo originally became locked.
I tried all the solutions above and that did not fix the issue for me. I found that it was because of the Active configuration
in the ConfigurationManager
was set to build only the Main (start up) project.
Go to Build
> ConfigurationManager
Ensure that all the projects you want to build are checked as in the screenshot below This is a similar issue on Asp.Net forum here and this is the details on MSDN . Although it was weired, bcoz I never changed these settings and it was working properly last week
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With