|
We have a book club in our local branch library. It is so old that most of the original participants have dropped off the twig, or turned over a new leaf.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
You need to get with the digital times.
It now called a kindle club. Which is just a matchstick
A Fine is a Tax for doing something wrong
A Tax is a Fine for doing something good.
|
|
|
|
|
I had problems with my PC at work and I got it reinstalled by the IT.
I then reinstalled Visual Studio 2017, getting the newest version available v15.9.24
They have changed the way they work with precompiled files. You can't create MFC C++ console projects anymore. The "new project" wizard is different too (MFC full app still working though, but in the new way)
At least you can still open old projects created previously, at home with the Visual Studio 2019 Community Edition it doesn't work anymore.
I have already found several places speaking about the problem but so far 3 of the supposed solutions tried (installing v141 packages, changing the project options and manual addition of the missing files + references) and still not working .
I will continue investigating / trying things.
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Or ... switch to C# ...
Come to the Dark Side - we have cookies.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
OriginalGriff wrote: Or ... switch to C# ...
I hope you meant DotNet Core 3.x C#.
OriginalGriff wrote: Come to the Dark Side - we have cookies.
Come to the darker side...we have chocolate fudge! DotNet Core! DotNet Core!!!
|
|
|
|
|
OriginalGriff wrote: Come to the Dark Millenial Side - we have cookies vegan soy stuff.
Let an old wraith fix that for you.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
CodeWraith wrote: Come to the Dark Millenial Original Side - we have cookies vegan soy stuff BACON.
FTFY!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
You are the oldest Millenial I have ever heard of.
Anyway, you are what you eat and a real Millenial is at least 50% soy, while that would make us two...
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
I am proud to say I am approximately 0% soy ...
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
What's soy?
Carnivore to the bone!
Phil
|
|
|
|
|
|
I didn't claw my way to the top of the food chain to be a vegetarian.
Pass the bacon. I'll finish it off.
|
|
|
|
|
I like it difficult...
I want to make that C++ (with MFC if possible) and C# work together in .Net Core.
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
we're still in the dark ages, using MFC/C++ with Visual Studio 2019 (16.4.5) and not having particular issues.
i can create c++ console app and MFC app.
I'd rather be phishing!
|
|
|
|
|
Really? I have Visual Studio 2019 16.6.4 Community Edition here at home and I can't create a console c++ app with MFC and before I could.
EDIT:
Now I can create it with the new precompiled headers, thanks to the tip by David Crow in the message below.
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
modified 28-Jul-20 16:51pm.
|
|
|
|
|
No, Mickeysoft knows better than you what you need and what you don`t need. Or when you are going to need it and when you have to update to new and shiny, with butt ugly and monochrome obviously being Mickeysoft`s new shiny.
I have always said that my current installation of Win 7 would be my last. Well, my PC died with a bang yesterday, so I guess it`s time to move on.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
modified 28-Jul-20 12:28pm.
|
|
|
|
|
Nelek wrote: You can't create MFC C++ console projects anymore. What happens if you opt for Windows Desktop and then Windows Desktop Wizard?
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles
|
|
|
|
|
Wohooo....
That's it
partially
It makes the new console APP with the new precompiled headers
#include "pch.h"
#include "framework.h"
But if I open an old project (working on them last month in Visual Studio 2017) with the previous
#include "stdafx.h"
then... no way.
At least the Visual Studio 2017 professional at work still can use it.
There must be a way without having to "copy + paste" the whole old project in a new "pch.h" structure, only have to find it.
But at least now I can continue doing my tests at home if I start a new project. Thanks for the tip.
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Thanks for the warnings! I am still in the C++ and MFC world although we are slowly moving away from MFC. We will not be moving from C++ though.
Anyway, I haven't created a new project in many years. I had nothing but problems the last times I did so I just stopped trying. Now I have a few sample projects I always copy and adjust. Mostly because I have them set up with all the targets for 32/64-bit mode, MBCS/Unicode, Static/Dynamic RTLs, and Debug/Release builds - all 16 combinations of those options. I have never figured how to do that in the IDE so I just don't bother. I find it easier to copy, rename, and edit than to it is deal with that stuff in the IDE. They still have some things broken when I try to sort out debug file output options. There again, I don't bother - hand editing saves the day. It is cumbersome but at least it works. That's what annoys me the most : I try to do stuff in the IDE and it breaks things in the project file. Eventually, I figured how to do them by hand and I stopped wasting my time in the IDE on that kind of thing.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
Rick York wrote: I find it easier to copy, rename, and edit than to it is deal with that stuff in the IDE. They still have some things broken when I try to sort out debug file output options. There again, I don't bother - hand editing saves the day. That was going to be my next move.
But... do you use the latest Visual Studio 2017 or 2019? Because I I can't even compile a previously valid project (which at work with 2017 still compiles fine)
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
That is odd. I use both VS2017 and VS2019. I never share project files between them. Each version has its own project files and I always keep them in separate subdirectories named VS2017 and VS2019 which are at the same level as the Source. I recently migrated over to VS2017, about a month ago, and I always copied the 17 files to the 19 directory and loaded them up, adjusted the SDK level, and everything worked.
I have not tried to share a project between versions because it never occurred to me that it could possibly work.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
Well... at work I only have the 2017 and we want to do tests with .Net core so I had to install 2019 at home.
Rick York wrote: I recently migrated over to VS2017, about a month ago, and I always copied the 17 files to the 19 directory and loaded them up, adjusted the SDK level, and everything worked.
Somewhen in the future we will have to port the BIG project to .Net core, and (AFAIK it is not expected that VS2017 will work with .Net Core) we will have to open all solutions in 2019 to compile them within the correct framework and with the target sdk.
So I started now with just open and see what happens. And it "works" as expected... wrong
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Sorry to read you have to move to .Net. You have my condolences.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
Rick York wrote: Sorry to read you have to move to .Net. You have my condolences. Very kind of you
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
I never left MFC because I refused to, back then, to use interpreter, garbage-collecting Java or its knock-off, interpreter C#. I use the latest C++17/20 community compiler, VS2019, and for free. The IDE serves me well too and I can configure it to compile today on any platform and machine setup I want. Every few years I have to re-seat my programs, though, since their MFC under-pinnings do change over time, the pch.h being one of them. From my perspective, Microsoft's most brilliant move was to humbly throw C# onto the Github code dump, hire Herb Sutter, the C++ ISO committee chair, and change all its docs to C++ examples. The code I daily write with modern C++ in modern MFC connecting to ultra-modern MFC GUI libraries like BCGSoft's BCGControlBar GUI library, is becoming more and more ODR compliant and maintainable, and even elegant. Doggedly hanging onto past versions of past versions of your programs (not to mention OSes), as well as past IDE versions are, IMO, not taking advantage of the 1000s of paid developers improving them. And as for C++, I am eagerly waiting for C++20 with Modules and C++23's Networking so I revamp my many MFC projects and evolve away from problematic dllimport/dllexports and Winsock2 (C++23 Networking will look very much like Winsock2 is my guess). Will it take time to re-do my projects? Yes. But this is where technical-debt comes from: taking the easy way out until everything breaks. Herb Sutter said in one of his posts that there were ~200 papers addressing/modifying/correcting C++ features last year, up from ~125 the year before. There is no comparison in long-term robustness of a language supported by the world's voting body (ISO) to a company who is only beholden to its shareholders (think: Microsoft's C#). Of course, if you are writing programs that don't need to survive the test of time, then I guess interpreters will do. I don't have that option. 40 years ago, Bjarne Strustrup invented C with classes and transformed programming with his principles. 29 years ago, Microsoft went all in on C++ and produced MFC. In the past few years, Microsoft has elevated MFC back on top. Go Microsoft. Excellent use of your trillions of dollars. Now, back to my MFC programming, but I thought it was worth the time to describe the other side of views on MFC. Avoid updating VS is silly advice.
|
|
|
|