| Author |
 Topic  |
|
|
ivan
Ketchup Master
Russia
75 Posts |
 Posted - Oct 11 2004 : 7:59:37 PM
|
Okay you may stop laughing now. ;)
I've been working with VSNET 2003 for more than a year now (switched from VS6, skipping v2002) and still haven't figured it out. In VS6 you press F7 to build the current project. In VS7.1 pressing F7 builds the solution. Having solutions with 10+ projects in them I find it... inconvenitnt to wait for the IDE to check the state of all of the projects and tell me they're up-to-date before building the one that needs to be built.
I tried to find the command that would do what I need. I failed miserably. The command I found was Build.BuildOnlyProject, and it was the only one with the name resembling the desired effect. I set F7 to be the shortcut to this command. After that, pressing F7 did nothing.
I gave up and from that moment on (it was long long ago) I right-click on the project name in solution explorer and choose 'build'. It is annoying.
Still refusing to believe that I can't build the current project by using a shortcut assigned to some command I thought I'd ask here... hope it's a stupid question ;) |
|
|
Stephen
Tomato Guru
United Kingdom
781 Posts |
Posted - Oct 12 2004 : 04:41:25 AM
|
It's surely quicker to click on the icon in the Build (or _Larry0) toolbar, than to right-click in the Solution Explorer.
I realise that doesn't answer your main question. |
Stephen Turner
ClickTracks http://www.clicktracks.com/
Winner: ClickZ's Best Web Analytics Tool 2003 & 2004
|
 |
|
|
Valyk
Senior Member
Canada
26 Posts |
Posted - Oct 12 2004 : 09:38:12 AM
|
Here is the solution I found.
Using the "Configuration Manager", I exclude every projects from the build excepy the main one. This way, when pressing F7 the only project that is built is the main one.
Since secondary projects rarely changes I still can build them by right-clicking on them.
It is a good idea to keep a separate solution with all the projects included in the build when you want to rebuild the complete solution. |
|
|
|
Omar
Starting Member
1 Posts |
Posted - Aug 10 2005 : 09:12:56 AM
|
The solution is using the "Build.BuildSelection" command. I had the same problem as you, having first tried "Build.BuildOnlyProject".
IHMO, their commands are incorrectly named. |
|
|
|
Old as dirt
Tomato Guru
USA
244 Posts |
Posted - Aug 10 2005 : 1:49:42 PM
|
| Is there anything in VSNET that is better than VS6? |
Ken |
|
|
|
feline
Moderator
United Kingdom
12804 Posts |
Posted - Aug 10 2005 : 2:45:09 PM
|
oh but it must be better, every one else at work said it was a great improvement over VC6. although come to think of it the only thing they could ever point to as an example of this was it had tabs *rolls eyes*
you can use CTRL-W to select the current word in VS2003 and CTRL-ENTER inserts a line above where i currently am. neither key works by default in VC6, but i have never tried to map them either. i like these keys, but this is not a massive improvement. i never used VC6 enough to give a proper comparison. |
zen is the art of being at one with the two'ness |
|
|
|
WannabeeDeveloper
Tomato Guru
Germany
775 Posts |
Posted - Aug 10 2005 : 4:06:44 PM
|
quote:
Originally posted by Not yet as old as dirt
Is there anything in VSNET that is better than VS6?
XP-Style (most of it)  |
 |
|
|
|
jpizzi
Tomato Guru
USA
642 Posts |
Posted - Aug 11 2005 : 01:20:15 AM
|
quote:
Is there anything in VSNET that is better than VS6?
MUCH better Standard C++ compliance.
|
Joe Pizzi |
|
|
| |
Topic |
|
Topic Locked
