|
|
It does take some getting used to, especially after using VS6 for the best part of 5 years! I loathe the new "sliding" toolbars and the help system sucks IMHO. Overall, it is slower to use and way more cluttered. There are some benefits - I find the IntelliSense system better than VS6 and when working on ATL/WTL projects (which is nearly all the time) I finally have some ClassWizard functionality (i.e. I can easily add Windows message handlers/WM_COMMAND handlers, etc.). And, being an ATL user, I find ATL7 indispensable!
On the whole, I would be more than happy to continue using VS6 if it had support for ATL7 plus a WTL ClassWizard!
When I am king, you will be first against the wall.
|
|
|
|
|
I have to agree that the .Net IDE can't please everyone, but I can't fault Microsoft for trying! With so many options and ways to tweak it, they couldn't test everything (let alone work out "typical values" for everyone's taste) and there are very few features that are half-baked (I think you got them all). I do get the same problem with the annoying selection jumpy bit in Media Player sometimes. Personally, I love the way you can tweak the .Net IDE to just the way you want it, and that you can view help files and write code in lovely full screen. My two major faults with .Net would be that it eats RAM like popcorn, and the HTML editor is pathetic (try editing a large HTML file and you'll see what I mean: it takes aeons to load the treeview).
Bender rocks!
modified 15-Jun-21 21:01pm.
|
|
|
|
|
Tom Welch wrote:
How many people are happy with the VS.NET IDE?
I am most happy whenever I see the very usefull message:
Project files cannot be dropped onto Visual Studio. They must be opened via the File menu.
<center> </center>
|
|
|
|
|
Yes, that definitely had to be one of MS' BIGgest blunders with the new IDE. Ive never heard of any good program which couldnt accept its own filetypes via drag-n-drop. BUT then again, as said before MS does like to innovate!
All in all i like the IDE, though i do miss an immediate window which actually was IMMEDIATE, and not "Wait until you run then program THEN i'll be immediate".
|
|
|
|
|
This makes total sense to me. It is obvious that :
- Microsoft is not eating enough their own dog food
- The OS and Office products are not built using this IDE
I personally find myself totally stuck. Example ? the Find in files feature. The poor guy who did that should never be allowed to touch a keyboard again.
|
|
|
|
|
Microsoft eats their own dog food--in fact they use the beta version of their dog food. While contracting at Microsoft in both the Natural Language Group and the Windows group, I am using the next version of the .NET frameworks, version 2.0 due out a year or more from now.
It is very unstable, but I can't use anything earlier because that is what Windows is shipping with.
It is true though that the VS IDE is mainly being used for debugging, since Microsoft still uses a command-line process for most of their applications and OS.
Well, first you can't debug an OS with VS.NET, you need the kernel debugger because VS.NET works within the OS.
Wes
|
|
|
|
|
I haven't really started to use it full time, but I would say that you both gain and loose, as is the case mostly when MS brings out a new version of a product.
On the down side, I see that I loose more screen real estate, with the appearance of more headings and toolbars on each window. There is no problem with adding new toolbars, just give the ability to switch them off.
Also, I see that all the trendy tranparent controls and menus make the UI slower and less responsive.
On the positive side, I see they finally decided to put in a find and replace... about time too!
|
|
|
|
|
We only use informal internal testing, but our software is used internally only, so this is appropriate. We just develop the UI and show it to someone internally that will use the software. We don't tell them anything about the program and ask them to use it. If they can figure it out without asking any questions then it passes muster. From there, we tweak it for useability and fewer user required actions.
|
|
|
|
|
As I see not too many people have proper way of software testing.
May be it is why we can see "GPFs" too ofthen in releases 
|
|
|
|
|
However, usability testing != software testing.
How does usuability usability have anything to do with well-written, bug-free code?
My 2p...
"Those that say a task is impossible shouldn't interrupt the ones who are doing it." - Chinese Proverb
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
