Home/ Questions/Q 1002191
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-16T07:47:45+00:00

what is the stack for a asp.net Web forms application?and why? example for ASP.NET

  • 0

what is the stack for a asp.net Web forms application?and why?

example for ASP.NET MVC there is an example:

http://codeclimber.net.nz/archive/2009/10/15/my-asp.net-mvc-stack-and-why-i-chosen-it.aspx

thanks

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    To be perfectly honest, this depends a lot on the specific project you plan to build with WebForms. Since I’m newer to MVC, I do just about all of my .NET development with WebForms. So here’s the "stack" (framework + tools + components) that I use when building an application:

    Framework

    Obviously, ASP.NET WebForms. I make sure to keep all of my different layers (presentation layer – aspx webform, business logic – aspx.vb/aspx.cs codebehind, data access layer – additional classes) separate while I’m building.

    Tools

    • Visual Studio 2010 – I dare you to find a better tool for developing a .NET-based web application.
    • SQL Management Studio Express – Fantastic tool for managing your database setup
    • TortoiseSVN – Subversion tool that integrates directly into Windows’ contextual file menus. It’s great for quickly committing/reverting projects!
    • BugTracker.NET – Great bug tracking tool that integrates with TortoiseSVN.

    Libraries

    • jQuery – I use this for everything
    • jQuery UI – Great for adding "squishy" user interface elements and building out more interactive web forms
    • Flexigrid – I use this for building datagrid elements on my sites. Since it’s built with jQuery, it interfaces nicely and handles AJAX data loads remarkably well.
    • YUI – Another JavaScript library that’s great for animations and transitions.

    Testing

    • Visual Studio Debugger – fantastic for stepping through server-side code to make sure things are working
    • Firebug – Firefox extension – Absolutely essential for debugging client-side scripts and for identifying HTML/CSS errors
    • IETester – Useful for anyone supporting commercial clients (who might still be using IE6)

    For deployment, I use a set of custom tools that create unique filenames for frequently changed files that will need to bypass a user’s cache when they’re changed – i.e. whenever a CSS or JS file is updated or I change an image, I’ll append a unique string to the end of the filename so the browser re-fetches the file.

    • 0