clone old hard driver to SSD
Friday, January 31, 2020
.suo issue in Visual Studio 2017 -- tips in compiling MFC project
tips in compiling MFC project . working on some examples in <Programming MFC ground up > book. first example in the book.
- Quick tip: What to do when Visual Studio freaks out and everything is red
- Close Visual Studio
- Delete the SUO file
- Restart Visual Studio.
- – Deleting suo did not help
- – Restarting VS did not help
- – Unloading and reloading the project solved the issue!
- Visual C++ : Please help me with the following code
- Visual Studio displaying errors even if projects build
- VS 2019 Intellisense reports compile errors when rebuild all does not.
- Fixing Visual Studio Intellisense Errors
- Shut down VS
- Nuke the .vs folder or the .suo file
- Restart VS
- Quick tip: What to do when Visual Studio freaks out and everything is red
Having just installed Xamarin, I first thought that it was the culprit. Or maybe Resharper. Anyway whatever the cause was (and I am still not 100% sure what actually triggered this behavior), recovering from it is actually quite easy:
The SUO file is a hidden file,, which is placed in the same folder as the SLN file. It contains a lot of information such as which files are currently open in the IDE, some local settings, etc. Personally I hate this file because it can cause a lot of trouble if it gets corrupted. And since it is hidden, you don’t always think about it.
So the rule is: If you see some weird behavior in Visual Studio, try to delete the SUO file first, before you try anything else.
Update: I was just told that unloading and reloading the project file might help too. I suspect that under the cover this also modifies the SUO file and solves the issue. Good to know :)
this tip works well: unload project and then reload project.
Adding to the votes:
the answer is: These errors have to do with the fact that your application is using Unicode (wchar_t) strings. The best thing to do is change all your string literals to wide character literals, e.g.
My symptoms in VS2019 were that I would build with some errors. Then I'd fix the errors, and the build would work, as shown in the Output window. But the Errors windows still showed the old errors. I could run it just fine. Closing VS2019 and reopneing fixed the issue, but only for a little while. This started happening on version 16.4.3
This solution seems to work for me:
Uncheck Tools->Option->Projects and Solutions->General->Allow parallel project initialization
Thank you for report this issues. Do these errors go away if you uncheck Tools > Options > Projects and Solutions > General > Allow parallel project initialization, delete the .vs folder, and reload the solution?
Clearing up Intellisense There's usually a simple solution when IntelliSense decides to sleep one off:
The .vs folder holds solution related temp data including the .suo file that caches intellisense and some debug data. That folder also holds Web site configuration data for Web projects and a few other things. It's safe to delete this folder - Visual Studio recreates it when it's missing.
Older versions of Visual Studio (prior to VS 2015) didn't have a separate folder and dumped that same information into files in the solution's root folder.
In these older versions you can fix Intellisense issues by deleting the Solution's .suo file. Deleting the .vs folder in newer version nukes the .suo file which is responsible for cached IntelliSense and also some cached Debug data. When VS acts up and reports whacky errors that seem wrong, the burning down the .suo file is a nice quick thing to try first.
The .suo file contains cached IntelliSense data and once that file is off, no amount of recompilation or clearing the project is going to help. Nuke the .suo file. or in VS 2015 or later the .vs folder and get back to sanity.
memory management research
memory management research. search "memory management" on codeproject.com
- Memory Management and RAII
- Memory Management for Beginners
- CString Management
- C++ Memory Management Innovation: GC Allocator
- Allocated Memory Management in C
- tonious/hash.c
- A Primer of the Windows Architecture
- Windows Memory Management - Part 2
- Memory Allocation Tool
- Unable to find atlapp.h file in Visual Studio 2017
- Exploiting Managed Memory
- Memory Leak Detection
- Windows Memory leak detection (update to existing article)
- Memory and Memory Corruption
- How a weak_ptr Might Prevent Full Memory Cleanup of Managed Object
- C++ Memory Pool
- How to create a Simple Lock Framework for C++ Synchronization
- SmartObject Class (Objective-C like Memory Management) for C++ (A substitute for Smart Pointer maybe?)
- What is Msimg32.dll?
- VS IDE Editor Tip: Quick Macros
- using / namespace
- Guide to Image Composition with Win32 MsImg32.dl
- Guide to WIN32 Paint for Beginners
- Guide to WIN32 Paint for Intermediates
- Guide to Win32 Memory DC
- Guide to WIN32 Regions
- A Guide to WIN32 Clipping Regions
- Walking the callstack
- C++ Memory Leak Finder
- Simple debug log for C++
- Easy Detection of Memory Leaks
- Diagnostic
- Catching Memory Leaks
- Memory Leak Detection in C
- Handle Management - Complete Solution
Thursday, January 30, 2020
add manifest into my application
add manifest into my application
- How to programmatically disable Program Compatibility Assistant in Windows 7 and Vista for a native C++ application?
- Custom installer without warning dialog… (TrustedInstaller.exe)
- Windows – How to block .exe files in vulnerable folders from running with Software Restriction Policies
- How to Change Compatibility Mode Settings for Apps in Windows 10
tips on TotoriseSVN tool
tips on TotoriseSVN tool. neat to update my assembly version automatically.
- Embed SVN’s revision into AssemblyInfo’s version number
- Create, update and merge branches in SVN
- Using SubVersion Revision Numbers in Build Versions
- subversion tutorial.
- Integrating the Subversion Revision into the Version Automatically with Native C/C++
- use svn revision number in application version
- Frequently asked questions
scheme of software protection
some thoughts of software protection. include three components:
search "updater" in codeproject.com.
- software updater. it update software version and check sum into registry item.
- software version enforcer. it will check current running software copy version and check sum. then compare the assembly version and check sum in the current registry. if the comparison match/equal, then let current copy working. otherwise disable current working copy. this software enforcer must be signed with my public key.
- my software product. it is obfuscated copy first. when it starts to run, it needs to check if my software version enforcer installed, then check public key of my company. if it is my company public key, or no software enforcer installed, then stop working and refuse to run.
- Copy Protection for Windows Applications
- Copy Protection for Windows Applications (Part 2)
- Copy Protection for Windows Applications (Part 3
- Copy Protection for Windows Applications (Part 4)
- An efficient way for automatic updating
- Download-Manager-for-Application-Updates
- TU: The Easy Update Library for Your Projects
- SmartClient: .NET Self Updating Applications
- Updating application clients with a Windows Installer: a simple workaround
- CatenaLoigc product
- Updater
- Adding automatic updates to your program - Part 1
- Application Auto Update Revisited
- Automatic Online Update Toolkit
- Purchase the Software Update Wizard
- Simple update check function
- UpdaterApp - a Library for Easy Update
- Maintenance and Updating of Legacy Code
- MS Access (*.mdb) + C#: SELECT, INSERT, DELETE and UPDATE Queries
- Batch Image Resizer
- An Updated Batch Image Resize Tool