Skip to content

Conversation

nevemlaci
Copy link
Contributor

No description provided.

:::
Visual Studio does not have a "C Project" option. You should use a C++ project, even for C.

To use C in Visual Studio:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is an unnecessary step and extra information. You do not have to do this for C. Naming a file with a .c extension is sufficient for VS to treat it as a C file instead of a C++ file.

The way I see it, there are two valid choices here:

  1. Merge the "Getting Started with C++" and "Getting Started with C" sections into a single section, with a note to make it *.cpp or *.c depending on what language you're using.
  2. Copy the CPP section word for word, making any C specific changes.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh I actually didn't know that, my bad. It has been some time since I used MSVC from VS for C, and I need this if I'm not in MSBuild.

@nickclark2016
Copy link
Collaborator

Please keep lines under 120 characters. I'll be updating the contributing docs shortly.

@jeremy-rifkin
Copy link
Member

My apologies, I introduced a conflict with #30

@nevemlaci nevemlaci closed this by deleting the head repository Apr 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants