VS 2022 is not C friendly
-
jmaida wrote:
I will calmly say VS is not a user/programmer friendly application.
I started with hand written scripts. Then I think I went to Borland IDE. Then the first Microsoft IDE (not called VS) Finally then I go to make files, then maven, then back to VS and then back to make/maven, then back to VS (going back and forth several times.) Eclipse is in there some where but I gave up on that right away (twice actually.) And at least one custom built build system in there as well. None of them were user friendly. Might note of course that I have written many applications also and the universal truth is that power and simplicity are not possible in the same application. The command line tools cat/type are pretty dang easy to use. The editor that I have been using for 20 years (not part of an IDE) still manages to make me jump through hoops every time I have to install it on new box just to get it to work the way I want.
jmaida wrote:
But I will solve this problem.
Having fought with VS many times, all I can say is that there is a way to solve the problem you described.
All that you have said, is very familiar to me, Eclipse, VS, Borland, Codeblocks, Geany (weird little editor/app) and of course Linux stuff with it's own IDE baggage (I have forgotten must of it and it's weird vi editor) For windows environments, I settled on Codeblocks because it stayed relatively the same as far as the interfacing, program settings, etc. Their editor is quite good, one of the best, I think. They add some new plugins now and then, but not too pushy. But if someones puts it down, I let go as not their cup of tea. We all have our fancies. I did business with a German company years ago and their programmers and I had no problems working together other some German/English language issues, but we all had similar likes and dislikes. Thanks for encouragement. VS can be frustratingly fluid.
"A little time, a little trouble, your better day" Badfinger
-
Here is a suggestion. Stop ranting about something you are having problems with. Go to https://www.codeproject.com/Questions/ask.aspx[^] and post the full details, so people can try to help you. And make sure you check what you post, so you can fix any typos, and ensure that all code snippets are surrounded by the appropriate <pre> tags so it is readable, like:
#include "somefile.h"
int main()
{
printf("Hello, World!");return 0;}
Tags used in the above case are: <pre lang="C++"> and </pre>
Thanks Richard, When I can compile more specific details I will do so. I have some weird problem where VS compiles the same simple C file (single file) with two different results. It's a test file from vendor's web site that uses their libraries. Very good suggestion. A helpful one that I should have used right off. I have even suggested in the past to others. Oh well.
"A little time, a little trouble, your better day" Badfinger
-
'Xactly. Me too. Kids these days expect everything to be handed to them. I also learned on OpenVMS, which has a debugger, but it's practically unusable.
unusable? I'm offended. :) Last week I was debugging some ancient FORTRAN, and it did just fine. Seriously though, it takes a while for the muscle memory to kick in to remember the keypad commands.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
-
I will. Thank you. I blame VS because 1. Have 2 copies of exactly the same C file. 2. Put them into VS "exactly" the same way (here is where the rub is, because VS makes that more complicated than it should be as "exactly" is not what has happened) 3. one works fine, the other does not. 4. Did a difference on .project files. Not "exactly" the same. That is what I am trying to resolve. If it is user error then shame on VS for making it easy to do.
"A little time, a little trouble, your better day" Badfinger
-
unusable? I'm offended. :) Last week I was debugging some ancient FORTRAN, and it did just fine. Seriously though, it takes a while for the muscle memory to kick in to remember the keypad commands.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
You are obviously hoopier frood than I. The main issue I had was that I couldn't get the debugger to display the source lines involves. (DEC C) "User error" I'm sure.
-
Thanks Richard, When I can compile more specific details I will do so. I have some weird problem where VS compiles the same simple C file (single file) with two different results. It's a test file from vendor's web site that uses their libraries. Very good suggestion. A helpful one that I should have used right off. I have even suggested in the past to others. Oh well.
"A little time, a little trouble, your better day" Badfinger
-
jmaida wrote:
VS compiles the same simple C file
No it doesn't. You need to understand the difference between Visual Studio (an Integrated Development Environment) and the C language compiler and the object linker.
-
jmaida wrote:
VS compiles the same simple C file
No it doesn't. You need to understand the difference between Visual Studio (an Integrated Development Environment) and the C language compiler and the object linker.
I think I have figured it out. Something to do with project properties and whether one has code selected or project selected. They look very similar expect one has linker options. The "additional includes" are showing blank in project properties even though I have set them in project properties when code file is selected. Very confusing. It was the includes that giving me different results between the two C file projects. These additional includes do not always resolve the include in code. Plus a user error in the path, but I corrected them only have them come back later.
"A little time, a little trouble, your better day" Badfinger
-
You are obviously hoopier frood than I. The main issue I had was that I couldn't get the debugger to display the source lines involves. (DEC C) "User error" I'm sure.
when you start moving source files to different places, sometimes the debugger cannot find what it needs - usually "set source " takes care of the problem. Not that it will come up again... :)
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.