Migrating from VC++ v6 to v7.1

[Owen]

With Visual C++ v6, I was able to open a .cpp file into the IDE, type F7, and
have an executable. With .NET 2003, that is no longer the case. Is there a
quick and dirty way in .NET to perform like its predecessor?

[Domenic Albano]

F5 to build and run,
or Ctrl+Shift+B to only build.

That is provided of course that you have the default C++ keyboard mappings.

Domenic

"Owen" <fu**@highwaay.net> wrote in message
news:10*************@corp.supernews.com...

With Visual C++ v6, I was able to open a .cpp file into the IDE, type F7, and have an executable. With .NET 2003, that is no longer the case. Is there a quick and dirty way in .NET to perform like its predecessor?

[Ronald Laeremans [MSFT]]

No sorry, we lost the ability to auto create a project wrapper around a .cpp
file. It was one of the fatalities of going to the joint IDE.

Ronald Laeremans
Visual C++ team

"Owen" <fu**@highwaay.net> wrote in message
news:10*************@corp.supernews.com...

With Visual C++ v6, I was able to open a .cpp file into the IDE, type F7,
and have an executable. With .NET 2003, that is no longer the case. Is
there a quick and dirty way in .NET to perform like its predecessor?

[Owen]

If only that worked. I even set the environment to the default C++ keyboard
mappings. Nothing.

In v6, pressing F7 would automatically create a workspace and add my files to
the project automatically. In v7.1, I must jump through the following hoops
before I can compile the code:
1. Select File -> Add Project -> New Project
2. Select Visual C++ Projects -> .NET -> Empty Project (.NET)
3. Enter the path to the files
4. Select OK
5. Select Project -> Add Existing Item
6. Add all the files into the project

Surely the behavior of v6's IDE has been preserved. Anyone?
Domenic Albano wrote:

F5 to build and run,
or Ctrl+Shift+B to only build.

That is provided of course that you have the default C++ keyboard mappings.

Domenic

"Owen" <fu**@highwaay.net> wrote in message
news:10*************@corp.supernews.com...

With Visual C++ v6, I was able to open a .cpp file into the IDE, type F7,

and

have an executable. With .NET 2003, that is no longer the case. Is there

a

quick and dirty way in .NET to perform like its predecessor?

[Owen]

Understandable. The pros of the integrated IDE outweigh the cons. You all have
done a great job.
Ronald Laeremans [MSFT] wrote:

No sorry, we lost the ability to auto create a project wrapper around a .cpp
file. It was one of the fatalities of going to the joint IDE.

Ronald Laeremans
Visual C++ team

"Owen" <fu**@highwaay.net> wrote in message
news:10*************@corp.supernews.com...

With Visual C++ v6, I was able to open a .cpp file into the IDE, type F7,
and have an executable. With .NET 2003, that is no longer the case. Is
there a quick and dirty way in .NET to perform like its predecessor?

[Peter van der Goes]

"Owen" <fu**@highwaay.net> wrote in message
news:10*************@corp.supernews.com...

With Visual C++ v6, I was able to open a .cpp file into the IDE, type F7, and have an executable. With .NET 2003, that is no longer the case. Is there a quick and dirty way in .NET to perform like its predecessor?

Gone, as Robert told you.
The closest workaround I've found for classroom use is to create a default
console project (I call mine CrashTestDummy), then use Project->Add Existing
Item to bring a new source code file(s) into the project. You have to
right-click the old source code file in solution explorer, then select
Remove to remove the old code before rebuilding.
Not nearly as slick as having a default project built around you source
code, but better than creating a new solution each time.

--
Peter [MVP Visual Developer]
Jack of all trades, master of none.