C in VS 2008

could u pls give me the steps to start a new C project and how to compile it?

ayha

Please read the following how to:

http://msdn.microsoft.com/en-us/library/bb384838.aspx

yes, create win32 console applciation and add the C file to the project.

U can compile code using
/TC -----------------> for C
/TP------------------> for C++

In VS 2008 can you can setup this switches by changing the project properties

Project->Properties->Configuration properties->C++->Advance->Compile AS C Code
Alt+F7

Though evilrix is technically correct, I would advise you to follow the steps specified above by Subrat2009. Relying on file extensions isn't the most practical thing, unless you're just messing around. The steps I have to take are different than those Subrat2009 specified (though very similar), so I will show you an alternative if the above doesn't work for you (I use Visual Studio 2008 Professional Edition; the above looks like the steps for VS2008 C++ Express)

1. Create a new C++ project, or open one that you wish to compile using C (there is no C project type--it's just C++) 
2. Click on "Project" in the menu bar. 
3. Click the item labeled "(NameOfYourProjectHere) Properties...     Alt+F7", which is usually at the very bottom of the list. 
4. In the dialog window that appears, expand the tree node on the left labeled "Configuration Properties" 
5. In the newly expanded nodes, expand the one labeled "C/C++" 
6. In the newly expanded nodes (that resulted from selecting "C/C++"), click the node labelled "Advanced" 
7. A grid of properties should appear in the right side of the dialog window. Set the one that says "Compile As" to the value "Compile As C Code (/TC)" 
8. Click the dialog windows "OK" button. 

That should do it. Hope that helps,

Nate

>> Relying on file extensions isn't the most practical thing, unless you're just messing around.
It's not about practical (or messing around!)... it's about what's correct. I'd also say that having to modify compiler settings necessarily (and it is unnecessary) is more messing around than just adopting the correct naming convention!

C++ code should always stored in .cpp files and C code in .c files and all compilers (that I've used and that's quite a few), unless told otherwise, will treat them in this way and use the correct language semantics. Sure, you can force compile C++ source as C and C source as C++ using switches but you would normally only do that if you are trying to integrate existing code (and the question leads me to believe this is not the case) and need to compile it with different language semantics.

If you are writing new code you should be naming your source code files correctly and the compiler will do the right thing.

evilrix: I completely disagree. You, as an experienced C++ programmer, should know that being as explicit as possible is always the best. When you program, you want your code to portray not only meaning, but intent. This is just one more step to take that shows intent, a rather under-rated commodity in the programming world. However, you do make a valid point with the file extensions--C source code should reside in .h, .c or .cc files, while C++ code should reside in .h and .cpp files (I tend to use .hpp for C++ header files, though this is not as common as I hope it will soon become. However, this fact is just one more arugment for my case, that the line between these two languages is not distinct enough to rely on file extensions).

Author: I strongly advise you to tell the compiler you want your code to be treated as C, rather than hoping that it "just will" (what if this behaviour changes in a later release, as the C language plummets faster and faster to death?)

> C++ code should always stored in .cpp files and C code in .c (or .cc) files

C++ extensions are .cxx, .cpp, .cc and .C
C extension is only .c

hi,

I created a new C++ console application (empty project) and changed cpp ext. to c. then Project->Properties->Configuration properties->C++->Advance->Compile AS C Code
and I can compile the C code.

ayha

Glad we could help :)

- Nate