Classic ASP transition to ASP.NET --- how difficult?

[niclipse]

I have a job that is interested in hiring me. The job requires .net programming experience, but they are willing to overlook that because I have so much Classic ASP expereince.

Here's the problem, im scarred of being hired for a job that I dont know 100%, but Im in no position to turn down a job that will allow me to relocate to the area Ive been wanting to move to forever.

My questions are:

What are the differences between the two?
Am I going to get in over my head?
Please describe as much as possible to help me out!

-Nick

[mendhak]

First thing to keep in mind, ASP.NET is not the next version of ASP.

ASP just used VBScript/Javascript. It was interpreted.

ASP.NET uses the .NET framework. Think of the .NET framework as a bunch of DLLs that sit there waiting for you to use it. And you'll be using it for everything whether you realize it or not. But the good thing is, the .NET framework allows you to separate your UI from your UI's logic.

You won't get in over your head. Start by having an open mind and understanding that ASP.NET is new to you. Your experience in web development will help you, not your experience with ASP.

I suggest that you get a feel of how ASP.NET works. To start, get Visual Web Developer which is a toned-down version of Visual Studio. Once you get VWD, have a look at some very simple ASP.NET tutorials. This should give you an idea of what it's all about. Anytime you have questions, post here and we'll help you by being as vague as possible.

On a philosophical/introspective note, think about this... you can't expect to have it easy all the time. You want to move to a certain area for whatever reasons, you have to work for it. Once you become proficient in ASP.NET, you will laugh at your attitude right now. And if you don't try, you'll never know whether you could have done it or not.

[niclipse]

I like the challenge, but hate the fear of not being able to complete a project because my lack of knowledge. I'll bust my ass if I have to, but will definitely need the support from a forum like this.

[niclipse]

Luckily my webhost for my personal website has .net, so I'll be able to tinker there on my free time.

[mendhak]

Your computer at home can also have .NET, easier than having to upload all the time

[Krenshau]

I very much recommend making the switch, regardless of the job. You will be so happy you did. You can do so many things in ASP .NET that you can't do in classic ASP, and you can do everything in ASP .NET that you can do in classic ASP. There is no loss, only gain in functionality. This is important because once you gain a good understanding of what you can do in .NET, you can offer your customer, clients, or the company you work for, more options to make their website better. Better because you gain more functionality, and better because you can complete projects faster due to the ability to do step thru debugging, you don't have to upload pages to run them (Visual Web Developer Express comes with a built in "server"), and you don't have to "roll your own" features as much. There are so many more advantages to ASP .NET, but you will find out when you get started learning it. I do recommend picking up a couple of books to help learn best practices. As previously stated, www.asp.net is a good site, too.