best way to learn Windows Forms
jello...@hotmail.com
dont understand how to get my mind around WinForms; they just seem a
lot more complex than VB6.
Thanks
-Charlie
Matt Fielder
used to dealing with classes. The difference appears bigger than it is when
first starting. You have to create an instance of your form first, and then
call the methods on that instance.
Example: if you have a form called HelloWorld.vb --- (note the difference in
extension) you would first create an "instance" of the form by something
such as:
dim f as new HelloWorld
Then to show the form, you would use
f.show
Modality is a bit different also -- try out
f.showdialog
Then other things work more like your used to than you think they might
be -- examples:
f.close
f.hide
etc.
Of course there are many other differences in .Net vs VB6, but if your like
me, after you've worked with it for a while, you'll find the .Net world a
much more orderly and comfortable one.
HTH
<jello...@hotmail.com> wrote in message
news:1165020421.9...@80g2000cwy.googlegroups.com...
RobinS
By working through it, you build an entire application, so it
covers all the basics, from building forms to data access.
Robin S.
-----------------------------
<jello...@hotmail.com> wrote in message
news:1165020421.9...@80g2000cwy.googlegroups.com...
Jello World
I can build console apps like the back of my hand
and declaring forms before instantiating them? isn't that standard vb6
and even vba?
even in Access Dim frm as new Form_Switchboard right?
i just-- the big picture-- a single book or 10 single books isnt going
to do this for me.
Are there good windows form websites?
Best practices, extensibility?
I just don't understand why forms are such a complex beast; under what
situations do you change the source code for the form?
-Charlie
Cor Ligthert [MVP]
There were more programmers already for many years who wrote the same as
you. They started and after a while most were sending messages like: "They
have to pull me back on my hairs to VB6".
You can use this newsgroup to help you. There is always somebody who is
starting like you who likes it to help, while you even can help yourself
others and learn in that way.
Don't be afraid with the answers. If they are wrong there is certainly
somebody in this newsgroup who will help to get them correct.
I hope this gives an idea,
Cor
<jello...@hotmail.com> schreef in bericht
news:1165020421.9...@80g2000cwy.googlegroups.com...
RobinS
question, not a general "tell me about Windows forms". There
is enough information about forms to fill a thousand-page book.
Robin S.
------------------------------------------
"Jello World" <jello...@hotmail.com> wrote in message
news:1165028811.4...@79g2000cws.googlegroups.com...
Michel Posseth [MCP]
mather of buying the right books ( and playing with the at that time beta
versions of VB.Net )
I used the programming microsoft visual basic book from balena , ( wich has
special attention to VB6 proggers ) i never found a really good VB.Net
Winforms Book so in the end i bought a C# book ( wich is a surprising
easy language if you already have understanding of javascript and the .Net
framework )
>and you have to get used to dealing with classes
I also used classes in VB6
regards
Michel posseth [MCP]
"Matt Fielder" <mfielderR...@nospam.nospam> schreef in bericht
news:eECZwdbF...@TK2MSFTNGP06.phx.gbl...
Tom Dacon
Forms Programming in C#" by Chris Sells, Addison-Wesley publishers.
Tom Dacon
Dacon Software Consulting
<jello...@hotmail.com> wrote in message
news:1165020421.9...@80g2000cwy.googlegroups.com...
Jello World
THIS MUCH
it's just no longer 'Visual Basic'
Why is this OOP so important?
is Web Development _REALLY_ that important?
What percentage of VB people develop Windows Forms Apps?
I just want simple Windows Forms apps.. what is 'Microsoft Forms
Server' is that going to make this easier?
There has to be some relief; building Windows Forms app in VC++ 6.0 is
easier than in VB.net 7.0, 7.1 or 8.0
-Charlie
Jello World
I still write VB6 to this day; I always have and I always will.
it's called Access forms... and i'll never stop doing this until 'real
vb' is practical compared to MS Access
-Charlie
Jello World
as-if
-Charlie
aaron...@gmail.com
According to Evans Data's Fall 2006 North American Development Survey,
overall, developer use of the Visual Basic family has dropped off by 35
percent since last spring.
Moreover, Evans said, "As expected, developers are finally leaving VB6
and earlier versions; they're also leaving VB.NET; which is down by 26
percent. This means Java now holds the market penetration lead at 45
percent, followed by C/C++ at 40 percent, and C# at 32 percent."
Phill W.
> it's just incredibly hard; I don't understand why things had to change
> THIS MUCH
Because Our Friends in Redmond said so ... :-(
> it's just no longer 'Visual Basic'
"Visual Basic" is /might/ be, "VB" it /ain't/.
> Why is this OOP so important?
It's no Panacea. You can /still/ write the same, monolithic slabs of
code that I .. er .. we used to. You might have to use different
classes to do anything useful, though. You probably did before, but
just didn't realise it; Forms have /always/ been Classes.
Try it - you might like it.
> is Web Development _REALLY_ that important?
Not to me.
> What percentage of VB people develop Windows Forms Apps?
An awful lot of them, I'd guess.
> I just want simple Windows Forms apps..
What's so difficult? You create a new Forms application and start
chucking stuff around in the Designer. OK, the code it generates is
/different/ from VB "Proper" and you haven't got Control Arrays any more
(until you realise the difference between Control Arrays and Arrays of
Controls), but I would argue that creating a simple form isn't /that/
much more difficult than it used to be.
> what is 'Microsoft Forms Server' is that going to make this easier?
Not a clue.
Regards,
Phill W.
Jello World
it's a totally different beast; and i'd rather just stick with VB6
until Microsoft starts talking about VB with a TEN YEAR ROADPLAN; who
knows what we should learn and what isnt worth it.
MS has been backtracking on the DAO / ADO thing; and I just flat out
won't invest in MS tech because I don't see stability in this career
track.
I just see VB 2005 as a beta still.
WHEN IS THE SERVICE PACK COMING OUT?
-Charlie
aaron...@gmail.com
-Aaron
RobinS
Robin S.
---------------------
<aaron...@gmail.com> wrote in message
news:1165444682.9...@l12g2000cwl.googlegroups.com...
aaron...@gmail.com
I've read statistics that 75% of vb6 developers never used a class; so
why do they make this shit 10 times more complex; SLOWER DURING
DEVELOPMENT AND EXECUTION.
yeah your stupid programming teacher from college might have claimed
that OOP was a worthy goal.
but I htink that it's a total pain in the ass and slower; more complex
and unnecessary
Maybe I just dont make my software 'complex enough' to need classes.
but as it is; classes make development SLOWER and execution SLOWER.
and VB6 already had enough classes for me.
-Aaron
Master Programmer
- Don't put yourself through the pain.
- Dont waste your time.
-- VB 6.0 was a great language.
-- VB.NET is slow to learn, slow to develop with and slow to run.
People will give you the normal bullshit about OOP (big fucking deal).
Don't be sucked in by the propaganda. I have been forced to use VB.NET
/ ASP.NET for the last 3 years and I can promise you that you will not
like it.
- OVERCOMPLICATED
- CHANGES EVERY 2 FUCKING MINUTES
- NEED TO WRITE MORE CODE THAN EVER BEFORE
Save yourself the aggrivation.
The Grand Master
aaron...@gmail.com
Especially with this:
-- VB.NET is slow to learn, slow to develop with and slow to run.
and this:
NEED TO WRITE MORE CODE THAN EVER BEFORE
MS doesn't need to come out with a new version of VB.net three times in
three years.
They just need to go back to basics.
And mixing OOP and a bunch of XML crap doesn't make our life easier.
VB against SQL Server.
Anything else is a distraction.
-Aaron