| 08.26.05
ASP to ASP.NET Migration Strategy
Making the appropriate selection of an ASP to ASP.NET migration strategy is
not always clear cut. As a developer, you would probably be tempted to
rewrite the entire web application in Microsoft .NET from scratch. However,
your manager might not be as enthusiastic as you are to this idea. The
application is already in production and satisfies the requirements. Why
follow a more risky and costly path if it is possible to start extending the
application in .NET and at the same time preserving an investment in the
legacy ASP code? Especially if a complete migration can be achieved
gradually in a number of evolutionary migration steps, with every step
resolving a concrete migration-justifiable problem.
Read
The Whole Article
Developing ASP.NET Applications with Macromedia's Dreamweaver MX 2004
Without a doubt, the most dominant web design tool today is Macromedia's
Dreamweaver. Dreamweaver enables visual designers to effortlessly create web
sites, and tools such as templates, CSS, and split-screen development have
driven Dreamweaver to the number-one spot. If you are a designer, however,
you know that at some point you'll need to extend Dreamweaver from a simple
HTML development tool to one that allows you to build database-driven
solutions.
Once you begin to think deeply about database driven web sites, a whole new
level of complexity is introduced. For example, it's not safe for a web
browser to directly connect to a database. For this kind of thing, you'll
want to use an Application Server on your web server. There are many types
of application servers you can use, such as Java, ColdFusion, and PHP. The
focus here will be on Microsoft's ASP.NET.
Read
The Whole Article
| Start
delivering qualified traffic to your site today. Click
Here |
|
Utilise client-side code in ASP.NET pages
In this article we'll explore the basics of client-side code usage and why
it may be necessary.
ASP.NET's codebehind structure provides a great way to separate application
code from Web page markup and controls. While it is suitable for most
situations, client-side code is not extinct. There are many situations where
client-side code may be more appropriate and sometimes the best approach.
Read
The Whole Article
ASP.NET Forms
Forms are an essential piece of ASP.NET—the ASP.NET Web programming model
itself wouldn't be possible without forms. The use of forms is not
constrained in pure HTML, but it is subject to some restrictions in ASP.NET.
In ASP.NET pages, a single form can post to itself, and the model provides
for generalized control state management and postback events. Writing
ASP.NET apps is easy and effective because of the single form model.
The restrictions on forms in ASP.NET may sound weird and arbitrary at first,
but actually the model is quite straightforward to work with. However, there
is one real-world scenario that the ASP.NET 1.x form model doesn't address:
having multiple, highly specialized forms in the same page. For example, you
can't have a search box that posts to a different page.
Read
The Whole Article |
