This post is not actually about the software. Bail out. Have you ever heard about interrupt mitigation? This is a fancy name for techniques used by an OS kernel to avoid being interrupted too often. Normally, each time a device (like network card, or a mouse) wants to inform the CPU about something
This summer my old friend motivated me to restart demoscene activity and I started coding a 4k intro for x86 Linux (which was supposed to be released at WeCan'2012, but we missed the deadline). This is an ongoing work, but I decided to share some experience that I consider interesting. 1. Even C is
IntroThis article is about how to get the memory dump of a process, by checking almost all memory addresses that can store data. Since C# is quite a high level programming language, I think this is the only method available to do this.And since someone asked how to search a string in a process' memo
In one of my previous articles, we explored how to handle Exceptions in WCF RESTful services. In this article the focus is same to handle exceptions but for ASP.NET Web API service. HttpResponseException class plays its role to return HTTP status code as well as further exception details to client.
The site navigation features in ASP.NET 2.0 make it easy to define
a site map and implement common navigation UI elements, such as a breadcrumb, treeview, and menu. Due to its use of
the provide model, you can dictate how to serialize
the site map. ASP.NET 2.0 ships with a default implementation that serializes site map information to an XML-formatted file
(Web.sitemap, by default), but as we saw in Part 4
this logic can be customized to garner site map information directly from the file system or through
a SQL Server database table. Site navigation can even be configured
to use security trimming, which will remove those nodes in the site map for which the currently logged on user does not
have authorization to view.
The site map provider model and security trimming features are used to customize the set of site map nodes used by the navigation
Web controls, and afford a great deal of customization. However, there are times where we may want to customize the rendered
output of the navigation control based on the site map data. For example, maybe in our Menu control we want to
display an icon next to each menu item depending on some classification defined for the menu item's corresponding site map
node. Alternatively, the markup rendered by ASP.NET's built-in navigation controls may not suit our needs. Rather than
displaying a TreeView or Menu, we may want to show the site navigation information in a bulleted list. Such functionality is
possible by directly working with the SiteMap
In this article we'll look at how to accomplish a hodgepodge of customizations when rendering the navigation UI controls.
Read on to learn more!
The goal of ASP.NET's site navigation feature is to allow a developer to specify a site map that describes his website's
logical structure. A site map is constructed of an arbitrary number of hierarchically-related site map nodes, which
typical contain a name and URL. The site navigation API, which is available in the .NET Framework via the SiteMap
class, has properties for accessing the root node in the site map as well as the "current" node (where the "current" node is
the node whose URL matches the URL the visitor is currently on). As discussed in
Part 2 of this article series, the data from the site
map can be accessed programmatically or through the navigation Web controls (the SiteMapPath, TreeView, and Menu controls).
The site navigation features are implemented using the provider
model, which provides a standard API (the SiteMap class) but allows developers to plug in their own
implementation of the API at runtime. ASP.NET 2.0 ships with a single default implementation,
with which the developer can define the site map through an XML file (Web.sitemap); Part 1
of this article series looked at defining this XML file. However, our site's structure might already be specified by existing
database data, or perhaps by the folders and files that makeup our website. Rather than having to mirror the database or
file system structure in a Web.sitemap file, we can create a custom provider that exposes the database
or file system information as a site map.
Thanks to the provider model we can provide a custom implementation of the site navigation subsystem, but one that still
is accessible through the SiteMap class. In essence, with a custom provider the SiteMap class
and navigation Web controls will work exactly as they did with the XmlSiteMapProvider. The only difference will
be that the site map information will be culled from our own custom logic, be it from a database, a Web service, the file system,
or from whatever data store our application may require. In this article we'll look at how to create a custom site
navigation provider and build a file system-based custom provider from the ground-up. Read on to learn more!
Read More >
In addition to this article series on ASP.NET 2.0's site navigation, I am also currently authoring an article series on
ASP.NET 2.0's membership, roles, and profile.
The membership system in ASP.NET provides a programmatic API for creating and managing user accounts, whereas the roles
piece enables a developer to define a set of roles and to associate users with roles. A website that provides user accounts
typically has certain sections of the site that are accessible only to certain users, only to authenticated users, or
to users that belong to a particular role.
For example, a website might have a set of pages that allow a trusted user to edit the content
of the website, or manage the existing users. Rather than simply trying to hide this page and hope no one accidentally
stumbles across it, or hard coding authorization rights to only allow in a single user, a more robust and secure approach
is to define an Administrator role that is then assigned to a select handful of trusted users. These administrative web pages
can then be configured to allow access only to those users in the Administrator role. Similarly, the website may contain
a set of pages that only authenticated users can access.
Since certain sections of the site might only be accessible by certain users this leaves us in
a delimma with site navigation. Do we include those pages that only authorized users can access in the website's site map?
If we do, then all users will see the restricted pages in the site's Menu or TreeView. Why show the links to these
pages for users who can't access them? If we leave out the restricted pages from the site map altogether, then those users
that are authorized to view those pages can't easily navigate to them because they're not part of the site map and therefore
don't appear in the site's TreeView or Menu!
Thankfully, ASP.NET 2.0's site navigation provides a feature called security trimming. When obtaining site map
information with security trimming enabled, only those site map nodes that the currently logged on user has authorization
to visit are available. That means the site's TreeView or Menu will contain just those sections accessible by the currently
logged in user. Read on to learn how to configure site navigation to support security trimming!
Read More >
A Multipart Series on ASP.NET 2.0's Site Navigation
This article is one in a series of articles on ASP.NET 2.0's site navigation functionality.
Part 1 - shows how to create a simple site map
using the default XML-based site map provider and how to display a TreeView and SiteMapPath (breadcrumb) based on the site map
Part 2 - explores programmatically accessing
site map data through the SiteMap class; includes a thorough discussion of the SiteMapPath (breadcrumb) control.
Any website that is composed of more than one page needs some sort of navigation user interface, which is created in a two-step
process. First, the site's logical structure must be defined; then, user interface elements are added to allow the user
to move between sections of the site's sturcture. Prior to ASP.NET 2.0, developers were required to tackle both of these
steps on their own. With version 2.0, however, ASP.NET provides a simple way to define a site's structure and includes
a handful of Web controls designed specifically to display site navigation user interfaces.
In Part 1 of this multi-part series of ASP.NET 2.0's
site navigation features we examined how to create the Web.sitemap XML site map file and how to display site
navigation information through the site navigation Web controls, which include:
SiteMapPath, which displays a breadcrumb (Home > Electronics > XBOX)
TreeView, which displays a collapsible, vertically displayed tree, showing the entire site map hierarchy
Menu, which displays either a horizontally- or vertically-aligned menu
Part 1 only provided a cursory introduction to both the site map file and navigation Web controls' functionalities and
capabilities. In this second part of the article series we'll turn our attention to programmatically working with the
site map information, as well as looking at the SiteMapPath navigation Web controls in detail. Read on to learn more!
Read More >
A Multipart Series on ASP.NET 2.0's Site Navigation
This article is the first on a series of articles on ASP.NET 2.0's site navigation functionality. This first part of
the series examines the basics of site navigation, showing how to create a simple site map using the default XML-based
site map provider. Future articles will cover more advanced features of site maps as well as how to create a custom
site map provider.
Any website that is composed of more than one page needs some sort of navigation user interface. A navigation user interface
might be as simple as static hyperlinks to the other pages in the site, or might involve the use of menus or trees.
But before a navigation user interface can be created for a site, the site's logical structure must first be
defined. (This logical structure is often referred to as a site map.)
For example, a website like Amazon.com is arranged into various sections by product line, like Books, Electronics,
Computers, DVDs, and so on. Each of these sections may have sub-sections. Books is broken down into categories like
Accessories, Books on CD, Novels, History, Romance, and so on. Typically, these logical structures form a hierarchy of
sorts. The screenshot below shows an abbreviated version of Amazon.com's site map.
Once the site map has been defined, the site's navigation user interface can be created. At Amazon.com, the main page
lists links to each of the main sections along the left-hand side of the page. Drilling down into a particular section
lists that section's sub-sections on the left. Other navigation user interfaces could be used as well, though: you might
have a tree showing the various sections and sub-sections, or a menu that listed as top-level menu items the sections
like Books, Electronics, DVDs, and so on, with those menu items' submenus containing the respective section's sub-sections.
Prior to ASP.NET 2.0, developers typically rolled their own site navigation solutions. ASP.NET 2.0, however, makes
defining a site's structure and implementing it using common navigation user interface elements a walk in the park.
In this article we'll look at ASP.NET 2.0's site navigation features. Read on to learn more!
Read More >
Welcome to codefeeds.com
Stay current by checking the top programming feeds in one convenient location.