|
|
|
 .NET Namespaces (1966)
.NET Framework Namespaces | Applications (895)
Management, Email, Graphics, Search.. | Articles & Samples (35837)
Assembly, Caching, Controls, Reflection.. | Community (108)
Conferences, Chat Rooms, Jobs, Training.. | Component & Controls (1004)
Forums, Management, Email, more.. | Developers Sites (136)
Sites dedicated to developer community.. | Developers Training (252)
Training CD-ROMs, Videos, Courseware.. | Downloads (333)
Service Packs, Code, Msdn Show.. | Hosting Services (141)
ASP and ASP.Net Hosting sites.. | Introduction (340)
ASP, ADO.Net, C#, VB.NET, XML | Knowledge Base (2219)
Knowledge Base Articles, Samples, Tutorials, HowTos... | Sample Chapters (243)
Sample Chapters from Developer Books.. | Silverlight (127)
Silverlight | Support WebCasts (630)
Microsoft's Support WebCasts |
|
|
|
|
Total Hits: 0 | Today: 0
|
Author: Scott Mitchell
|
Rating:
|
|
Most data-driven web applications have a fixed data model and user interface. What I mean by "fixed" it that the data it needs to be captured is known in advance. Consequently, the database's tables are created before a single line of code is written and the application's user interfaces are dictated by this pre-determined data model. While most applications work with a fixed data model there are scenarios where the parts of the data model need to be defined by the end user. Such applications ar...
|
|
|
|
Total Hits: 0 | Today: 0
|
Author: Scott Mitchell
|
Rating:
|
|
ASP.NET includes a number of data source and data Web controls that make it remarkably easy to work with data from a web page. For example, to display the results of a database query simply add and configure a SqlDataSource control and then bind that to a GridView, ListView, or some other data Web control. There's no need to write any source code; the data source controls allow declarative access to data. For more information on working with data in ASP.NET see my Accessing and Updating Data in ...
|
|
|
|
Total Hits: 0 | Today: 0
|
Author: Scott Mitchell
|
Rating:
|
|
ASP.NET web pages commonly display messages in response to user actions. For instance, a typical CRUD (Create, Read, Update, Delete) web page might display the message, "Record deleted" immediately after deleting a record and the message "Record updated" immediately after updating a record. Likewise, there would be messages displayed for inserting a new record and messages displayed in the event of an error. Such messages are typically displayed using a single Label Web control. This control may...
|
|
|
|
Total Hits: 0 | Today: 0
|
Author: Scott Mitchell
|
Rating:
|
|
This article is the second installment of a four-part series that examines how to build a data-driven web applications that offers dynamic user interfaces. Over the course of this article series we will build a complete and functional web application with a dynamic, data-driven user interface. Specifically, the demo application is a fictional website used by numerous law firms to manage their clientele. The application uses both a fixed and dynamic data model for law firms to manage their client...
|
|
|
|
Total Hits: 0 | Today: 0
|
Author: Scott Mitchell
|
Rating:
|
|
This functionality is most commonly used to search the Internet using search engines like Google or Live.com. I recently was reading Scott Hanselman's blog and found an interesting entry on how to let your visitors add your website to their search bar. In a nutshell, you need to provide information on how to search you site in an XML file according to the OpenSearch standard. Next, reference this file in the head element on each web page in your site via a link tag. When a user visits your site ...
|
|
|
|
Total Hits: 0 | Today: 0
|
Author: Scott Mitchell
|
Rating:
|
|
Several of the earlier installments in this article series examined how to apply authorization rules in order to prohibit particular users, roles, or classes of users from accessing particular resources. For instance, Part 2 showed how to define URL-based authorization rules in web.config for roles. With just a bit of XML markup, it is possible to block particular users or roles from visiting certain web pages. Just installments also looked at using the LoginView control, which displays differen...
|
|
|
|
Total Hits: 0 | Today: 0
|
Author: Scott Mitchell
|
Rating:
|
|
Last week's article, Using a Dynamic IN Clause, showed how to display detail records for a set of user-selected master records. This entailed creating a User Defined Function (UDF) in the database that would translate a comma-delimited string into tabular data that could then be parsed by SQL's IN keyword. Following that, the user interface was created using a CheckBoxList to enumerate the master records and a GridView to display the details records for the checked master records....
|
|
|
|
Total Hits: 0 | Today: 0
|
Author: IIS Team
|
Rating:
|
|
Request-based tracing provides a good way to figure out what exactly is happening with your requests and why, provided you can reproduce the problem you are experiencing. Problems like poor performance on some requests, or authentication related failures on other requests, or even the server 500 error from ASP or ASP.net can often be very difficult to troubleshoot--unless you have captured the trace of the problem when it occurs. That is where failed-request tracing comes in. It is designed to b...
|
|
|
|
Total Hits: 0 | Today: 0
|
Author: Scott Mitchell
|
Rating:
|
|
To say that debugging support was lacking in classic ASP is a bit of an understatement. One of the most common debugging "techniques" for classic ASP developers was to simply place Response.Write statements in various code portions in order to see certain variable values or to ensure that a particular piece of code was being reached. One of the most common / useful places to put such a debugging Response.Write is right before executing a dynamic SQL statement....
|
|
|
|
Total Hits: 0 | Today: 0
|
Author: Rob Howard
|
Rating:
|
|
Whenever I give a presentation on ASP.NET, it's always fun to watch the audience when the new tracing functionality is demonstrated. For those of us who have built solutions with ASP, tracing is a godsend! In this month's column, we're going to look at the tracing feature in ASP.NET. Let's start by discussing the common tracing technique for ASP, Response.Write()....
|
|
|
|
Total Hits: 0 | Today: 0
|
Author: Robert Walling
|
Rating:
|
|
A standard debugging tactic when developing Active Server Pages (ASP) is to use Response.Write statements to display troubleshooting information to the screen. With the release of Visual Studio .NET and its accompanying step-through debugger this practice has (thankfully) become obsolete in ASP.NET. However, once an application is deployed to a web server the debugger cannot be used without installing Remote Debugging, a practice frowned upon by system administrators due to security issues. One ...
|
|
|
|
Total Hits: 0 | Today: 0
|
Author: Bean Software
|
Rating:
|
|
Tracing is a way to monitor the execution of your ASP.NET application. You can record exception details and program flow in a way that doesn't affect the program's output. In ASP.NET 2.0, there is rich support for tracing. The destination for trace output can be configured with TraceListeners like the EventLogTraceListener....
|
|
|
|
|
|
