[RESOLVED] ASP.NET vs Desktop Apps programming
Hello,
I'm new for ASP.NET but not new for programming. My background is VB6, i know HTML, CSS, General RDBMS, and I learned a bit of VB.NET, MS SQL Server and .NET Framework.
My questions is:
If you know very well VB.NET, RDBMS, MS SQL Server and .NET Framework (including XML, Visual Studio IDE), HTML, CSS but you know NOTHING about ASP.NET what is the new things you should learn for ASP.NET to become at least intermediate level ASP.NET programmer?
--
Accept intermediate level ASP.NET just as a general statement. I don't want to dig into it like what exactly do you mean by intermediate and how it's different from expert and basic.
--
The question is what are the brand new things you should learn as an ASP.NET developer comparing to Desktop apps?
The first 2 things it came to my mind are: System.Web Namespace and System.Web.UI Namespace. Also IIS.
Best Regards,
Dimitar Ivanov
Re: ASP.NET vs Desktop Apps programming
Hey,
If you have done VB.Net in Windows Applications, then a lot of the code will be transferrable. What I mean by this is, for instance, any classes the you have used, FileInfo, Directory, XmlDocument etc, they all exist in ASP.Net as well.
The main difference comes in the way ASP.Net pages work, i.e the Page Life Cycle, and PostBacks to the server. This is a completely different paradigm, and the main place the people get tripped up.
In Windows Development, you click a button and the click event gets executed. The same thing happens in ASP.Net, except the page had to first post back to the server, in order for the click event to execute, and then the response is sent back to the client.
If you haven't done so already, have a look here:
http://www.asp.net/learn/
There is a wealth of information.
The two namespaces that you mention are the main ones that you will need to get familiar with.
Gary
Re: ASP.NET vs Desktop Apps programming
Quote:
The main difference comes in the way ASP.Net pages work, i.e the Page Life Cycle, and PostBacks to the server. This is a completely different paradigm, and the main place the people get tripped up.
:thumb:
Can you please quote similar kind of differences? That's exactly what I was looking for in my question - simple list with quotes (differences) with little explanation (no details).
I know this link, there are very useful tutorial up there. In fact there are tons of info about ASP.NET in internet. The things is that these tons of info are mixed with vb.net, xml, html, css, sql, vs studio, ado.net, etc. etc. which are definately a part of ASP.NET but not the "unique" things for ASP.NET.
Re: ASP.NET vs Desktop Apps programming
Re: ASP.NET vs Desktop Apps programming
Good link :check:, and "web forms vs win forms" kind of keywords are good to go, it didn't pop up in my head....:ehh:
Re: ASP.NET vs Desktop Apps programming
Hey,
Do you have any specific follow up questions regarding this?
If not, remember to mark your thread resolved.
Gary
Re: [RESOLVED] ASP.NET vs Desktop Apps programming
Quote:
Originally Posted by
Digitborn
If you know very well VB.NET, RDBMS, MS SQL Server and .NET Framework (including XML, Visual Studio IDE), HTML, CSS but you know NOTHING about ASP.NET what is the new things you should learn for ASP.NET to become at least intermediate level ASP.NET programmer?
If you already know all of that, then you know about 80%, because an understanding of all of that is most of web development. What you need to keep in mind though is that you shouldn't compare winforms and webforms because you will then start trying to 'make' webforms act and work like winforms. It has its limitations and quirks which you learn as you work.
Quote:
--
Accept intermediate level ASP.NET just as a general statement. I don't want to dig into it like what exactly do you mean by intermediate and how it's different from expert and basic.
--
Expert = me. Basic, intermediate and noobs = everyone else. :afrog:
Quote:
The question is what are the brand new things you should learn as an ASP.NET developer comparing to Desktop apps?
The first 2 things it came to my mind are: System.Web Namespace and System.Web.UI Namespace. Also IIS.
Really, don't look at it that way. You don't pick a namespace. Just start coding and questioning as you go along and you'll get advice or you'll find articles that show you how to do things. The important bit in all of this is to make sure you understand what's happening when you use code from somewhere. As long as you're understanding it, you're learning it.
