do i need to be as strong in c# as an asp.net/c# developer as i would as a c# desktop application developer? there seems to be much less c# coding involved when developing asp.net websites than desktop applications. are there certain things in c# that aren't used as often when used in asp.net websites than in desktop software? i was just wondering if there were different ways of approaching learning the language depending on how it will be applied. thanks.
1
-
1difference between c# and asp.net/c# - when you see them, you'll shit bricks.Matt– Matt2010-06-28 10:20:26 +00:00Commented Jun 28, 2010 at 10:20
Add a comment
|
4 Answers
do i need to be as strong in c# as an asp.net/c# developer as i would as a c# desktop application developer?
Yes.
there seems to be much less c# coding involved when developing asp.net websites than desktop applications
No, not less c#. Just different c#.
Here's the secret: start building your web application and when you run into something you don't know how to do, ask it here.
Comments
I think you have to know all the basics of the language when working with ASP.Net.
There are, of course, things that you won't need when working in one or another.
e.g. When working with ASP.Net, you don't need to know anything about WinForms, and most of the time you won't be working with things like threads.
When working with ASP.Net you'll also have to learn lots of things outside C#, and basically learn the basics of web development.
In my personal experience, one of the things that took me a while to get used to was the stateless model of web development (I worked a lot in desktop applications and this model wasn't very clear at first).
So, yes, you have to be strong at c# to start working with ASP.Net.
As an approach, I recommend you read something about the stateless model, that's a good way to start, in my opinion.
Best regards
Comments
You're implying a separation where none exists. The only real difference between ASP.Net and WinForms development is the delivery method. The concepts are the same. Development needs, language restrictions, data concepts, everything still derives from the same framework. The only thing that is truly different is how that end product gets to the customer.
Don't get bogged down in the details of the platform. I think you would do well to understand both platforms of delivery because they are different even if most of it happens "under the covers". Understanding the differences between the two delivery platforms is very useful though.
11 Comments
John Saunders
-1: the concepts are certainly not the same. Web == stateless. Big difference.
Joel Etherton
@John - I would categorize that as a mechanism of the delivery method. While the page is being executed in the thread, the state is identical. An important distinction to be sure, but I did mention that difference in my answer. Thanks for the comment. A lot of people seem to mark -1 and not bother to say why they disagree.
John Saunders
@Joel: you really sound like you don't understand HTTP at all. Are you an ASP.NET developer?
Joel Etherton
@John Saunders - actually yes, I am an ASP.Net developer, and I understand http just fine. C# even in ASP.Net involves more than just the delivery across the protocol.
Rex M
@John I think Joel's point is that for any application of note, the layer at which you care whether the end-user is coming through via HTTP or WinForms is pretty small. The part of the iceberg that's underwater, so to speak, is mostly agnostic to that.
|
ASP.NET does a lot of its magic by creating and compiling classes on the fly and calling methods using reflection or on interfaces. You will understand the framework and what it is doing "behind the scenes" a lot better if you actually understand C# (or VB.NET or the .NET Framework in general)
