| Groups | Blog | Home |
visual studio .net general : QUERY: C++ programming
When you make a new project, you will get a dialog "Win32 Application Wizard - <project name>" On this, you must select the Application Settings tab (which by the dark blue coloring is not obviously a selectable tab!!), and there check the Empty Project box. Then, when you add your file, it will be the only source file and its main( ) will be seen as the start point. Val -- ~~~~~~~~~~~~ "We've secretly switched the dilithium crystals with new Folger's Crystals... let's watch what happens." ~~~~~~~~~~~~ [quoted text, click to view] "KevinGPO" <kevingpo@hotmail.com> wrote in message This is about programming C++ using Visual Studio.NET 2002 & 2003.news:unQmAiCNGHA.1180@TK2MSFTNGP09.phx.gbl... I created a new Visual C++ project, Win32, Console application. What's this? _tmain(int argc, _TCHAR* argv[]) I had a self-contained C++ file that I added to the project along side the ready-made _tmain() file. I tried to build the project but it kept on saying reached eof, or couldn't find <iostream>. It probably was because VS didn't like the alien carriage-returns. Anyway, is there anything I need to know if I want to program like old-style unmanaged C++? Besides the weird name _tmain() and _TCHAR, is there any other nasty surprises I need to watch out for? PS: What is the difference between vsnet and vstudio newsgroups?
On Sat, 18 Feb 2006 01:13:08 -0000, "KevinGPO" <kevingpo@hotmail.com>
[quoted text, click to view] wrote: >This is about programming C++ using Visual Studio.NET 2002 & 2003. > >I created a new Visual C++ project, Win32, Console application. > >What's this? > >_tmain(int argc, _TCHAR* argv[]) That's Unicode. You don't use chars anymore on the Windows platform, you use those _t/_T macros that map to either char (8 bit, ASCII/ANSI) or wchar_t (16 bit, Unicode UCS-2/UTF-16) depending on whether you define... umm... some appropriate constant (sorry, it's been some time since I used C++). Go hunt through the standard headers and search for _TCHAR and _tmain in the MSDN library. I'm afraid you've got a lot of reading ahead of you. All C++ library functions that operate on strings or characters have _t equivalents, and you should use only those from now on. That has nothing to do with .NET or managed code, by the way. That's plain old unmanaged (Win32 native) handling of Unicode. When you're writing managed code there's only System.Char and System.String, both of which are always Unicode (16 bit, UTF-16). --
This is about programming C++ using Visual Studio.NET 2002 & 2003.
I created a new Visual C++ project, Win32, Console application. What's this? _tmain(int argc, _TCHAR* argv[]) I had a self-contained C++ file that I added to the project along side the ready-made _tmain() file. I tried to build the project but it kept on saying reached eof, or couldn't find <iostream>. It probably was because VS didn't like the alien carriage-returns. Anyway, is there anything I need to know if I want to program like old-style unmanaged C++? Besides the weird name _tmain() and _TCHAR, is there any other nasty surprises I need to watch out for? PS: What is the difference between vsnet and vstudio newsgroups?
[quoted text, click to view]
KevinGPO wrote: > This is about programming C++ using Visual Studio.NET 2002 & 2003. > > I created a new Visual C++ project, Win32, Console application. > > What's this? > > _tmain(int argc, _TCHAR* argv[]) > > I had a self-contained C++ file that I added to the project along side the > ready-made _tmain() file. I tried to build the project but it kept on saying > reached eof, or couldn't find <iostream>. It probably was because VS didn't > like the alien carriage-returns. > > Anyway, is there anything I need to know if I want to program like old-style > unmanaged C++? Besides the weird name _tmain() and _TCHAR, is there any > other nasty surprises I need to watch out for? > > > > > PS: What is the difference between vsnet and vstudio newsgroups? > > In addition to Val's good advice, if you have files with non-Windows line endings, you can fix them by using File->Advanced Save Options (this is in VS2003).
Hi guys
Am still getting compile errors. I have a C++ cpp source file (just one, with a class and a standard main function). It does however take in #include <iostream.h> and I have tried the CXX 3rd edition version #include <ciostream> or #include <iostream>. But the error message is always the same. "fatal error C1010: unexpected end of file while looking for precompiled header directive" The line that it points to is right at the end of file. Probably it has something to do with carriage-returns or something. The file was created in Windows 2000/XP wordpad/notepad. I created a new Visual C++ Project, Win32 console. It did supply me with a stdafx.cpp and _main() function file, but I replaced this with my own cpp source file. My cpp source file compiles fine with Visual C++ 6.0. But why doesn't it compile under Visual Studio.NET 2003? Please someone help! Kev [quoted text, click to view] "David Wilkinson" <no-reply@effisols.com> wrote in message news:%23G7hBcINGHA.3896@TK2MSFTNGP15.phx.gbl... > KevinGPO wrote: > >> This is about programming C++ using Visual Studio.NET 2002 & 2003. >> >> I created a new Visual C++ project, Win32, Console application. >> >> What's this? >> >> _tmain(int argc, _TCHAR* argv[]) >> >> I had a self-contained C++ file that I added to the project along side >> the >> ready-made _tmain() file. I tried to build the project but it kept on >> saying >> reached eof, or couldn't find <iostream>. It probably was because VS >> didn't >> like the alien carriage-returns. >> >> Anyway, is there anything I need to know if I want to program like >> old-style >> unmanaged C++? Besides the weird name _tmain() and _TCHAR, is there any >> other nasty surprises I need to watch out for? >> >> >> >> >> PS: What is the difference between vsnet and vstudio newsgroups? >> >> > > In addition to Val's good advice, if you have files with non-Windows line > endings, you can fix them by using File->Advanced Save Options (this is in > VS2003). > > David Wilkinson
Hi,
That error is usually related to your stdafx and associated includes being messed up. You may wish to create a new console app with the wizard and then just follow it's structure... [quoted text, click to view] KevinGPO wrote: > Hi guys > > Am still getting compile errors. > > I have a C++ cpp source file (just one, with a class and a standard main > function). It does however take in #include <iostream.h> and I have tried > the CXX 3rd edition version #include <ciostream> or #include <iostream>. But > the error message is always the same. > > "fatal error C1010: unexpected end of file while looking for precompiled > header directive" > > The line that it points to is right at the end of file. Probably it has > something to do with carriage-returns or something. The file was created in > Windows 2000/XP wordpad/notepad. I created a new Visual C++ Project, Win32 > console. It did supply me with a stdafx.cpp and _main() function file, but I > replaced this with my own cpp source file. > > My cpp source file compiles fine with Visual C++ 6.0. But why doesn't it > compile under Visual Studio.NET 2003? > > Please someone help! > > Kev > "David Wilkinson" <no-reply@effisols.com> wrote in message > news:%23G7hBcINGHA.3896@TK2MSFTNGP15.phx.gbl... >> KevinGPO wrote: >> >>> This is about programming C++ using Visual Studio.NET 2002 & 2003. >>> >>> I created a new Visual C++ project, Win32, Console application. >>> >>> What's this? >>> >>> _tmain(int argc, _TCHAR* argv[]) >>> >>> I had a self-contained C++ file that I added to the project along side >>> the >>> ready-made _tmain() file. I tried to build the project but it kept on >>> saying >>> reached eof, or couldn't find <iostream>. It probably was because VS >>> didn't >>> like the alien carriage-returns. >>> >>> Anyway, is there anything I need to know if I want to program like >>> old-style >>> unmanaged C++? Besides the weird name _tmain() and _TCHAR, is there any >>> other nasty surprises I need to watch out for? >>> >>> >>> >>> >>> PS: What is the difference between vsnet and vstudio newsgroups? >>> >>> >> In addition to Val's good advice, if you have files with non-Windows line >> endings, you can fix them by using File->Advanced Save Options (this is in >> VS2003). >> >> David Wilkinson > > --
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
| home · blog · groups | Questions? Comments? Contact the dn |