Leading the jump from the classic ASP to ASP.NET, is there any suggestion?

< /p>

So I just started a new company, 99% of its code is written in classic ASP (most of which is not well written), and part of the reason they hired me was because I had used it in the past ASP and ASP.NET. The ASP.NET experience is VB.NET, but I used C# when I was in college, but I like it only because I have used a lot of PHP in the past. When I didn’t pay attention, I just Start typing C syntax and have it. There are many occasions in ASP. I just end the line in a semi-colon out of habit and have to go back and delete it.

But I digress, basically I just Without the knowledge I need to make the best decision, I have jotted down some key processes that I like:

>Version control – to be honest, I never actually use it. It’s just my own In other words, I have never had so much time to push me to use it. The store I work for is always cautious about the wind. I want to know what server-side and
>local development environment you think I should use-maybe I just quickly Google , But I want to set up a local development environment so I can test things without having to first FTP somewhere to push the change live-I never really understood the steps between checking version control and seeing it, whether There is some kind of automated system that can “Hey, I saw you checked in, let me see what is the difference between this and the real-time version and push the affected files”-it may just be lack of vc understanding all together:(
> IDE-download VS2010 Beta 10 now, hope it is stable
> MVC.NET-easy to pick up? I always hate the whole concept of Web Forms, it seems that it is not suitable for the Internet being developed in other parts of the world in the end.
> And something else – like I said I’m relatively new to this stack so I like Any suggestions I can get as early as possible to avoid any “shit, I wish I knew 3 months ago” moments

Edit: accept the suggestions and make this community wiki

Version control:

Absolutely look at SubVersion, it is free, we use a paid hosting service called Assembla (www.assembla.com), But you can install the server on the network. The most popular client is called TortoiseSVN (http://tortoisesvn.tigris.org/), which is also free.
You can also check the VisualSVN (http://tortoisesvn.tigris.org/) integrated into the VS IDE. ://www.visualsvn.com/), their site also has a convenient SVN server installation.

Local development environment

Local IIS in VS or built-in VS Web server It’s all good, I think it’s really popular. Opening a website (based on file system) instead of IIS seems to work for us.

Promote change

ASP is based on The development of the page does not need to be compiled, and it is very easy to copy the files to the test or production site. According to the way you compile/publish the asp.net website, you need to consider how to compile the library code and publish your web application/website.

I recommend using SVN to submit changes and update the test/production site first.

IDE:

I recommend updating to the latest Beta version of VS2010 and using it.

p>

Anything else?

Considering the launch, did you replace everything before going online?

Consider adopting existing frameworks, using ORM or Business Objects frameworks, and possibly even code generation. Take a look at CodeSmith, it has various ORM/Business Object frameworks related to it. (These will use .net The various technologies and techniques in the framework, you need to learn)

Look at the basic structure of the website:

Consider asp.net WebForms (application) or MVC (website) [Yes Yes, this is a very basic analysis of the difference]

Site membership and permissions: check MembershipProvider, RoleProvider and build your own.

File system: consider uploading files Way and location.

Separate the UI into reusable UserControls.

HTH, good luck, you have a lot to do…

< p>