Leading the jump from Classic ASP to ASP.NET, any advice? -


So I have just started in a new company, which is 99% of its code written in classic ASP (from Mostly poorly written) and they were part of the reasons I hired on because I had worked with both ASP and ASP.Net in the past. The ASP.NET experience was VB.NET, but I have worked in college in C #, but I like it because I have done a lot of work in PHP in the past and when I am not focusing, I started to type and on many occasions in ASP I tried to get out of my habit in a semi-colon, and to go back and remove it.

But I want to retreat, basically I do not have the need of knowledge, making the best decisions on things get notes of some important procedures on which I would like advice:

  • Version Control - The truth should be said that I have never actually used it. On my own, I never had the power to push me to use the moment and the shops I worked in, always take care of the air.
  • Local Dev surroundings - Something is probably that I'm Google quickly but I want to setup local dev environment so I can test the stuff without fitting it anywhere
  • Change Live Push - I have never understood this step by checking anything in the version control and seeing it, there is an automated type of automated system that can "see" I'm checking you Let me see what is different between this and the live version and push the affected files "- Probably there is a lack of vc to understand everything at once: (
  • IDE
  • MVC.NET - Easy to pick up? I always hate the web form The whole concept, it seemed that in the end the internet was not completely fit, the rest of the world would be developed Yes
  • anything - like I said I'm relative

Edit: To get advice and make, I think <3>

Version Control:

Obviously take a look at the subversion, it's free, we use a pend-on-hosted service called Assembla (www.assembla.com), but you can not connect to the server on your network. Est Can afford to drink. The most popular client is called TortoiseSVN () You can also see a look at VisualSVN () which are integrated into VS IDE, their site also has an easy SVN server installation.

Local Dev Environment

Both the VS web-server built in local IIS or VS are OK, I really think it's a priority. Opening a website (file system based) rather than IIS based works very well for us.

Change Live Push

ASP is very page Page-based development and compilation is not needed, copying files to a test or production site is quite easy is. Depending on how you can compile / publish your asp.net site, you will need to compile the library code and publish your web application / website.

To update test / production sites.

IDE:

I recommend updating the latest beta version of VS 2010 and use it.

<

Anything else:

Consider the rollout, are you changing everything before you live?

Consider adopting an existing structure, using an ORM, or business objects objects framework, possibly code-generation. Take a look at CodeSmith, it has a different ORM / Business Object framework associated with it. (These will use different technologies and technologies in the framework of the net, which you will have to learn)

Look at the basic structure of the site:

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

Site membership and permissions: Take a look at the membership provider, the rollpiver and build your own.

Different UI in Reusable UserControls

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


Comments

Popular posts from this blog

sql - dynamically varied number of conditions in the 'where' statement using LINQ -

asp.net mvc - Dynamically Generated Ajax.BeginForm -

Debug on symbian -