Organising asp.net website development process
        Posted  
        
            by ZX12R
        on Stack Overflow
        
        See other posts from Stack Overflow
        
            or by ZX12R
        
        
        
        Published on 2010-03-10T13:20:13Z
        Indexed on 
            2010/03/11
            5:18 UTC
        
        
        Read the original article
        Hit count: 725
        
Is there a standard practice to organize the process of developing a simple website. there is no use implementing MVC as there is no data base involved. It will be very useful in organizing the project and separating
- the aspx files and master
- page content(this can be very useful in implementing simple cms techniques)
- user controls
- scripts
- styles
- images
is there any industry standard or best practice for this.?
thanks in advance :)
Update: yes the way i have listed is convenient. but it would be great if i could separate server codes and files like master,aspx.. and the actual page content.
One more reason for not using MVC: I usually outsource the SEO process. Now an MVC application can be greek/latin for my SEO expert. :)
© Stack Overflow or respective owner