Infragistics: How to set Application Styling settings through Web.Config

You can use the AppStyling Visual Studio Add-in which is available from the Tools menu in Visual Studio or alternatively, you can manually add the settings into your web.config as seen below.

<configSections>  
   <section name="infragistics.web" 

type="System.Configuration.SingleTagSectionHandler,System, Version=1.0.3300.0, 

Culture=neutral, 

PublicKeyToken=b77a5c561934e089" />
</configSections>
<infragistics.web styleSetName="ElectricBlue" styleSetPath="~/ig_res" 

enableAppStyling="true" />

Good luck

Top 6 Firefox Extensions for Web Developer

Every one knows that Firefox has tons of plug-ins and add-on’s, but there are a few any web developer must know and use.

FireBug: Firebug integrates with Firefox to put a wealth of development tools at your fingertips while you browse. You can edit, debug, and monitor CSS, HTML, and JavaScript live in any web page.

FireShot: FireShot is a Firefox extension that creates screenshots of web pages. Unlike other extensions, this plugin provides a set of editing and annotation tools, which let users quickly modify captures and insert text and graphical annotations. Such functionality will be especially useful for web designers, testers and content reviewers. It’s possible to choose whether entire web page or only visible part of this page should be captured.
Screenshots can be uploaded to server, saved to disk (PNG, JPEG, BMP), copied to clipboard, e-mailed and sent to external editor for further processing.

CSSMate: Inline CSS Editing Evolved. Originally a port of the fantastic EditCSS tool that I’ve been using for many months. I’ve gutted it, made each stylesheet load into a separate tab. Removed the save load clear functionality as i found it to be useless and added in support for loading stylesheets that have a media type of “all” instead of “screen”.

ViewSourceWith: The main goal consists to view page source with external applications but you can also…
- open page source as DOM document, read faq
- open CSS and JS files present on page
- open images using your preferred image viewer (e.g. GIMP or ACDSee)
- open PDF links with Acrobat Reader or Foxit Reader or what you prefer
- edit textboxes content with your preferred editor and automatically see modified text on browser when you re-switch focus on it, this simplifies wiki pages editing, read faq
- open server side pages that generate the browser content, this simplifies web developer’s debug, read server-faq
- open files listed in Javascript console. When editor open file the cursor can be moved to line number shown on javascript console, read js faq
For desperate cases you can add Microsoft IE to editor list.

Web Developer: Maybe the most succesfull of all, has great reviews. Adds a menu and a toolbar with various web developer tools.

These description are take from the Firefox add-ons site.

How to: WebDataGrid paging when there are more pages

QuickPages is a method of paging which will give links to a limited number of pages before and after the current page index.   Below is an example of the Paging behavior which is setup to display 3 quick pages along with a "First" and "Last" quick link.  This setup provides the best user experience for paged records which return more than 8 pages of data.

<ig:Paging PagerAppearance="Both" PagerMode="NumericFirstLast" 
    QuickPages="3" PageSize="20" 
    FirstPageText="First" LastPageText="Last" >
</ig:Paging>

Hope this helps!

FSFS vs BDB

FSFS and BDB are Subversion file system implementations. Traditionally Berkeley DB (BDB) was the standard file system used by Subversion. It solves many serious concerns with BDB such as data corruption and added improvements such as smaller space requirements. Now the FSFS is the standard, the default setting, and recommended by Subversion developers.

How FSFS is Better

• Write access not required for read operations
• Little or no need for recovery
• Smaller repositories
• Platform-independent
• Can host on network file system
• No unmask issues
• Standard backup software
• Can split up repository across multiple spools
• More easily understood repository layout
• Faster handling of directories with many files
• (Fine point) Fast "svn log -v" over big revisions
• (Marginal) Can give insert-only access to revs subdir for commits

How FSFS is Worse

• More server work for head checkout
• Finalization delay
• Lower commit throughput
• Immature code
• Big directories full of revision files
• (Developers) More difficult to index
  

SVN and SVN Repository

Subversion (SVN) is a very popular open source versioning system. It manages files, directories, and changes made to files and directories over time by single of multiple users

SVN is a client-server application where the SVN repository serves the tasks of a server. It is a central storage place which stores information in the form of a file system tree. Users share data by reading and writing to the repository. The repository keeps track of all changes written to the file i.e. modifications to the files, file contents, and directory structure. Users see the latest version of the file system by default but they can view every change ever make to the contents of the repository.

A decade ago Concurrent Versioning System (CVS) was the most-widely used versioning. It is built on Revision Control System (RCS) and thus inherits its flaws and this inheritance is precisely the reason it is very difficult to fix these flaws in CVS. SVN was created to overcome the flaws of CVS. It offers all the benefits of CVS without its flaws.

Although SVN is primarily used by programmer to track their project, it is capable of managing any sort of file collection. Important features of SVN are:

• users can store ongoing work (code, docs, data, etc.) in a central repository
• users can access the latest versions in the central repository
• automates the process of updating local working copy of the project with modifications made by others?
• users can track all changes ever made and revert to previous versions

Following are some important features which make SVN a better choice over CVS.

• Subversion versions entire trees i.e directories, renames, and file metadata
• changes are atomic. If you commit files a.aspx and b.aspx.cs, either both will be updated or neither will be updated
• tagging and branching are not resource intensive
• Subversion is designed as a client/server application