VS 2005 vs. VB6

  • Thread starter Thread starter Rob R. Ainscough
  • Start date Start date
R

Rob R. Ainscough

I've been coding .NET for over a couple of years now and I must admit that
VB6 debugging is still a much better experience (with the exception of not
being able to view a recordset) where it has real "edit and continue"
features and one can see the real output to a windows form.

However, the VS 2005 IDE does provide more benefits - code snippets,
comments, rename, find all references, far better intellisense, smart
blocking, section compression. My only suggestion for VS 2007 -- get rid of
the Design/source concept used for web page development. VS should be
feature rich enough that design/source is not needed. Not to mention VS
2005 does a really bad hack job when looking at the source -- they should
"hide" this from the developer in the IDE and all should be done via code
behind and/or form design. All the other "details" really just get in the
way -- I realize this exists because .NET framework just isn't there yet it
terms of being able to do everything (meaning we still have to resort
JavaScript or 3rd party to get some tasks done).

I hope Microsoft move away from the Design, source, code behind and provide
enough functionality so we can just do design & code behind -- which would
truely remove the transition of Windows Form development to Web Page
application development. The less I have to know about HTML, the better --
lets focus on the bigger issues. From a business owners perspective, the
less the developer has to learn on redundant feature sets, the more they can
produce to the end user. Fortunately most of my future apps are going to be
"smart clients" (I hate using that buzz word) -- aka click once -- so web
development is going to be minimal.

Rob.
 
Rob R. Ainscough said:
I've been coding .NET for over a couple of years now and I must admit that
VB6 debugging is still a much better experience (with the exception of not
being able to view a recordset) where it has real "edit and continue"
features and one can see the real output to a windows form.

However, the VS 2005 IDE does provide more benefits - code snippets,
comments, rename, find all references, far better intellisense, smart
blocking, section compression.
Click to expand...

I'm not sure what compression you're talking about... unless it's that
"Treeview like" expand/collapse mess <g> (irk) VB5/6 has "Single Procedure
View" so you can look at only one procedure (which is all I ever want to
see/concentrate on anyway) but the rest of the your list is available in
CodeSMART 2005 for VB6 (www.axtools.com).
 
OK, and why are you posting this to the newsgroups? You have posted a nice
blog article, but why blog on newsgroups?
 
Lebesque,

Before there were blogs the mainpurpose from newsgroups was as Rob did.
Sharing information.

Do you mean that because that there are now blogs the newsgroup purpose is
changed.

Something because that there are plans, you cannot go by car anymore.

Cor
 
Cor,

I've not been on newsgroups longer than blogs exist and I did not know this
former main purpose, so I apologize for being impertinent. Anyway, the post
seemed to me just like another troll-invocation, just like the one about the
king's men and horses, you surely know which one.
 
Lebesque,
Anyway, the post seemed to me just like another troll-invocation, just
like the one about the king's men and horses, you surely know which one.
Click to expand...
That it is not in my opinion, it is a quiet positive message about VB.Net
with things the OP likes and he does not like and trys to give some wishes
to Microsoft. But in general in the way I have read it very positive meant.

Maybe should I have added this link.

http://lab.msdn.microsoft.com/productfeedback/Default.aspx

It can be that I did not because I don't agree completely the part about the
designers. However that should not be a reason for not given a link.
However, thinking about it, that is a little bit childnes.

Cor
 
Back
Top