How long does it take to become a good asp.net programmer?

I was told that I need to learn some basic C# programming to start ASP.NET. So I am currently learning C# with a LOT of difficulties. Got problems understanding OOP as well as some


(for loop). Should I give up?? I am 49 and was thinking getting into .NET development. What do you guys suggest I should do??How long does it take to become a good asp.net programmer?
Stick with it. It is very rewarding. But, like many things in life, it is not terribly hard to learn but very difficult to master. With quite a bit of prior programming experience, I felt that I had ';learned'; .NET in about 6 weeks of working with it. But, I have been using it for almost 6 years (since it was first available) and only in the last year would I even begin to say that I have ';mastered'; it. I would say I am in the very, very bottom of those who would be considered .NET gurus. So if that helps you get any idea of what kind of effort it requires...





But of course, you do not have to be a guru to do even very impressive, sophisticated things with .NET. It is a very broad platform, and I know many who have made it to ';senior developer'; level after only having used it for 2 or 3 years. They also had prior programming experience, though.





You mention that you are struggling with OOP concepts. This suggests that you are learning .NET as possibly your first programming language, or at least your first real one. Don't worry about the .NET part - concepts like OOP and for loops apply to (nearly) all programming languages, and you would have to learn them regardless of the specific language you choose. So you are actually learning two things at once - programming theory and .NET/c#. Because of that, give yourself extra time, and take into consideration the fact that you really are learning two subjects at once.How long does it take to become a good asp.net programmer?
You can use ASP with either C# or VB. In my opinion VB is a little easier to grasp as it is based upon a beginner language (BASIC)





OOP - Object oriented programming is just a fancy way of grouping related parts of a program together. OOP allows you to structure your code so that is is easier to read, maintain and reuse.





In an OOP program you have Properties, Events and Methods which are grouped together into the following:


Class, Module, Form


.


Properties - describe


Events - indicate something has happened


Methods - do something








A Form is a container for program code with a user interface. ( a Window)


A Module is a container for related code like a form but it has no visible interface


A Class is like a module but has the ability to be copied.





You can think of a Class as cookie dough... With it you can make different types of cookies. A Class object called Cookies is copied and among the different copies some of the properties are changed by the baker.





So with a flavor property you can set it to represent different types of cookies. Chocolate Chip, Peanut Butter, Ginger ect.


The copies are all cookies it is the value of their properties which set them apart.








With our cookie dough you need a method to bake it and we need a property to indicate if it has been baked.





So the Cookie Class will have a method called Bake which will set a property IsBaked to True to indicate that the cookie dough is no longer raw but a finished baked cookie.





This brings us to the topic of Events... Events tell the program something has happened. When an Event happens the section of code related to an event fires and the section of related program code will execute.





To tie this in to our cookie class...


When we baked our cookies we most likely baked a dozen. So we could have aother property called Count. We could have as part of our Bake method some code which adds 12 to the Count.





Now for an Event.... the most likely Event to have with a Cookie Class might be. ';Eat A Cookie';





With the ';Eat A Cookie'; Event we can indicate to the program that something has happend. ';Eat A Cookie'; will reduce the Count by 1. So Every Time you eat a cookie the count is reduced.





You can make more events to trigger other program functions.


Like when the Cookie count drops to zero fire an Event called ';Time To Make More Cookies';