When you search for ASP.NET WYSIWYG editors on the Internet, you find loads of plain HTML-based editors. They are typically deployed in web-based content management systems, in which they are used to edit HTML snippets. All of them are based on existing browser technology:

- Internet Explorer offers the DHTML control to edit the HTML - Firefox has Midas, the pendant to the MS DHTML control

The advantage of this technology is that the browser does not require a plug-in or an ActiveX control. However, using this technology, it is not possible to modify complete word processing documents, such as MS Word or RTF files. Furthermore, it is not possible to edit, nor add headers and footers, text frames and other such sophisticated features...

Abstract

The process of establishing a database connection can be time consuming depending upon network connectivity. Connection pooling is a viable option if the network is an issue, and database server resources are available. I'll begin by discussing connection pooling and examining how you may use it in your .NET applications.

Introduction

Connecting to the database is resource intensive and a relatively slow operation in an application but the most crucial of them all. There are several steps involved with establishing a database connection. First, you will establish a connection to the database server over the network. Next, the connection string is parsed and the user authenticated. Finally, the connection is established, and operations may be performed. Connection pooling allows an application to maintain ownership of a database connection...

Dear oh so wonderful ASP.NET,

I know that we programmers are far, far more stupid than your code generator. Clearly, if I write:

<form action="BoardEdit.aspx" method="post" runat="server">

Then actually you might as well assume I'd written:

<form method="post" runat="server">

And left you to figure out what the form action should be, because you can do that perfectly every time, fully accounting for the URL re-writing. If I suggest something different, clearly I would never have a good reason for doing this (for example, in the case that you've got no damm clue how to respect URL re-writing rules, but oh no, that would NEVER happen, would it? Oh, wait...).

Love (the thought of punching) you loads,

Jonathan

This is because the server control tags were not converted into their respecting HTML element tags by ASP.Net. This happens when ASP.Net is not properly registered with IIS. .Net framework provides an Administration utility that manages the installation and uninstallation of multiple versions of ASP.NET on a single machine. You can find the file in C:\WINNT\Microsoft.NET\Framework\v**\aspnet_regiis.exe use the command: aspnet_regiis.exe -u ---> to uninstall current asp.net version. use the command: aspnet_regiis.exe -i ---> to install current asp.net version.