Do you like asp.net?

[bill7771]

I'm wondering what people think of asp.net; how you like working with it. I've coded a lot of html and javascript, jsp, classic asp, etc. and I'm balking a bit when it comes to committing to learning asp.net. I'm uncomfortable reading about asp.net because it abstracts so much of what web coding is all about and I imagine eventually, an asp.net coder is still going to have to learn html well, along with javascript, css and various other web-related languages/technologies. I feel that Microsoft's attempt to make web-coding feel like Windows desktop coding just can't work because of the fundamental differences in the environments. Maybe I just need to forge ahead and it will all become clear to me. Do you find yourselves using the web controls? What parts of asp.net do you like/dislike?

Thanks,

Bill

 

[jbenson001]

To answer your question, I LOVE asp.net compared to classic ASP coding. The separation of code and html is one of the best points of it. Mixing the 2 is sloppy and makes debugging a nightmare. By using the code-behind model, your code is in one place, and easy to debug with Visual Studio's debugger, which can debug javascript and sql stored procedures.
Yes you are correct in that learning ASP.NET does not mean that you need to know nothing else. Of course you still need to understand HTML, CSS, a client side langage and of course a database language.
I know it's difficult to learn something new after you have done something for so long and are proficient at it. Just get a good book, and do some simple applications. They way I learned is to take a small application(windows or asp) and covert it to asp.net. The fact is, that eventually you will have to learn it as most new development will use the .NET framework, and the only jobs for asp will be to maintain code, not develop new code.
So, I say, try it, you'll like it. It will take a little time, but this forum is an excellent source for help. And of course there are many resources on line to help.

Good luck.
Jim

 

[jshurst]

I agree with jbenson. You will still need to know CSS, Javascript, html, and a database language to write applications...sure you can drag some controls on the screen if you want to, but eventually you'll need to go behind the scenes.

I love asp.net coding. The .NET Framework blows all other development platforms away.

Regards,

J

 

[ca8msm]

Coming from a HTML background, you'll instantly start to see the benefits that the code separation model brings. All the server-side controls do is act as a method of outputting the HTML that you[/b want (if you find controls that don;t output what you want, either don;t use them or use a control adaptor to alter the output) yet make the act of controlling the logic of the page much easier.

Personally, I don't like the drag and drop culture as people do think of it like windows programming, and we see lots of people on here who have absolutely no concept of how web applications work. I can see this won't apply to you and I think you'll grow to love it. I'd try thinking up a simple scenario to develop an application for, and post here for advice on each section and go and try some of the methods people advise you on.


-------------------------------------------------------

Mark,
[URL unfurl="true"]http://aspnetlibrary.com[/url]
[URL unfurl="true"]http://mdssolutions.co.uk[/url] - Delivering professional ASP.NET solutions
[URL unfurl="true"]http://weblogs.asp.net/marksmith[/url]

 

[bill7771]

Thanks, Guys, I'm encouraged. I've got the APress book by Matthew MacDonald, Beginning ASP.Net 3.5 in C# 2008. Seems like a good book, too. I like C# and Visual Studio and the .net classes, as I've been working with them all in the Windows desktop environment. I also like C# for code in a web app because it's easier to switch to javascript from C# as they're more alike in syntax than Basic and javascript are.

Thanks again;
Bill

 

[jbenson001]

If you are used to javascript then C# is a more natural decision. I came from a PowerBuilder background so VB was easier for me to understand. Either way, they both have the same functionality. I'm sure you like it.

 

[bill7771]

Jbenson001;

I like C# over VB for coding in the asp.net environment not because C# syntax is closer to what I already know, (done a lot of VB over the years), but because in the web environment I'm coding a lot of javascript on the client side, so swithcing between the two languages all the time is easier for me if they've got similar syntax. For example, I find myself coding foreach instead for {} in <Script> tags and getting the errors and having to convert to javascript. I guess stopping and thinking what I'm doing first would work too.

(Avoiding these doubly-underlined add/links while scrolling in these forums is like playing a video game.)

 

[jbenson001]

I hear you, that makes sense.

 

[jmeckley]

I love c# and .net framework. I have a love/hate relation with webforms.
love because
1. they are easy to use.
2. work great for smalll apps
3. allow you focus on data and behavior instead of presentation

hate because
1. they are near impossible to unit test
2. postback/viewstate is akward (although I have come to deal with it)
3. near impossible to unit test for automation. haven't tinkered with Watin yet.
4. my js/css/ajax skills are novice at best because I've relied on webforms.

If i had more time/confidence I would make the transistion to monorail or MS MVC (c# 3.5). these .net web frameworks use a RESTFUL mothodology rather than a postback model.

Jason Meckley
Programmer
Specialty Bakers, Inc.