How quickly can you get upto scratch on .net?

[DannyBoy]

I've been working primarily with/on sql server, java, perl, php/ruby & jscript commerce projects for 3 years but would like to focus on .net development now as more and more of the available work I'm being offered is with .net applications / projects.

Haven't had too much time to do my research yet and won't do for another month or two but would just like to know from anyone that works with .net currently, or is planning to start development with it, how long it has taken to learn + any recommendations / advice on what to prepare for before jumping in the deep end.

Any comments are appreciated 🙂

Cheers,
-D

 

[Crusty]

To give you an idea, I've done most of my application dev in Java, but my latest project needed to be done in .NET. Within about a week I was able to write a completely event driven real time stock market analysis tool. It's really not all that different then Java in terms of application design and functionality, just takes getting used to the IDE and different layout to the classes.

Database work is a LOT easier with .NET then with java due to the DataSets and the DataGridViews. Overall, it's not that hard to pick up, and the web documentation is very good and not just MS documentation, tons of other sites with handy tips/ideas.

 

[KB]

As long as you have a good basis in object oriented programming from your previous languages .Net will be a breeze to pick up.
You just need to learn the namespaces and classes that perform the same functionality as java.

I used the .net Quickstarts a lot in th beginning at http://samples.gotdotnet.com/quickstart/aspplus/

 

[Jaxidian]

In my opinion, the two places where you'll spend most of your learning curve is with:

1. .NET-specific classes and controls (such as learning the intricate details of drop downs, gridviews, Datasets, etc.)
2. IF you're doing web development, then page lifecycles, when to do dynamic control creation, and data persistence.

If you go with C#, syntax will be a breeze for you except for some advanced things (perhaps generics tho I dunno what Java syntax is for that off-hand) which you'll just have to look up and remember.

Good luck!

 

[imported_Dhaval00]

To get down and dirty with what .NET can do and how YOU can do it, start with O'Reilly's Programming C# (4th Edition) and Programming ASP.NET (3rd Edition). To learn about the internals, CLR via C# by Jefferey Richter is the best book. Understanding .NET's delegate/event model and Generics is of utmost important as you move your way up to WCF, WF, and WPF. Moving forward, almost all .NET services (Windows, stand-alone, and Web) will be written in WCF. Not to mention the fact, at the database level you have .NET integration with SSIS, SSAS, and SSRS. I actually started with OOP in Java, but switched quickly to .NET after figuring out what it had to offer - the switch wasn't hard at all. As a generalized opinion, I think more and more companies will switch to .NET because of the amalgamation of their development products with their business products.

Have fun .NET'ing and welcome to dark side 🙂

 

[Gunslinger08]

As with most high-level OO programming languages, it's easy to learn and hard to master. You can pick it up in probably a week or less given your experience, but it's going to take you some time to write the most efficient code possible.

 

[Atheus]

Originally posted by: Dhaval00
To get down and dirty with what .NET can do and how YOU can do it, start with O'Reilly's Programming C# (4th Edition) and Programming ASP.NET (3rd Edition). To learn about the internals, CLR via C# by Jefferey Richter is the best book. Understanding .NET's delegate/event model and Generics is of utmost important as you move your way up to WCF, WF, and WPF. Moving forward, almost all .NET services (Windows, stand-alone, and Web) will be written in WCF. Not to mention the fact, at the database level you have .NET integration with SSIS, SSAS, and SSRS. I actually started with OOP in Java, but switched quickly to .NET after figuring out what it had to offer - the switch wasn't hard at all. As a generalized opinion, I think more and more companies will switch to .NET because of the amalgamation of their development products with their business products.

Are you a Microsoft advertisement? 😉

 

[jaynonymous]

The biggest hurdle in learning .NET, IMHO, is learning the classes in the framework. The QuickStarts do a pretty good job of illustrating the basics. I also recommend the O'Reilly Programming C# book. With your experience, I wouldn't think that it would take more than a few months to feel really comfortable in the environment. The Framework is quite large, but it's not too bad to learn once you understand the basics.

 

[replicator]

It is definitely easy if you are knowledgeable with Java. I work with it rarely, but will develop for it on a need basis because there is enough documentation out there and the IDE is as good as it gets.

 

[postmortemIA]

.NET = Microsoft answer/implementation of Java

You'll be surprised how C# looks and acts like Java 🙂

 

[DannyBoy]

Originally posted by: postmortemIA
.NET = Microsoft answer/implementation of Java

You'll be surprised how C# looks and acts like Java 🙂

Most things seem to resemble java &/or elements of it to some degree recently 😕

 

[imported_Dhaval00]

Originally posted by: Atheus

Originally posted by: Dhaval00
To get down and dirty with what .NET can do and how YOU can do it, start with O'Reilly's Programming C# (4th Edition) and Programming ASP.NET (3rd Edition). To learn about the internals, CLR via C# by Jefferey Richter is the best book. Understanding .NET's delegate/event model and Generics is of utmost important as you move your way up to WCF, WF, and WPF. Moving forward, almost all .NET services (Windows, stand-alone, and Web) will be written in WCF. Not to mention the fact, at the database level you have .NET integration with SSIS, SSAS, and SSRS. I actually started with OOP in Java, but switched quickly to .NET after figuring out what it had to offer - the switch wasn't hard at all. As a generalized opinion, I think more and more companies will switch to .NET because of the amalgamation of their development products with their business products.

Are you a Microsoft advertisement? 😉

I have actually been on the receiving end of that comment on more than one occasion 🙂

I would definitely qualify myself as a technologist. As far as Microsoft goes, I think they build great tools for developers... I make a living because of Microsoft, and I see no harm in promoting it as a company. Ultimately if you think about it, Microsoft employs people just like you and me (I know this because I know some of these people). Not to mention the fact that these guys do the grunt work and put out products like Visual Studio, CLR, SQL Server, etc. so that you (?) and I (!) can make a living.

And no, I don't work for Microsoft 🙂

 

[George P Burdell]

Originally posted by: joshsquall
As with most high-level OO programming languages, it's easy to learn and hard to master. You can pick it up in probably a week or less given your experience, but it's going to take you some time to write the most efficient code possible.

:thumbsup: