views:

167

answers:

5

Possible Duplicate:
How can I learn ASP.NET?

I'm a new comer to the ASP.Net world , i learned C# before and i have 3 years experience of C#,i wanna to ask what are the required steps to be professional in ASP.net in short time ,also i wanna to ask , is it a must to learn JavaScript ,Jquerey,CSS because i knows so little info's about them, and i feel they are so important in the web world ,from where to begin,any resources can help me ..

+2  A: 

To start with ASP.NET, go to http://asp.net. They also have an MVC section. This is probably the best resource to start with.

Both ASP.NET and ASP.NET-MVC have good things going for them, ASP.NET was designed to be familiar to VB6/WinForms developers and is an abstraction over HTML/HTTP, which is fairly leaky. MVC is much closer to pure web development (as it was with classic ASP).

In terms of learning JavaScript and CSS - if you are at all serious about web development, you need to learn these.

jQuery is a JavaScript library - it makes lots of things in JavaScript easier to do, so well worth the investment.

Oded
+1  A: 

I think you should focus your efforts on learning ASP.NET MVC. Although it is built on top of ASP.NET, it does require a different way of approaching website design. It is the future and it is a lot easier to work with.

Although ASP.NET has served us well for many years, most serious new web projects will be written in MVC going forward.

For JQuery: the examples on http://docs.jquery.com/Main_Page are a good place to start. Also: if you can, get the book JQuery in Action. I found it invaluable.

Daniel Dyson
@Daniel Dyson. I'm a huge MVC fan and all my development has switched. But thats a bold claim that its the future! Microsoft has said Webforms and MVC will continue to be updated and supported.
Pino
I agree. It is a huge claim. And yes, WebForms will be supported well into the future. However, I think for someone Starting Out, why trouble yourself with the quirks and workarounds of ASP.NET when there will be plenty of work available in MVC. You just have trawl through StackOverflow ASP.NET tag to see the many issues caused by the codebehind page event model of ASP.NET. Think ViewState or dropdownlist selection lost on postback/rebinding etc. I could go on but am running out of characters. I would rather have done without that pain for the last 10 years!
Daniel Dyson
@daniel dyson Totally Agree, just wanted to make sure that it was clear webforms isnt going away.
Pino
+1  A: 

also a very interesting resource is www.tekpub.com. There are series of videos about asp.net, asp.net mvc and jquery (amongst other topics)

Roger
+2  A: 

So maybe these steps as a suggestion:

  • Learn HTML / CSS

Fundamental really - whether you go down the ASP.NET or ASP.NET MVC route, you'll need to know this. Learn how to use html layout containers such as 'div' and then learn how to transform these with CSS stylesheets. It's fairly easy to put together clean layouts using this.

For HTML, there's load on the net to get you started. Two for starters

http://www.w3schools.com/html/ http://htmldog.com/

Those sites also brush upon CSS. I actually bought this book and it really did get me up to speed quickly and showed techniques for common layouts.

  • Choose between ASP.NET and ASP.NET MVC.

As mentioned above, there are plenty of resources on http://www.asp.net/. It's good to get an understanding of the differences between the two approaches.

Personally, if I was undertaking any new work now - where possible I would use ASP.NET MVC as it forces you to write sites that are much easier to unit test and it's just a nicer seperation of concerns, but it all depends on the kind of sites you'll be putting out there really.....both are easy to learn, but if you wanted a very short, shallow learning curve, I would say ASP.NET is your best bet. May even be an idea to learn and understand that first, before learning ASP.NET MVC and seeing what you feel its advantages are your for applications.

  • Javascript / JQuery

Depending on the sites you produce and how fine grained control you want, you may find yourself needing to use Javascript. For AJAX, a lot of it is shielded away from you with ASP.NET / MVC and you can get partial page postsbacks working with little or no effort (again, once you learn ASP.NET this term will mean more to you). JQuery is excellent and does a nice job of shielding you from some of the quirks of Javascript. ASP.NET MVC adds JQuery files to a project by default now (not sure if ASP.NET does?). There are some nice little JQuery things out there, such as lightbox for displaying a nice gallery of images on a site.

Have fun!

Michael
thank u so much , this is a great help,I have already worked on asp.net,but always i feel i missed some thing,they don't like professional web sites through the internet,i don't know may be the design,the interface,the accessibility,and i can't do a professional testing to my work(my pages,every day i find i missed some thing like checks or handling exception etc),finally the security and performance issues,the books and articles about them so complex, i wanna to learn how to build a secure web application with moderate performance.and easy to modify.
Security is pretty easy now - there are tons of resources on http://www.asp.net.Feel free to mark as answer if of any use! ;-)
Michael
Using 'general' JavaScript libraries isn't a good thing as it inhibits standards development and stems the outflow of users from using Internet Explorer.
Delan Azabani
@Delan Your ignorance knows no bounds. JQuery works just as well on a PHP rendered page as on a pure HTML page as it does on an ASP.NET MVC page.
Daniel Dyson
+1 Michael. Nice answer
Daniel Dyson
Did I say that JavaScript libraries work differently on PHP, plain HTML or ASP. No, I didn't. I said that using general libraries is generally bad. This is because all the patchwork stops the development of real, native standards. It's also bad because all the babysitting removes the need for people to stop using Internet Explorer.
Delan Azabani
+1  A: 

While I can see some validity to Michael's answer, if I may take the opposite side of things:

ASP.Net has its own form of mark-up that can either be cool or annoying if you start using a lot of these controls it can get away from some of the direct HTML stuff. So while you may need to know some HTML, I'm not sure I know every kind of tag ever supported by HTML4 for example. Writing a basic "Hello World!" page in a few different forms in ASP.Net could be a useful exercise as there are at least a handful of ways that I could imagine giving that as an example. I haven't looked into ASP.Net MVC too much so there may be some major changes there for me to see yet.

Javascript is very common, especially if you get into AJAX-enabled sites which are quite common. Some of the basics of Javascript are easy enough to get but there are likely all kinds of tricks and tips that I'm sure I'll never know and that's OK.

jQuery is a nice framework for handling some stuff in Javascript but I'm not sure I'd say that it is required to know it. I've used it for the past couple years in my current work but that is because it is part of the main website we are rebuilding. I wouldn't say this is required but it can be handy for doing some tricks on a site like show/hide sections or binding various button actions to things.

CSS is likely the most hit and miss on this list as some could argue that this is more for designers to write and handle while others may say that developers should write the CSS. I've done some work with CSS for a few years now but it still isn't my forte.

There is the potential to get more in the middle-tier stuff with C# and end up with a bunch of web services so that there isn't as much UI work which could simplify things for you if you want to go down that road. At the same time, don't forget that there can be a number of other software packages that can run on top of ASP.Net like Sitecore, which can mean getting more into XSLT and XML than using C# at times.

JB King
I can see where you're coming from here. ASP.NET MVC does keep you a lot more in touch with the HTML though - a lot cleaner markup and less bloat.If you're going to be building websites, I do think it helps to understand HTML and CSS though. After all, if you decide to move away from Microsoft technology completely, you've still got transferable skills.
Michael