|
web
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
best way to learn Windows FormsI am a VB6 programmer and I know how to build console apps.. I just
dont understand how to get my mind around WinForms; they just seem a lot more complex than VB6. Thanks -Charlie The big difference is .Net is truly object oriented, and you have to get
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_wo***@hotmail.com> wrote in message Show quoteHide quote news:1165020421.954257.264200@80g2000cwy.googlegroups.com... >I am a VB6 programmer and I know how to build console apps.. I just > dont understand how to get my mind around WinForms; they just seem a > lot more complex than VB6. > > Thanks > > -Charlie > I never had so manny problems with switching to VB.Net ,,,, it is just a
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 VB6regards Michel posseth [MCP] Show quoteHide quote "Matt Fielder" <mfielderREMOVECAPS@nospam.nospam> schreef in bericht news:eECZwdbFHHA.2468@TK2MSFTNGP06.phx.gbl... > The big difference is .Net is truly object oriented, and you have to get > 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_wo***@hotmail.com> wrote in message > news:1165020421.954257.264200@80g2000cwy.googlegroups.com... >>I am a VB6 programmer and I know how to build console apps.. I just >> dont understand how to get my mind around WinForms; they just seem a >> lot more complex than VB6. >> >> Thanks >> >> -Charlie >> > > Check out Tim Patrick's book, Start-to-Finish Visual Basic 2005.
By working through it, you build an entire application, so it covers all the basics, from building forms to data access. Robin S. ----------------------------- <jello_wo***@hotmail.com> wrote in message Show quoteHide quote news:1165020421.954257.264200@80g2000cwy.googlegroups.com... >I am a VB6 programmer and I know how to build console apps.. I just > dont understand how to get my mind around WinForms; they just seem a > lot more complex than VB6. > > Thanks > > -Charlie > I just don't need the basics; I need more advanced stuff
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 RobinS wrote: Show quoteHide quote > Check out Tim Patrick's book, Start-to-Finish Visual Basic 2005. > By working through it, you build an entire application, so it > covers all the basics, from building forms to data access. > > Robin S. > ----------------------------- > <jello_wo***@hotmail.com> wrote in message > news:1165020421.954257.264200@80g2000cwy.googlegroups.com... > >I am a VB6 programmer and I know how to build console apps.. I just > > dont understand how to get my mind around WinForms; they just seem a > > lot more complex than VB6. > > > > Thanks > > > > -Charlie > > If you want to know more about using forms, post a specific
question, not a general "tell me about Windows forms". There is enough information about forms to fill a thousand-page book. Robin S. ------------------------------------------ Show quoteHide quote "Jello World" <jello_wo***@hotmail.com> wrote in message news:1165028811.417992.107960@79g2000cws.googlegroups.com... >I just don't need the basics; I need more advanced stuff > > > 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 > > > RobinS wrote: >> Check out Tim Patrick's book, Start-to-Finish Visual Basic 2005. >> By working through it, you build an entire application, so it >> covers all the basics, from building forms to data access. >> >> Robin S. >> ----------------------------- >> <jello_wo***@hotmail.com> wrote in message >> news:1165020421.954257.264200@80g2000cwy.googlegroups.com... >> >I am a VB6 programmer and I know how to build console apps.. I just >> > dont understand how to get my mind around WinForms; they just seem a >> > lot more complex than VB6. >> > >> > Thanks >> > >> > -Charlie >> > > Jello,
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_wo***@hotmail.com> schreef in bericht Show quoteHide quote news:1165020421.954257.264200@80g2000cwy.googlegroups.com... >I am a VB6 programmer and I know how to build console apps.. I just > dont understand how to get my mind around WinForms; they just seem a > lot more complex than VB6. > > Thanks > > -Charlie > and for the record??
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 Cor Ligthert [MVP] wrote: Show quoteHide quote > Jello, > > 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_wo***@hotmail.com> schreef in bericht > news:1165020421.954257.264200@80g2000cwy.googlegroups.com... > >I am a VB6 programmer and I know how to build console apps.. I just > > dont understand how to get my mind around WinForms; they just seem a > > lot more complex than VB6. > > > > Thanks > > > > -Charlie > > If you don't mind doing it in C# instead of VB, take a look at "Windows
Forms Programming in C#" by Chris Sells, Addison-Wesley publishers. Tom Dacon Dacon Software Consulting <jello_wo***@hotmail.com> wrote in message Show quoteHide quote news:1165020421.954257.264200@80g2000cwy.googlegroups.com... >I am a VB6 programmer and I know how to build console apps.. I just > dont understand how to get my mind around WinForms; they just seem a > lot more complex than VB6. > > Thanks > > -Charlie > it's just incredibly hard; I don't understand why things had to change
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 Tom Dacon wrote: Show quoteHide quote > If you don't mind doing it in C# instead of VB, take a look at "Windows > Forms Programming in C#" by Chris Sells, Addison-Wesley publishers. > > Tom Dacon > Dacon Software Consulting > > <jello_wo***@hotmail.com> wrote in message > news:1165020421.954257.264200@80g2000cwy.googlegroups.com... > >I am a VB6 programmer and I know how to build console apps.. I just > > dont understand how to get my mind around WinForms; they just seem a > > lot more complex than VB6. > > > > Thanks > > > > -Charlie > > Jello World wrote:
> it's just incredibly hard; I don't understand why things had to change Because Our Friends in Redmond said so ... :-(> THIS MUCH > 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. I just really have a problem keeping it in scope.
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 Phill W. wrote: Show quoteHide quote > Jello World wrote: > > 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. ROFL.. C#
as-if -Charlie Tom Dacon wrote: Show quoteHide quote > If you don't mind doing it in C# instead of VB, take a look at "Windows > Forms Programming in C#" by Chris Sells, Addison-Wesley publishers. > > Tom Dacon > Dacon Software Consulting > > <jello_wo***@hotmail.com> wrote in message > news:1165020421.954257.264200@80g2000cwy.googlegroups.com... > >I am a VB6 programmer and I know how to build console apps.. I just > > dont understand how to get my mind around WinForms; they just seem a > > lot more complex than VB6. > > > > Thanks > > > > -Charlie > > 
Other interesting topics
Upgrading Access 97 application to dotNet
Changing Color of Textbox on Hover Best Approach When Saving a New Project Manage DataBase For loop variable date Merging two tables in Dataset? I only want to get the matching info based on the two key fields No Response Redirect but something like Response Forward? How do you start an assembly dynamically with constructors Enter Key vs. Tab Key SyncLock Required? |
|||||||||||||||||||||||
