(svsv) Asp.net, C#, Sql server - code

Writing XPath Expressions

2009-10-01T03:21:00.001-07:00

http://www.stylusstudio.com/docs/v60/d_xpath.html

Writing XPath Expressions

2009-10-01T03:21:00.000-07:00

http://www.stylusstudio.com/docs/v60/d_xpath.html

TransactionScope

2009-09-23T05:53:00.000-07:00

http://www.c-sharpcorner.com/UploadFile/mosessaur/TransactionScope04142006103850AM/TransactionScope.aspx
http://www.codeproject.com/KB/dotnet/TransactionScope20.aspx

CLR Architecture

2009-09-23T05:31:00.000-07:00

http://www.codeproject.com/KB/dotnet/DotNetWhitePaper.aspx
http://www.codersource.net/basics_dot_net_framework.html

User Defined Functions in SqlServer

2009-09-22T01:07:00.000-07:00

http://www.sqlteam.com/article/user-defined-functions
http://www.java2s.com/Code/Oracle/Stored-Procedure-Function/Useauserdefinedfunctioninstoredprocedure.htm

Wcf

2009-09-22T00:58:00.000-07:00

http://www.codeproject.com/KB/aspnet/wcfinjavascript.aspx?display=Print
http://nayyeri.net/host-wcf-service-and-asp-net-application-on-same-virtual-directory
http://www.myitblog.com/sundararajan/programming-your-first-wcf-service.html

WCF

2009-09-21T23:30:00.001-07:00

WCF

2009-09-21T23:30:00.000-07:00

Shortcut keys of special characters in Html and key board

2009-09-18T13:21:00.000-07:00

Reference : http://home.earthlink.net/~awinkelried/keyboard_shortcuts.html

Tip sheet on special characters
On MacOS, the option key functions as a modifier key like the shift key. Hold it down and press another key simultaneously. For option - shift, hold down both the option and shift keys and press another key simultaneously.

On Windows, the Alt key functions as a modifier like the shift key. To make special characters, hold down the Alt key and type in the numbers from the numeric keypad.

(Note: I’m mentioning a useful little program because I use it at home on my Macintosh and a Windows machine and it helps you find a special character when you forget the key combination for it. Here’s how the author describes it:

If you don’t want to remember all these numbers, you should try the little shareware utility PopChar from ergonis software. One click, and PopChar displays a table of all characters of the current font. Select the desired character and it instantly appears in your document. You can also insert HTML symbols. PopChar is available for Mac OS 9, Mac OS X, and Windows.)

For more HTML number codes, see Character entity references in HTML 4.

HTML Name Code HTML Number Code Glyph MacOS Windows Description
‘ ‘ ‘ option - ] Alt + 0145 left single quote
’ ’ ’ option - shift - ] Alt + 0146 right single quote
‚ ‚ ‚ single low-9 quote
“ “ “ option - [ Alt + 0147 left double quote
” ” ” option - shift - [ Alt + 0148 right double quote
„ „ „ option - shift - w double low-9 quote
† † † option - t Alt + 0134 dagger
‡ ‡ ‡ option - shift - 7 Alt + 0135 double dagger
… … option - ; horizontal ellipsis
‰ ‰ ‰ option - shift - r Alt + 0137 per mill sign
‹ ‹ ‹ option - shift - 3 Alt + 0139 single left-pointing angle quote
› › › option - shift - 4 Alt + 0155 single right-pointing angle quote
♠ ♠ ♠ black spade suit
♣ ♣ ♣ black club suit
♥ ♥ ♥ black heart suit
♦ ♦ ♦ black diamond suit
‾ ‾ ‾ overline, = spacing overscore
← ← ← leftward arrow
↑ ↑ ↑ upward arrow
→ → → rightward arrow
↓ ↓ ↓ downward arrow
™ ™ ™ option - 2 Alt + 0153 trademark sign
" " " double quotation mark
& & & ampersand
< < < less-than sign
> > > greater-than sign
[ [ left square bracket
] ] right square bracket
– – – option - hyphen Alt + 0150 en dash
— — — option - shift -hyphen Alt + 0151 em dash
Alt + 0160 nonbreaking space
¡ ¡ ¡ option - 1 Alt + 0161 inverted exclamation
¢ ¢ ¢ option - 4 Alt + 0162 cent sign
£ £ £ option - 3 Alt + 0163 pound sterling
¤ ¤ ¤ Alt + 0164 general currency sign
¥ ¥ ¥ option - y Alt + 0165 yen sign
¦ or &brkbar; ¦ ¦ Alt + 0166 broken vertical bar
§ § § option - 6 Alt + 0167 section sign
¨ or ¨ ¨ ¨ option - shift - u Alt + 0168 umlaut
© © © option - g Alt + 0169 copyright
ª ª ª option - 9 Alt + 0170 feminine ordinal
« « « option - \ Alt + 0171 left angle quote
¬ ¬ ¬ option - l Alt + 0172 not sign
Alt + 0173 soft hyphen
® ® ® option - r Alt + 0174 registered trademark
¯ or &hibar; ¯ ¯ Alt + 0175 macron accent
° ° ° option - shift - 8 Alt + 0176 degree sign
± ± ± option - shift - = Alt + 0177 plus or minus
² ² ² Alt + 0178 superscript two
³ ³ ³ Alt + 0179 superscript three
´ ´ ´ option - shift - e Alt + 0180 acute accent
µ µ µ option - m Alt + 0181 micro sign
¶ ¶ ¶ option - 7 Alt + 0182 paragraph sign
· · · option - shift - 9 Alt + 0183 middle dot
¸ ¸ ¸ option - shift - z Alt + 0184 cedilla
¹ ¹ ¹ Alt + 0185 superscript one
º º º option - 0 Alt + 0186 masculine ordinal
» » » option - shift - \ Alt + 0187 right angle quote
¼ ¼ ¼ Alt + 0188 one-fourth
½ ½ ½ Alt + 0189 one-half
¾ ¾ ¾ Alt + 0190 three-fourths
¿ ¿ ¿ option - shift - ? Alt + 0191 inverted question mark
À À À option - ` A Alt + 0192 uppercase A, grave accent
Á Á Á option - e A Alt + 0193 uppercase A, acute accent
Â Â Â option - i A Alt + 0194 uppercase A, circumflex accent
Ã Ã Ã option - n A Alt + 0195 uppercase A, tilde
Ä Ä Ä option - u A Alt + 0196 uppercase A, umlaut
Å Å Å option - shift - a Alt + 0197 uppercase A, ring
Æ Æ Æ option - shift - ' Alt + 0198 uppercase AE
Ç Ç Ç option - shift - c Alt + 0199 uppercase C, cedilla
È È È option - ` E Alt + 0200 uppercase E, grave accent
É É É option - e E Alt + 0201 uppercase E, acute accent
Ê Ê Ê option - i E Alt + 0202 uppercase E, circumflex accent
Ë Ë Ë option - u E Alt + 0203 uppercase E, umlaut
Ì Ì Ì option - ` I Alt + 0204 uppercase I, grave accent
Í Í Í option - e I Alt + 0205 uppercase I, acute accent
Î Î Î option - i I Alt + 0206 uppercase I, circumflex accent
Ï Ï Ï option - u I Alt + 0207 uppercase I, umlaut
Ð Ð Ð Alt + 0208 uppercase Eth, Icelandic
Ñ Ñ Ñ option - n N Alt + 0209 uppercase N, tilde
Ò Ò Ò option - ` O Alt + 0210 uppercase O, grave accent
Ó Ó Ó option - e O Alt + 0211 uppercase O, acute accent
Ô Ô Ô option - i O Alt + 0212 uppercase O, circumflex accent
Õ Õ Õ option - n O Alt + 0213 uppercase O, tilde
Ö Ö Ö option - u O Alt + 0214 uppercase O, umlaut
× × × Alt + 0215 multiplication sign
Ø Ø Ø option - shift - o Alt + 0216 uppercase O, slash
Ù Ù Ù option - ` U Alt + 0217 uppercase U, grave accent
Ú Ú Ú option - e U Alt + 0218 uppercase U, acute accent
Û Û Û option - i U Alt + 0219 uppercase U, circumflex accent
Ü Ü Ü option - u U Alt + 0220 uppercase U, umlaut
Ý Ý Ý Alt + 0221 uppercase Y, acute accent
Þ Þ Þ Alt + 0222 uppercase THORN, Icelandic
ß ß ß option - s Alt + 0223 lowercase sharps, German
à à à option - ` a Alt + 0224 lowercase a, grave accent
á á á option - e a Alt + 0225 lowercase a, acute accent
â â â option - i a Alt + 0226 lowercase a, circumflex accent
ã ã ã option - n a Alt + 0227 lowercase a, tilde
ä ä ä option - u a Alt + 0228 lowercase a, umlaut
å å å option - a Alt + 0229 lowercase a, ring
æ æ æ option - ' Alt + 0230 lowercase ae
ç ç ç option - c Alt + 0231 lowercase c, cedilla
è è è option - ` e Alt + 0232 lowercase e, grave accent
é é é option - e e Alt + 0233 lowercase e, acute accent
ê ê ê option - i e Alt + 0234 lowercase e, circumflex accent
ë ë ë option - u e Alt + 0235 lowercase e, umlaut
ì ì ì option - ` i Alt + 0236 lowercase i, grave accent
í í í option - e i Alt + 0237 lowercase i, acute accent
î î î option - i i Alt + 0238 lowercase i, circumflex accent
ï ï ï option - u i Alt + 0239 lowercase i, umlaut
ð ð ð Alt + 0240 lowercase eth, Icelandic
ñ ñ ñ option - n n Alt + 0241 lowercase n, tilde
ò ò ò option - ` o Alt + 0242 lowercase o, grave accent
ó ó ó option - e o Alt + 0243 lowercase o, acute accent
ô ô ô option - i o Alt + 0244 lowercase o, circumflex accent
õ õ õ option - n o Alt + 0245 lowercase o, tilde
ö ö ö option - u o Alt + 0246 lowercase o, umlaut
÷ ÷ ÷ Alt + 0247 division sign
ø ø ø option - o Alt + 0248 lowercase o, slash
ù ù ù option - ` u Alt + 0249 lowercase u, grave accent
ú ú ú option - e u Alt + 0250 lowercase u, acute accent
û û û option - i u Alt + 0251 lowercase u, circumflex accent
ü ü ü option - u u Alt + 0252 lowercase u, umlaut
ý ý ý Alt + 0253 lowercase y, acute accent
þ þ þ Alt + 0254 lowercase thorn, Icelandic
ÿ ÿ ÿ option - u y Alt + 0255 lowercase y, umlaut

reference :
http://home.earthlink.net/~awinkelried/keyboard_shortcuts.html

Articles on WCF

2009-09-06T02:18:00.000-07:00

Great Tutorials on WCF -

http://aspalliance.com/articles/learnwcf.aspx

and

http://msdn.microsoft.com/hi-in/magazine/cc163647(en-us).aspx

If you share the same zeal,come, Join the leader

walk in with a hard copy of your resume along with a passport size photograph on"

12th september 2009( saturday ) or 13th september 2009 ( sunday)

Timing : 1.00pm to 3.00pm

Skill Requirement:

ïƒ¼MS technologies: VB 6.0, VB.NET, VBA/MS Access
ïƒ¼Java Technologies: J2EE, Core Java, JMS
ïƒ¼PHP- Frontend development with PHP scripting
ïƒ¼C++ - Knowledge on corresponding language features,
ïƒ¼STL, Pointers
ïƒ¼Scripting: UNIX shell scripting, Perl scripting
ïƒ¼Oracle: oracle Database Concepts, PL/SQL,
ïƒ¼Performance tuning preferably in UNIX environment
ïƒ¼Sybase- Sybase Database Concepts, Queries,
Performance Tuning
ïƒ¼SQL Server- SQL database concepts, SQL queries DTS
ïƒ¼Datawarehouse / Bi Technologies â€“Data stage / MSBI / Cognos /
SAS / Hyperion / Crystal Reports

Walk in Venue :
HCL Technologies Limited
Special Economic Zone, L & T Phoenix Info Park Pvt. Ltd.
Building: H-08: Level â€“ 2 & 3 HITEC CITY 2 â€“ Survey No. 30, 34, 35, & 38
(Behind DELL), Hyderabad-500081. Tel: 040 6698 1000

IIS

2009-09-05T02:36:00.000-07:00

http://aspnet.4guysfromrolla.com/articles/011404-1.aspx

Installing procedure and system requirements for moss 2007

2009-08-31T22:27:00.000-07:00

Deployment for 2007 Microsoft Office

SharePoint Server

A server farm typically consists of one or two back-end database servers and one
or more front-end servers that provide Web services and Office SharePoint Server
2007 services, such as search, Excel Services, and indexing.

Hardware and software requirements

Before you install and configure Office SharePoint Server 2007, make sure your
servers have the recommended hardware and software. To deploy a server farm, you
need at least one server computer acting as a Web server and an application
server, and one server computer acting as a database server. The server
computers must meet the following requirements:

Hardware requirements

Front-end Web server and application server computers: a dual-processor computer
with processor clock speeds of 2.5-gigahertz (GHz) or higher and a minimum of 2
gigabytes (GB) of RAM.

Back-end database server: a dual-processor computer with processor clock speeds
of 2.0 GHz or higher and a minimum of 2 GB of RAM.

Software requirements Web and Application Server

Microsoft Windows Server 2003 (Standard, Enterprise, Datacenter, or Web Edition)
with Service Pack 1 (SP1)

Microsoft .Net Framework 2.0

Microsoft .Net Framework 3.0

The Web server and application server computers must be configured as Web
servers running Microsoft Internet Information Services (IIS) in IIS 6.0 worker
process isolation mode.

Each of the computers must be using the NTFS file system. Windows Server 2003
includes a conversion utility (Convert.exe) that you can use to convert an
existing file allocation table (FAT) volume to NTFS without losing data.

Back-End Database Server

The back-end database server computer must be running Microsoft SQL Server 2005
or Microsoft SQL Server 2000 with Service Pack 3 (SP3) or later. It is assumed
that you have installed and configured the database program on the back-end
server computer. You do not need to set up or create specific databases for
Office SharePoint Server 2007. The Office SharePoint Server 2007 Setup program
will create the necessary databases when you install and configure Office
SharePoint Server 2007.

In addition to these requirements, if you are using SQL Server 2005, you need to
configure surface area settings. Use the following procedure to do this.

Configure surface area settings in SQL Server 2005

Click Start, point to All Programs, point to
Microsoft SQL Server 2005, point to Configuration Tools,
and then click SQL Server Surface Area Configuration.

In the SQL Server Surface Area Configuration dialog box, click
Surface Area Configuration for Services and Connections.

In the tree, open your instance of SQL Server, open Database Engine,
and then click Remote Connections.

Click Local and Remote Connections, click Using both
TCP/IP and named pipes, and then click OK.

Security account requirements

To install Office SharePoint Server 2007 in a server farm environment, at-least
2 accounts are required:

A user account that you can use to install Office SharePoint Server 2007 and run
the SharePoint Products and Technologies Configuration Wizard. This account must
be:

A domain user account.

A member of the Administrators group on each of your front-end servers.

A member of the SQL Server Logins, which grants login access to your SQL Server
instance.

A member of the SQL Server Database Creator server role, which grants permission
to create and alter databases.

A member of the SQL Server Security Administrators server role, which grants
permission to manage server logins.

src="http://www.datasprings.com/Portals/0/MOSS_2007_Deployment_files/image002.jpg" />

A unique domain user account that you can specify as the Office SharePoint
Server 2007 service account. This user account is used to access your SharePoint
configuration database. It also acts as the application pool identity for the
SharePoint Central Administration application pool and it is the account under
which the Windows SharePoint Services Timer service runs. The SharePoint
Products and Technologies Configuration Wizard adds this account to the SQL
Server Logins, the SQL Server Database Creator server role, and the SQL Server
Security Administrators server role. It is recommended that you follow the
principle of least privilege and do not make this user account a member of any
particular security group on your front-end servers or your back-end servers.

Configure the server as a Web server

Before you install and configure Office SharePoint Server 2007, you must install
and configure the required software on each of your front-end servers. This
includes installing and configuring IIS so your front-end servers act as Web
servers, installing Windows .NET Framework 2.0, enabling ASP.NET 2.0, and
installing Windows Workflow Foundation Runtime Components Beta 2.2 (build
3807.7).

Install and configure IIS

IIS is not installed or enabled by default in Windows Server 2003. To make your
server a Web server, you must install and enable IIS, and you must make sure
that IIS is running in IIS 6.0 worker process isolation mode.

Click Start, point to All Programs, point to
Administrative Tools, and then click Configure Your
Server Wizard.

On the Welcome to the Configure Your Server Wizard page, click Next.

On the Preliminary Steps page, click Next.

On the Server Role page, click Application server (IIS, ASP.NET),
and then click Next.

On the Application Server Options page, click Next.

On the Summary of Selections page, click Next.

Click Finish.

Click Start, point to All Programs, point to
Administrative Tools, and then click Internet
Information Services (IIS) Manager.

In the IIS Manager tree, click the plus sign ( ) next to the server name, and
then right-click the Web Sites folder and select
Properties.

In the Web Sites Properties dialog box, click the
Service tab.

In the Isolation mode section, clear the Run WWW
service in IIS 5.0 isolation mode check box, and then click OK.

Note: The Run WWW in IIS 5.0 isolation mode
check box is only selected if you have upgraded to IIS 6.0 on Windows Server
2003 from IIS 5.0 on Microsoft Windows 2000. New installations of IIS 6.0 use
IIS 6.0 worker process isolation mode by default.

Install Windows .NET Framework 2.0

Run .Net Framework 2.0 Setup

Enable ASP.NET 2.0

Click Start, point to All Programs, point to
Administrative Tools, and then click Internet
Information Services (IIS) Manager.

In the IIS Manager tree, click the plus sign ( ) next to the server name, and
then click the Web Service Extensions folder.

In the details pane, click ASP.NET v2.0.50727, and then click
Allow.

Install .Net Framework 3.0

1. Run .Net Framework 3.0 Setup

Install Microsoft Windows Workflow Foundation Runtime.
Install and configure 2007 Office SharePoint Server

It is recommended that you install and configure Office SharePoint Server 2007
on all of your front-end servers before you configure Office SharePoint Server
2007 services and create sites. If you want to build a minimal server farm
configuration, and incrementally add front-end servers to expand the farm, you
can install and configure Office SharePoint Server 2007 on a single front-end
server and configure the front-end server as both a Web server and an
application server. Regardless how many front-end servers you have in your
server farm, you must have SQL Server running on at least one back-end database
server before you install Office SharePoint Server 2007 on your front-end
servers.

Run 2007 Office SharePoint Server Setup

Run Officeserver.exe, on one of your Web server computers.

On the Enter your Product Key page, enter your product key and click
Continue.

src="http://www.datasprings.com/Portals/0/MOSS_2007_Deployment_files/image004.jpg" />

On the Read the Microsoft Software License Terms page, review the terms, select
the I accept the terms of this agreement check box, and then
click Continue.

src="http://www.datasprings.com/Portals/0/MOSS_2007_Deployment_files/image005.jpg" />

On the Choose the installation you want page, click Advanced.

src="http://www.datasprings.com/Portals/0/MOSS_2007_Deployment_files/image008.jpg" />

On the Server Type tab, do one of the following:

If you are setting up a computer that will act as an application server, or a
Web server and an application server, click Complete, and then
click Install Now.

If you are setting up a computer that will act as a Web server only, click
Web Front End, and then click Install Now.

src="http://www.datasprings.com/Portals/0/MOSS_2007_Deployment_files/image009.jpg" />

When Setup finishes, a dialog box appears telling you that you must complete the
configuration of your server. Make sure that the Run the SharePoint
Products and Technologies Configuration Wizard now check box is
selected.

Click Close to start the configuration wizard. Instructions for
completing the wizard are provided in the next set of steps.

Run the SharePoint Products and Technologies Configuration
Wizard

After Setup finishes, you can use the SharePoint Products and Technologies
Configuration Wizard to configure Office SharePoint Server 2007. The SharePoint
Products and Technologies Configuration Wizard automates several configuration
tasks, including: installing and configuring the configuration database,
installing Office SharePoint Server 2007 services, and installing SharePoint
Central Administration. Use the following instructions to run the SharePoint
Products and Technologies Configuration Wizard.

On the Welcome to SharePoint Products and Technologies page, click Next.

src="http://www.datasprings.com/Portals/0/MOSS_2007_Deployment_files/image012.jpg" />

Click Yes in the warning dialog box that appears notifying you
that some services might need to be restarted during configuration.

On the Connect to a server farm page, do one of the following:

If this is the first front-end server that you are configuring in your server
farm, click No, I want to create a new server farm, and then
click Next.

If you have already configured your first server in your server farm, click
Yes, I want to connect to an existing server farm, and then
click Next.

src="http://www.datasprings.com/Portals/0/MOSS_2007_Deployment_files/image014.jpg" />

On the Specify Configuration Database Settings dialog box, in
Database server, type the name of the computer that is running
SQL Server.

Do one of the following:

If this is the first server that you are configuring in your server farm, type a
name for your configuration database in Database name, or use
the default database name.

If you have already configured the first server in your server farm, click
Retrieve Database Names, and in Database name
click the database name that you created when you configured the first server in
your server farm. The default name is SharePoint_Config.

src="http://www.datasprings.com/Portals/0/MOSS_2007_Deployment_files/image016.jpg" />

In User name , type the user name of the account used to
connect to the computer running SQL Server (be sure to type the user name in the
format DOMAIN\username).

Important: This account is the Office SharePoint Server 2007
service account under which several Office SharePoint Server 2007 services run.
The user account that you specify as the Office SharePoint Server 2007 service
account must be a domain user account, but it does not need to be a member of
any specific security group on your front-end servers or your back-end database
servers. However, the user account that you specify must be a member of the
following two SQL Server security roles on your back-end database servers:
Database Creator and Security Administrator. It is recommended that you follow
the principle of least privilege and specify a user account that is not a member
of the Administrators group as your Office SharePoint Server 2007 service
account.

In Password, type the user's password, and click Next.

Skip the next step if you have already configured first server in your server
farm.

On the Configure SharePoint Central Administration Web Application page, select
the Specify port number check box and type a port number if you
want the SharePoint Central Administration Web application to use a specific
port, or leave the Specify port number check box unchecked if
you do not care which port number the SharePoint Central Administration Web
application uses.
src="http://www.datasprings.com/Portals/0/MOSS_2007_Deployment_files/image018.jpg" />

On the Configure SharePoint Central Administration Web Application
dialog box, select NTLM authentication (the default), click Next.

On the Completing the SharePoint Products and Technologies Wizard page, click
Next.

On the Configuration Successful page, click Finish.

The SharePoint Central Administration Web page opens.

Notes

If you are prompted for your user name and password, you might need to add the
SharePoint Central Administration site to the list of trusted sites and
configure user authentication settings in Internet Explorer. Instructions for
configuring these settings are provided in the next set of steps.

If you see a proxy server error message, you might need to configure your proxy
server settings so that local addresses bypass the proxy server. Instructions
for configuring this setting are provided later in this section.

Add the SharePoint Central Administration site to the list
of trusted sites

In Internet Explorer, on the Tools menu, click Internet
Options.

On the Security tab, in the Select a Web content zone
to specify its security settings box, click Trusted Sites,
and then click Sites.

Clear the Require server verification (https:) for all sites in this
zone check box.

In the Add this Web site to the zone box, type the URL for the
SharePoint Central Administration site, and then click Add.

Select the Require server verification (https:) for all sites in this
zone check box.

Click Close to close the Trusted Sites dialog
box.

Click OK to close the Internet Options dialog
box.

Configure user authentication settings for trusted sites

In Internet Explorer, on the Tools menu, click Internet
Options.

On the Security tab, in the Select a Web content zone
to specify its security settings box, click Trusted sites,
and then click Custom Level.

In the Settings list box, under User Authentication,
click Automatic logon with current username and password.

Click OK twice.

Note: If you do not want to add the SharePoint Central
Administration site to the list of trusted sites, but you do not want to be
prompted for your user name and password every time you access the SharePoint
Central Administration site, you can instead add the SharePoint Central
Administration site to the Local intranet zone. If you do this, you must enable
the Automatic logon only in Intranet zone user authentication setting instead of
the Automatic logon with current username and password user authentication
setting

Configure 2007 Office SharePoint Server
services

After you have installed and configured Office SharePoint Server 2007 on all of
your front-end servers, you must configure Office SharePoint Server 2007
services. The services you need to configure depends on your server topology and
the server roles you deploy. Use the following guidelines to determine which
services you need to configure in your server farm.

Search and indexing servers You must start and configure the
Office SharePoint Server Search service on at least one of your front-end
servers. This service provides search and indexing services. You can start and
configure this service on any type of server, including a server that is acting
as an application server and provides only Office SharePoint Server 2007
services, a server that is acting as both an application server and a Web server
and provides both Office SharePoint Server 2007 services and Web services, or a
server that is acting as a Web server and provides only Web services.

Web servers The Web server role is implemented by IIS and the
Windows SharePoint Services Web Application service. The Windows SharePoint
Services Web Application service must be running on any server that acts as a
Web server and renders Web content. This service is started by default on
servers that you set up using the Web Front End option during
Setup. If you set up a server using the Complete option during
Setup, and you want that server to act as a Web server and render Web content,
then you must start the Windows SharePoint Services Web Application service on
that server.

src="http://www.datasprings.com/Portals/0/MOSS_2007_Deployment_files/image020.jpg" />

src="http://www.datasprings.com/Portals/0/MOSS_2007_Deployment_files/image022.jpg" />

In addition to configuring services on your front-end servers, you must create
the Shared Services Provider (SSP). The SSP makes it possible to share the
Office SharePoint Server 2007 services across your server farm. You must create
the SSP before you can use it in a farm environment; Office SharePoint Server
2007 does not create the SSP by default in a farm environment.

The following procedures step you through the process of configuring Office
SharePoint Server 2007 services, creating a Web application for the SSP,
creating the SSP, and configuring indexing settings.

Start and configure the Search service

On the SharePoint Central Administration home page, click the Operations
tab on the top navigation bar.

On the Operations page, in Topology and Services, click
Servers in farm.

On the Servers in Farm page, click the server on which you want to configure the
search service.

Click Start next to Office SharePoint Server Search.

On the Office SharePoint Server Search Settings page, in the Query and
Indexing section, make sure that the Use this server for
indexing content and Use this server for serving search queries
check boxes are selected.

In the Default Catalog Location section, type a path to a
physical folder to store the index files, or use the default location that is
specified.

In the Contact E-Mail Address section, specify a valid e-mail
address.

In the Service Account section, click Configurable, and in
User name and Password, type the user name and
password for the user account under which you want the Search service to run.
The user account must be a member of the Administrators group on the computer
that is running the Search service. If you want to use the principle of least
privilege and select a unique user account that does not have administrative
rights on your front-end servers or on your back-end database servers, see the
Known Issues/Readme for Office SharePoint Server 2007 Beta 2. The user name must
be in the format DOMAIN\username.

In the Web Front End And Crawling section, do one of the
following:

If you are configuring the search service on a server that provides Web services
and renders Web content, click No dedicated Web front-end computer for
crawling

If you are configuring the search service on a server that is a standalone
search server that does not provide Web services and render Web content, click
Use a dedicated web front end computer for crawling, and then,
in Select a web front end computer, click the computer you want
to use for crawling.

Click Start.

Start the Windows SharePoint Services Web Application
service

You must start the Windows SharePoint Services Web Application service on every
computer that you want to act as a Web server and was set up using the
Complete option during Setup. This service is started by default on
servers that were set up using the Web Front End option. To
enhance security, you can leave this service turned off on application servers
that do not provide Web content to client computers. Also, you do not need to
turn this service on to use SharePoint Central Administration on a server.

On the SharePoint Central Administration home page, click the Operations
tab on the top navigation bar.

On the Operations page, in Topology and Services, click
Servers in farm.

On the Servers in Farm page, click the server on which you want to start the
Windows SharePoint Services Web Application service.

Click Start next to Window SharePoint Services Web
Application.

Create the Shared Services Provider

On the SharePoint Central Administration home page, click the
Application Management tab on the top navigation bar.

On the Application Management page, in the Office SharePoint Server
Shared Services section, click Create or configure this farm's
shared services.

On the Manage this Farm's Shared Services page, click New SSP.

Important: If you have not created a Web application for the
SSP administration site, you need to create one before you create the SSP. If
you have already created a Web application for the SSP administration site, skip
to step 14.

On the New Shared Services Provider page, click Create a new Web
application.

On the Create New Web Application page, in the IIS Web Site
section, click Create a new IIS web site, and do not modify the
default settings in this section.

In the Security Configuration section, under
Authentication provider, select the appropriate option for your
environment, and do not modify the default settings in the remainder of this
section.

In the Load Balanced URL section, do not modify the default
settings.

In the Application Pool section, click Create new
application pool.

In Application pool name, enter the name of your application
pool or use the default name.

Click Configurable, and in User name and
Password, type the user name and password for the user account
under which you want the application pool to run. The user account does not have
to be a member of any particular security group. It is recommended that you use
the principle of least privilege and select a unique user account that does not
have administrative rights on your front-end servers or on your back-end
database servers. You can use the user account that you specified as the Office
SharePoint Server 2007 service account; however, if that user account is a
member of a security group that has administrative rights on your front-end
servers or your back-end database servers, you will not be following the
principle of least privilege. The user name must be in the format
DOMAIN\username.

In the Database Name and Authentication section, verify the
database information and make sure that Windows Authentication
(recommended)is selected.

In the Search Server section, do not modify the default
settings.

Click OK. Upon successful creation of the Web application, the
New Shared Services Provider page appears.

In the SSP Name section, in Web Application,
select the Web application that you created for the SSP, and do not modify any
of the default settings in this section.

In the My Site Location section, do not modify any of the
default settings.

In the SSP Service Credentials section, in User name
and Password, type the user name and password for the user
account under which you want the SSP to run. The user account does not have to
be a member of any particular security group. It is recommended that you use the
principle of least privilege and select a unique user account that does not have
administrative rights on your front-end servers or on your back-end database
servers. You can use the user account that you specified as the Office
SharePoint Server 2007 service account; however, if that user account is a
member of a security group that has administrative rights on your front-end
servers or your back-end database servers, you will not be following the
principle of least privilege. The user name must be in the format
DOMAIN\username.

In the SSP Database section, you can either accept the default
settings (recommended), or specify your own settings for the database server,
the database name, or the SQL authentication credentials.

In the Search Database section, you can either accept the
default settings (recommended), or specify your own settings for the search
database server, the database name, or the SQL Server authentication
credentials.

In the Index Server section, in Index Server,
click the server on which you configured the Search service.

Note: If there is no index server listed in the Index
Server section, then no server in your farm has been assigned the index
server role. To assign the index server role to a server in your farm, follow
the instructions in the "Configure the Search service" section earlier in this
topic.

In the SSL for Web Services section, click No.

Click OK. Upon successful creation of the SSP, the Success page
appears.

On the Success page, click OK to return to the Manage this
Farm's Core Services page.

Configure indexing settings

On the SharePoint Central Administration home page, click the
Application Management tab on the navigation bar.

On the Application Management page, in the Office SharePoint Server
Shared Services section, click Create or configure this farm's
shared services.

On the Manage this Farm's Shared Services page, click SharedServices1.

On the Shared Services Administration page, in Search, click
Search Settings.

On the Configure Search Settings page, in the Crawl Settings
section, click Default content access account.

In the Default content access account section, in Account,
Password, and Confirm Password, type the user
name and password for the user account that you want to use to crawl content on
your sites. This account must be a domain user account. It is recommended that
you use the principle of least privilege and select a unique user account that
cannot modify content and does not have administrative rights on your front-end
servers or on your back-end database servers. You can use the user account that
you specified as the Office SharePoint Server 2007 service account; however, if
that user account is a member of a security group that has administrative rights
on your front-end servers or your back-end database servers, you will not be
following the principle of least privilege. The user account that you specify
will be added to the Web application Full Read policy for your farm. The user
name must be in the format DOMAIN\username.

Click OK.

In the Crawl Settings section, click Content sources.

On the Manage Content Sources page, click Local Office SharePoint Server
sites.

On the Edit Content Source page, in the Crawl Schedules
section, under Full Crawl, click Create schedule.

In the Manage Schedules dialog box, configure schedule settings
for full crawls of your content, and then click OK.

In the Crawl Schedules section, under Incremental Crawl,
click Create schedule.

In the Manage Schedules dialog box, configure schedule settings
for incremental crawls of your content, and then click OK.

In the Start Full Crawl section, select the Start full
crawl of this content source check box, and then click OK.

Create and configure a site

After you configure services in your server farm, you can create a Web
application and a site collection. You should create the Web application on the
first server on which you installed Office SharePoint Server 2007 (in other
words, the same server that is running the SharePoint Central Administration
service).

Create a Web application for your SharePoint site

On the SharePoint Central Administration home page, click the
Application Management tab on the top navigation bar.

In the SharePoint Web Application Management section, click
Create or extend Web application.

On the Create or Extend Web Application page, click Create a new Web
Application.

On the Create New Web Application page, in the IIS Web Site
section, click Create a new IIS web site, and change the port
setting to port 80. This will allow you to access your site by typing http://ServerName.
If you use a nonstandard port number you will have to include the port number in
the URL to access your site (for example, http://ServerName:port).

In the Security Configuration section, under
Authentication provider, select the appropriate option for your
environment, and do not modify any other settings in this section.

Note: By default, the authentication provider is set to
NTLM.

In the Load Balanced URL section, do not modify the default
settings.

In the Application Pool section, select Create new
application pool, and use the default settings for the application pool
name.

Click Configurable, and in User name and
Password, type the user name and password for the user account
under which you want the application pool to run. The user account does not have
to be a member of any particular security group. It is recommended that you use
the principle of least privilege and select a unique user account that does not
have administrative rights on your front-end servers or on your back-end
database servers. You can use the user account that you specified as the Office
SharePoint Server 2007 service account; however, if that user account is a
member of a security group that has administrative rights on your front-end
servers or your back-end database servers, you will not be following the
principle of least privilege. The user name must be in the format
DOMAIN\username.

In the Database Name and Authentication section, verify the
database information and ensure Windows Authentication (recommended)is
selected.

In the Search Server section, do not modify the default
settings.

Click OK.

On the Application Created page, which appears after successful creation of the
Web application, click Create a new Windows SharePoint Services site
collection.

Create the site collection for your Web application

On the Create Site Collection page, in the Title and Description
section, in Title, enter a title for the new site.

In Description, enter a description of the site collection.

In the Web Site Address section, click Create site at
this URL, and in URL path click (root).

It is most common to create a site collection at the root; however, you can
create a site collection at a specific URL path.

In the Primary Site Collection Administrator section, in
User name, type the user name of the site collection
administrator. This can be the same user account that you specified as the
Office SharePoint Server 2007 service account, but you should follow the
principle of least privilege and use a user account that does not have
administrative privileges or rights on your front-end or back-end servers.

In the Quota Template section, select a predefined quota
template to limit resources used for this site collection.

Note: You can also select No Quota, thereby
allowing this site collection to use any available resources.

In the Template Selection section, click the Publishing
tab, and then click Corporate Intranet Site.

Click OK to create the site collection with the attributes you
specified. Upon successful completion, a Top-Level Site Successfully Created
page appears.

Click OK to return to the SharePoint Central Administration
home page, or click the http://ComputerName link to go to your new
SharePoint site home page.

After you install and configure Office
SharePoint Server 2007

After you finish creating your first site, you can start adding content to the
site and you can start customizing the site. However, it is recommended that you
first configure several administrative settings to ensure that your Office
SharePoint Server 2007 environment is operating properly and you are using all
of the features and capabilities provided by Office SharePoint Server 2007.

Install and configure Excel Calculation Services

To take full advantage of the business intelligence capabilities of
Office SharePoint Server 2007 you need to start and configure Excel Calculation
Services. Instructions for doing this are provided below.

Note: Excel Services is only available if you use a product key
that activates the Enterprise version of Office SharePoint Server 2007.

Start and configure Excel Calculation Services

On the SharePoint Central Administration home page, click Administrative
Tasks.

On the Administrative Tasks page, click Add Excel Services Trusted
Locations.

On the Add Excel Services Trusted Locations page, in Action,
click Add Excel Services Trusted Locations.

On the Excel Services Trusted File Locations page, click Add Trusted
File Location.

In the Location section, in Address, type the
address of the trusted file location. It is recommended that the trusted file
location be an Office SharePoint Server 2007 site, but you can also specify
universal naming convention (UNC) paths or HTTP Web sites.

In Location Type, click Windows SharePoint Services
if you specified an Office SharePoint Server 2007 site, click UNC
if you specified a UNC path, or click HTTP if you specified an
HTTP Web site.

In the External Data section, in Allow External Data,
select the trust level for external data sources that you want to enable by
doing one of the following:

Click None to prevent Excel Calculation Services from
processing connections to any external data connection.

Click Trusted data connection libraries only to prevent Excel
Calculation Services from processing connections to external data sources that
are embedded within workbooks. This setting permits Excel Calculation Services
to process links to trusted data connection libraries.

Click Trusted data connection libraries and embedded to permit
Excel Calculation Services to process direct connections to external data
sources that are embedded within workbooks. This setting also permits Excel
Calculation Services to process links to trusted data connection libraries.

Configure alternate access mappings for your Web
applications

If you installed and configured Office SharePoint Server 2007 on a single
front-end server, and a user browses to your server, the server will render the
content that is in your Web application. However, if you added subsequent
front-end servers to your server farm, the newly-added servers will not have
alternate access mappings configured to your Web application. To map newly-added
front-end servers to your existing Web application, you need to configure
alternate access mappings.

Before you configure alternate access mappings, install and configure Office
SharePoint Server 2007 on all of the front-end servers that you want to add to
your server farm, and make sure that the servers are joined to your server farm.
See "Run Windows SharePoint Services Setup" and "Run the SharePoint Products and
Technologies Configuration Wizard" for information about installing and
configuring Office SharePoint Server 2007.

To configure alternate access mappings

On the SharePoint Central Administration home page, click the Operations
tab.

On the Operations page, in the Global Configuration section,
click Alternate access mappings.

In Alternate Access Mapping Collection, click Change
Alternate Access Mapping Collection.

In the Select an Alternate Access Mapping Collection dialog box, click the Web
application that you want to modify. If you have created only one Web
application, and you specified port 80 for the Web application, the Web
application should be listed as SharePoint (80).

Click Edit Outbound URLs, and verify that your Web application is listed in the
Default zone for outbound URLs. The outbound URL is the URL that you want users
to use to access your Web application.

Note: If you have a load-balanced configuration with a host
name, add the host name to the Outbound URL for the Default zone.

Click Save.

Click Add Incoming URLs.

On the Add Incoming URLs page, in New default zone URL protocol, host
and port type the URL for the server that you want to map to your Web
application. Typically, this is http://servername:portnumber.

Note: If you have a load-balanced configuration, you should add
the server name of each of your front-end Web servers to the list of internal
URLs. This will allow each of your Web servers to reach the content in your
common Web application. Also, make sure the zone you selected for the incoming
URL matches the zone of the outbound URL for the load balancer. You can have
multiple incoming URLs associated with a single outbound URL.

In Zone, make sure that Default is selected.

Click Save.

Configure additional administrative settings

After you have deployed the SharePoint Server, there are some other additional
settings which you need to configure. You should perform these tasks to take
full advantage of the SharePoint 2007 administrative Features:

Email Settings:
- Incoming:

Configuring server for incoming emails will enable you to get advantage of the
following SPS 2007 features:

1. SharePoint sites can accept and archive incoming e-mail.

2. SharePoint sites can archive e-mail discussions as they happen, save e-mailed
documents, and show e-mailed meetings on site calendars.

3. In addition, configure the SharePoint Directory Management Service for e-mail
distribution list creation and management.

Outgoing

Configure Outgoing SMTP Email server to enable SPS 2007 for sending
Notifications and alerts to the site users and administrators. You can configure
“From” and “Reply to” email addresses for outgoing emails.

Create SharePoint sites: Create more SharePoint sites and Web
applications if your site design requires multiple sites or multiple Web
applications.

Diagnostic logging settingsTo get yourself helped in
troubleshooting, configure various logging and diagnostics settings including
trace logs, event messages, user-mode error messages, and Customer Experience
Improvement Program events.

Configure antivirus protection settingsConfigure Antivirus
Settings for Server to enable the virus scanning for document upload and
downloads, also configure virus scanning timeout and execution threads on the
server for antivirus. A SharePoint Server 2007 compatible Antivirus program is
required for this.

You can use the following procedure to configure optional administrative
settings using SharePoint Central Administration.

Configure administrative settings using SharePoint Central
Administration

Click Start, point to All Programs, point to
Administrative Tools, and then click SharePoint 3.0
Central Administration.

On the SharePoint Central Administration home page, under Administrative
Tasks, click the administrative task you want to perform.

On the Administrative Tasks page, next to Action, click the
task.

reference : http://www.datasprings.com/Resources/ArticlesInformation/OverviewonInstallingSharepoint2007/tabid/774/language/en-US/Default.aspx

Merrit Scholarships

2009-08-31T06:15:00.000-07:00

Merit Scholarship for Ap Students

WindowsCommunicationFoundation.

2009-08-30T08:02:00.000-07:00

Below is link for small sample on WindowsCommunicationFoundation.
http://www.codeproject.com/KB/WCF/wcf_bohansen.aspx: windowdcommunicationfoundation

MVC Architecture

2009-08-29T02:07:00.000-07:00

The main aim of the MVC architecture is to separate the
business logic and application data from the presentation
data to the user.

Here are the reasons why we should use the MVC design pattern.

1. They are resuable : When the problems recurs, there is
no need to invent a new solution, we just have to follow the
pattern and adapt it as necessary.
2. They are expressive: By using the MVC design pattern
our application becomes more expressive.

1). Model: The model object knows about all the data that
need to be displayed. It is model who is aware about all the
operations that can be applied to transform that object. It
only represents the data of an application. The model
represents enterprise data and the business rules that
govern access to and updates of this data. Model is not
aware about the presentation data and how that data will be
displayed to the browser.

2). View : The view represents the presentation of the
application. The view object refers to the model. It uses
the query methods of the model to obtain the contents and
renders it. The view is not dependent on the application
logic. It remains same if there is any modification in the
business logic. In other words, we can say that it is the
responsibility of the of the view's to maintain the
consistency in its presentation when the model changes.

3). Controller: Whenever the user sends a request for
something then it always go through the controller. The
controller is responsible for intercepting the requests from
view and passes it to the model for the appropriate action.
After the action has been taken on the data, the controller
is responsible for directing the appropriate view to the
user. In GUIs, the views and the controllers often work
very closely together.

OverLoading in Webservice

2009-08-27T22:58:00.001-07:00

using System;
using System.Web;
using System.Web.Services;
using System.Web.Services.Protocols;

[WebService(Namespace = "http://tempuri.org/")]
[WebServiceBinding(ConformsTo = WsiProfiles.None)]
public class Service : System.Web.Services.WebService
{
public Service ()
{
}
[WebMethod(MessageName = "One param", Description = "str Value", EnableSession = true)]
public string Method( string str)
{
return "Hello World";
}
[WebMethod(MessageName = "two param", Description = "two str values", EnableSession = true)]
public string Method(string str,string str1)
{
return "Hi";
}

}

Dynamic Controls

2009-08-27T03:03:00.001-07:00

using System;
using System.Data;
using System.Configuration;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using System.Collections.Generic;

public partial class _Default : System.Web.UI.Page
{
protected void Page_Load(object sender, EventArgs e)
{
if (Page.IsPostBack != true)
{
List temp1 = new List();
ViewState["allData"] = temp1;

}
if (ViewState["allData"] != null)
{
List values = (List)ViewState["allData"];
foreach (string strdata in values)
{
TableRow row = new TableRow();
TableCell cell = new TableCell();
TextBox text = new TextBox();
text.Width = 200;
text.Text = strdata;
cell.Controls.Add(text);// = strdata.Split(',')[1];
row.Cells.Add(cell);
Table1.Rows.Add(row);
}
}

}
protected void Button1_Click(object sender, EventArgs e)
{
TableRow row = new TableRow();
TableCell cell = new TableCell();
TextBox txt = new TextBox();
txt.Width = 200;
cell.Controls.Add(txt);
row.Cells.Add(cell);
Table1.Rows.Add(row);
List myData = (List)ViewState["allData"];
myData.Add(txt.Text);
ViewState["allData"] = myData;
}
}

MaintaningDynamicControlsi Asp.net

2009-08-27T02:03:00.000-07:00

Paste This Code in Page_load
------------------------------
if (Page.IsPostBack != true)
{
List temp1 = new List();
ViewState["allData"] = temp1;

}
List values = (List)ViewState["allData"];
foreach (string strdata in values)
{
TableRow row = new TableRow();
TableCell cell = new TableCell();

Label label = new Label();
label.Text = strdata.Split(',')[0];
cell.Text = strdata.Split(',')[0];
row.Cells.Add(cell);
//pnlDynamiclabelsandtxt.Controls.Add(label);
TextBox text = new TextBox();
text.Text = strdata.Split(',')[1];
cell = new TableCell();
cell.Controls.Add(text);// = strdata.Split(',')[1];
row.Cells.Add(cell);
table.Rows.Add(row);
//pnlDynamiclabelsandtxt.Controls.Add(table);

//pnlDynamiclabelsandtxt.Controls.Add(text);
}

Paste This Code In BtnAdd_click
-----------------------------------------------------

for (int i = 0; i < gvUser.Rows.Count; i++)
{
CheckBox chk = (CheckBox)gvUser.Rows[i].Cells[0].FindControl("cbUser");
if (chk.Checked == true)
{
string strUserName = gvUser.Rows[i].Cells[2].Text;
string strUserID = gvUser.Rows[i].Cells[1].Text.ToString();
DataSet ds = DisplayUserAll();
DataRow[] drarr = ds.Tables[0].Select("FIELD1='" + strUserID + "'");
string strPhoneN0 = drarr[0]["FIELD10"].ToString();

TableRow row = new TableRow();
TableCell cell = new TableCell();

cell.Text = strUserName;
row.Cells.Add(cell);
//AddDynamicLabel(strUserName);
TextBox txt = new TextBox();
txt.Text = strPhoneN0;
txt.Width = 200;
cell = new TableCell();
cell.Controls.Add(txt);// = strPhoneN0;
row.Cells.Add(cell);

table.Rows.Add(row);

//pnlDynamiclabelsandtxt.Controls.Add(txt);
List myData = (List)ViewState["allData"];
myData.Add(strUserName + "," + strPhoneN0);
ViewState["allData"] = myData;
pnlDynamiclabelsandtxt.Visible = true;

}
}

ASP.NET Caching

2009-08-25T04:35:00.000-07:00

http://aspnet.4guysfromrolla.com/articles/022802-1.aspx

Lean Wpf

2009-08-07T22:51:00.000-07:00

http://www.wpftutorial.net/

LINQ With Asp.net

2009-07-24T22:47:00.000-07:00

http://weblogs.asp.net/scottgu/archive/2006/05/14/Using-LINQ-with-ASP.NET-_2800_Part-1_2900_.aspx

Introduction to .Net Framework 2.0 Nullable Types

2009-07-23T23:57:00.001-07:00

http://www.c-sharpcorner.com/UploadFile/mosessaur/nullabletypes08222006164135PM/nullabletypes.aspx

Session Management

2009-07-13T22:41:00.000-07:00

http://www.codeproject.com/KB/aspnet/ExploringSession.aspx

Forms Authentication in asp.net

2009-07-09T02:45:00.000-07:00

refer this url
http://www.4guysfromrolla.com/webtech/110701-1.shtml

http://www.15seconds.com/Issue/020220.htm

create html table from javascript

2009-07-03T03:39:00.000-07:00

SqlQuery for copying data from one table to another table when serial no is even

2009-07-02T23:32:00.000-07:00

insert into table1 (id,sal) select sal,id from example where cast(sal as int)%2<>1

Stored Procedure with 2 SqlStatements

2009-07-02T22:33:00.000-07:00

create procedure sp_Retrive
as
select ID,Sal from Example
select Id,Name from Test
go

SqlConnection cnn = new SqlConnection("user id=sa;password=;database=samples;server=localhost\\SQLEXPRESS");

SqlCommand cmd = new SqlCommand("Retrive",cnn);
cmd.CommandType = CommandType.StoredProcedure;
SqlDataAdapter da = new SqlDataAdapter(cmd);
DataSet ds = new DataSet();
da.Fill(ds);

webservice.htc document for calling webservice from html

2009-07-02T20:02:00.000-07:00

webservice.htc

sample application for calling webservice from HTML in asp.net using Javascript
Callingwebservice.rar

Getting directory information

2009-07-02T07:01:00.000-07:00

int count = 0;
protected void Page_Load(object sender, EventArgs e)
{
try
{
string[] strFiles = Directory.GetFiles("E://svsv");
string[] strarr =new string[1];
strarr[0] = "E://svsv";
direc(strarr);

}
catch
{

}
}
public void direc(string[] str)
{
for (int inti = 0; inti < str.Length; inti++)
{
string[] strFiles = Directory.GetFiles(str[inti]);
count =count+ strFiles.Length;
string[] strDirectory = Directory.GetDirectories(str[inti]);
for (int i = 0; i < strDirectory.Length; i++)
{
string[] strFiles1 = Directory.GetFiles(strDirectory[i]);
count = count + strFiles1.Length;
}
for (int i = 0; i < strDirectory.Length; i++)
{
string[] strFiles1 = Directory.GetDirectories(strDirectory[i]);
if (strFiles1.Length != 0)
{
//string[] strarr = new string[strFiles1.Length];
//for (int j = 0; j < strarr.Length; j++)
//{
// strarr[j] = str[inti]+"//"+strarr[j]+"//";
//}
direc(strFiles1);
}
}
}

}

Skins,Themes,StyleSheets in asp.net2.0

2009-06-20T03:22:00.000-07:00

http://www.beansoftware.com/ASP.NET-Tutorials/Themes-Skins.aspx

Samples on Update Pannel

2009-06-19T22:49:00.000-07:00

http://www.asp.net/AJAX/documentation/live/Tutorials/UpdatePanelTutorials.aspx

Sample Articles on Dot Net

2009-06-18T22:13:00.000-07:00

Impersonation in asp.net

Creating Triggers in sql server

Asp.net Page Life Cycle

Serialization and Deserialization in .net

2009-06-08T19:18:00.000-07:00

Introduction

Serialization is a process of converting an object into a stream of data so that
it can be easily transmittable over the network or can be continued in a persistent
storage location. This storage location can be a physical file, database or ASP.NET
cache. Serialization is the technology that enables an object to be converted into
a linear stream of data that can be easily passed across process boundaries and
machines. This stream of data needs to be in a format that can be understood by
both ends of a communication channel so that the object can be serialized and reconstructed
easily. The advantage of serialization is the ability to transmit data across the
network in a cross-platform-compatible format, as well as saving it in a persistent
or non-persistent storage medium in a non-proprietary format. Serialization is used
by Remoting, Web Services SOAP for transmitting data between a server and a client.
De-serialization is the reverse; it is the process of reconstructing the same object
later. The Remoting technology of .NET makes use of serialization to pass objects
by value from one application domain to another.

In this article, I will discuss .NET's support for Serialization and how we can
build a class that supports custom serialization.

What is Serialization and De-Serialization?

Serialization is the process of saving the state of an object in a persistent storage
media by converting the object to a linear stream of bytes. The object can be persisted
to a file, a database or even in the memory. The reverse process of serialization
is known as de-serialization and enables us to re-construct the object from the
previously serialized instance of the same in the persistent or non-persistent storage
media.

Serialization in .NET is provided by the System.Runtime.Serialization
namespace. This namespace contains an interface called IFormatter which
in turn contains the methods Serialize and De-serialize that can be used to save
and load data to and from a stream. In order to implement serialization in .NET,
we basically require a stream and a formatter. While the stream acts as a container
for the serialized object(s), the formatter is used to serialize these objects onto
the stream.

The basic advantage of serialization is the ability of an object to be serialized
into a persistent or a non-persistent storage media and then reconstructing the
same object if required at a later point of time by de-serializing the object. Remoting
and Web Services depend heavily on Serialization and De-serialization.

Advantages and Disadvantages of Serialization

The following are the basic advantages of serialization:

Facilitate the transportation of an object through a network

Create a clone of an object

The primary disadvantage of serialization can be attributed to the resource overhead
(both the CPU and the IO devices) that is involved in serializing and de-serializing
the data and the latency issues that are involved for transmitting the data over
the network. Further, serialization is quite slow. Moreover, XML serialization is
insecure, consumes a lot of space on the disk and it works on publicmembers and public
classes and not on the private or
internal classes. Therefore, it compels the developer to allow the
class to be accessed by the outside world.

The Serializable Attribute

In order for a class to be serializable, it must have the attribute SerializableAttributeset and all its members must also be serializable, except if they are ignored
with the attribute NonSerializedAttribute. However, the class="code-keyword">private and publicmembers of a class are always serialized by default. The SerializationAttributeis only used for binary serialization. The code snippet below shows the
usage of SerializableAttribute.


using System;
using System.Collections.Generic;
using System.Text;
using System.Xml.Serialization;
namespace DemoSerialization
{
    [Serializable]
    public class Employee
    {
        public int empCode;
        public string empName;
        [XmlAttribute(empName)]
        public string EmpName
        {
            get
            {
                return empName;
            }

            set
            {
                empName = value;
            }
        }
    }
}

Note the Serializable attribute that is specified at the beginning
of the class in the code listing above. The SerializableAttribute is
useful for situations where the object has to be transported to other application
domains. It needs to be applied even irrespective of whether the class implements
the ISerializable interface. If this attribute is not set in that case,
then when we try to serialize an object, the CLR throws a SerializationException.

Types of Serialization

Serialization can be of the following types:

Binary Serialization

SOAP Serialization

XML Serialization

All these types of serialization are explained in detail in the sections that follow.

Binary Serialization

Binary serialization is a mechanism which writes the data to the output stream such
that it can be used to re-construct the object automatically. The term binary in
its name implies that the necessary information that is required to create an exact
binary copy of the object is saved onto the storage media. A notable difference
between Binary serialization and XML serialization is that Binary serialization
preserves instance identity while XML serialization does not. In other
words, in Binary serialization the entire object state is saved while in XML serialization
only some of the object data is saved. Binary serialization can handle graphs with
multiple references to the same object; XML serialization will turn each reference
into a unique object. The following code listing shows how we can implement binary
serialization.


#region Binary
private void btnBSerialize_Click(    class="code-keyword">object sender, EventArgs e)
{
    Employee emp=new Employee();
    emp.empCode=Convert.ToInt16(txtbEmpCode.Text);
    emp.EmpName=txtBEmpName.Text;
    BinarySerialize(txtBinary.Text, emp);
    MessageBox.Show(Binary Serialize Done!);
}
private void btnBDSerialize_Click(    class="code-keyword">object sender, EventArgs e)
{
    Employee emp = new Employee();
    emp = (Employee)BinaryDeserialize(txtBinary.Text);
    lblBEmpCode.Text =Emp Code: + Convert.ToString(emp.empCode);
    lblBEmpName.Text = Emp Name: + emp.EmpName;
}
public void BinarySerialize(    class="code-keyword">string filename, Employee emp)
{
    FileStream fileStreamObject;

    fileStreamObject = new FileStream(filename, FileMode.Create);
    BinaryFormatter binaryFormatter = new BinaryFormatter();
    binaryFormatter.Serialize(fileStreamObject, emp);
    fileStreamObject.Close();
}
public static     class="code-keyword">object BinaryDeserialize(string filename)
{
    FileStream fileStreamObject = new FileStream(filename, FileMode.Open);
    BinaryFormatter binaryFormatter = new BinaryFormatter();
    object obj = (object)binaryFormatter.Deserialize(fileStreamObject);
    fileStreamObject.Close();
    return obj;
}
#endregion

Advantages and Disadvantages of Binary Serialization

One of the major advantages of using Binary Serialization in the managed environment
is that the object can be de-serialized from the same data you serialized it to.
Besides, the other advantage of Binary Serialization is enhanced performance as
it is faster and even more powerful in the sense that it provides support for complex
objects, read only properties and even circular references. However, the downside
to this is that it is not easily portable to another platform.

SOAP Serialization

The SOAP protocol is ideal for communicating between applications that use heterogeneous
architectures. In order to use SOAP serialization in .NET we have to add a reference
to System.Runtime.Serialization.Formatters.Soap in the application.
The basic advantage of SOAP serialization is portability. The SoapFormatter
serializes objects into SOAP messages or parses SOAP messages and extracts serialized
objects from the message. The following code listing shows how we can implement
serialization using the SOAP protocol:


#region SOAP

private void btnSSerialize_Click(    class="code-keyword">object sender, EventArgs e)
{
    Employee emp = new Employee();
    emp.empCode = Convert.ToInt16(txtSEmpCode.Text);
    emp.EmpName = txtSEmpName.Text;
    SOAPSerialize(txtSoap.Text, emp);
    MessageBox.Show(SOAP Serialize Done!);
}

private void btnSDeSerialize_Click(    class="code-keyword">object sender, EventArgs e)
{
    Employee emp = new Employee();
    emp = (Employee)SOAPDeserialize(txtSoap.Text);
    lblSEmpCode.Text = Emp Code: + Convert.ToString(emp.empCode);
    lblSEmpName.Text = Emp Name: + emp.EmpName;
}
public void SOAPSerialize(    class="code-keyword">string filename, Employee employeeObject)
{
    FileStream fileStreamObject = new FileStream(filename, FileMode.Create);
    SoapFormatter soapFormatter = new SoapFormatter();
    soapFormatter.Serialize(fileStreamObject, employeeObject);
    fileStreamObject.Close();
}
public static     class="code-keyword">object SOAPDeserialize(string filename)
{
    FileStream fileStreamObject = new FileStream(filename, FileMode.Open);
    SoapFormatter soapFormatter = new SoapFormatter();
    object obj = (object)soapFormatter.Deserialize(fileStreamObject);
    fileStreamObject.Close();
    return obj;
}
#endregion

XML Serialization

According to MSDN, "XML serialization converts (serializes) the publicfields and properties of an object or the parameters and
returns values of methods, into an XML stream that conforms to a specific XML Schema
definition language (XSD) document. XML serialization results in strongly typed
classes with public properties and
fields that are converted to a serial format (in this case, XML) for storage or
transport. Because XML is an open standard, the XML stream can be processed by any
application, as needed, regardless of platform." Implementing XML Serialization
in .NET is quite simple. The basic class that we need to use is the XmlSerializerfor both serialization and de-serialization. The Web Services use the SOAP
protocol for communication and the return types and the parameters are all serialized
using the XmlSerializer class. XML Serialization is however, much slower
compared to Binary serialization. We can set a property as an XML attribute as shown
in the code listing below.


#region Xml
private void btnXSerialize_Click(    class="code-keyword">object sender, EventArgs e)
{
    Employee emp = new Employee();
    emp.empCode = Convert.ToInt16(txtXEmpCode.Text);
    emp.EmpName = txtXEmpName.Text;
    XMLSerialize(txtXml.Text, emp);
    MessageBox.Show(Xml Serialize Done!");
        } private void btnXDeSerialize_Click(object sender, EventArgs e) { Employee emp
        = new Employee(); emp = (Employee)XMLDeserialize(txtXml.Text); lblXEmpCode.Text
        = Emp Code:" + Convert.ToString(emp.empCode);
    lblXEmpName.Text = Emp Name:"
        + emp.EmpName; } public void XMLSerialize(String filename, Employee emp) { XmlSerializer
        serializer = null; FileStream stream = null; serializer = new XmlSerializer(typeof(Employee));
        stream = new FileStream(filename, FileMode.Create, FileAccess.Write); serializer.Serialize(stream,
        emp); if (stream != null) stream.Close(); } public static Employee XMLDeserialize(String
        filename) { XmlSerializer serializer = null; FileStream stream = null; Employee
        emp = new Employee(); serializer = new XmlSerializer(typeof(Employee)); stream =
        new FileStream(filename, FileMode.Open); emp = (Employee)serializer.Deserialize(stream);
        if (stream != null) stream.Close(); return emp; } #endregion

Advantages of XML Serialization

The advantages of XML Serialization are as follows:

XML based

Support for cross platforms

Easily readable and editable

Working with Formatters

A formatter is used to determine the serialization format for objects. In other
words, it is used to control the serialization of an object to and from a stream.
They are the objects that are used to encode and serialize data into an appropriate
format before they are transmitted over the network. They expose an interface called
the IFormatter interface. IFormatter's significant methods
are Serialize and De-serialize which perform the actual serialization and de-serialization.
There are two formatter classes provided within .NET, the BinaryFormatter
and the SoapFormatter. Both these classes extend the IFormatter
interface.

The Binary Formatter

The Binary formatter provides support for serialization using binary encoding. The
BinaryFormater class is responsible for binary serialization and is
used commonly in .NET's Remoting technology. This class is not appropriate when
the data is supposed to be transmitted through a firewall.

The SOAP Formatter

The SOAP formatter provides formatting that can be used to serialize objects using
the SOAP protocol. It is used to create a Soap envelop and it uses an object graph
to generate the result. It is responsible for serializing objects into SOAP messages
or parsing the SOAP messages and extracting these serialized objects from the SOAP
messages. SOAP formatters in .NET are widely used by the Web Services.

Points to Remember

This section deals with some of the points that we have already covered in this
article and some others that we have not, but are still very important and relate
to the serialization and de-serialization concepts of .NET. When you apply the Serializablecustom attribute to a type, all instance fields of the class
(public, private, protected,
etc.) are serialized automatically. XmlSerializer does not use the
ISerializable interface; rather, it uses the IXmlSerializable
interface. The XmlSerializer class can only serialize the class="code-keyword">public properties of the class, whereas the
BinaryFormatter class can serialize privatefields using the ISerializable interface.

The Serializable attribute is a must for making a class serializable
irrespective of whether we have implemented the ISerializable interface
in this class. When we serialize a class, the objects of the references to other
classes that are contained in this class are also serialized if they are marked
as serializable. All members are serialized, including public, private
or protected members. Furthermore,
even circular references are supported by binary serialization. Note that read only
properties are not serialized except the collection class objects. However, the
read only properties can be serialized using binary serialization.

If we do not require serializing a particular property of a class when using an
XmlSerializer, we have to mark the property with the custom attribute
XmlIgnoreAttribute. When using a SoapFormatter we have
to use the SoapIgnoreAttribute instead. The XmlSerializer
generates an in-memory assembly optimized for each type since the initial invocation
to a Web Service always takes so much time. To combat this, we can use the sgen.exe
tool to pre-generate the serialization assembly.

Conclusion

Serialization is the process of storing an object, including all of its members,
to a persistent or a non-persistent storage media by converting the object into
a linear stream of data. De-serialization is the process of restoring an object's
values from the said stream. The advantage of serialization is to save the state
of an object in order to have the ability to recreate the same object at a later
point of time if and when it is required. The .NET Framework provides a strong support
for serialization of objects. The .NET Framework provides a unified standard for
serializing and de-serializing objects for building distributed heterogeneous systems.
This article has explored Serialization and De-serialization and the various types
of Serialization concepts with code examples wherever necessary. It has discussed
what Custom Serialization is and how to implement it. However, I would recommend
not using serialization unless it is absolutely necessary due to the drawbacks that
I have already explained in this article.

reference :
http://www.codeproject.com/KB/aspnet/Serialization.aspx
http://www.developer.com/net/csharp/article.php/3110371

ajax tool kit sample url

2009-06-04T05:16:00.001-07:00

http://www.asp.net/ajax/AjaxControlToolkit/Samples/

Enum - Enumerator in C#

2009-05-30T03:24:00.001-07:00

valign="top" width="100%"> Enumerators in C#
valign="top">
valign="top"> Enumerators can be used to store lists of value types with set values, much like constants. For example, a C# constant could be defined using the statement below: color="#0000ff" size="2"> const int EngineCapacity = 1000; If there was more than one engine capacity, then a range of constants could be defined, such as: const int EngineCapacitySmall = 600; const int EngineCapacityMedium = 1000; const int EngineCapacityLarge = 1200; const int EngineCapacityExtraLarge = 1800; If even more constants were needed then this list could get pretty large, so it would be more convenient to group them into a single enumerator, by using syntax such as that shown below: /// <summary> /// Engine capacity enumerator /// class="Apple-converted-space"> </summary> enum EngineCapacity class="Apple-converted-space"> : int { Small = 600, Medium = 1000, Large = 1200, ExtraLarge = 1800 } Each enumerator is assigned a name (in this case it is EngineCapacity) and an optional data type. Here, the EngineCapacity enumerator is assigned a type of int, although being the default data type for enumerators it does not need to be specified - the following code will also work: enum EngineCapacity class="Apple-converted-space"> : int { Small = 600, Medium = 1000, Large = 1200, ExtraLarge = 1800 } A value for the enumerator's type does not need to be specified - if it is not then the value of a type is incremented by one from the previous type (taking 0 as the first value). So in the example below, the small engine capacity will be 0 and the large engine capacity value will be 1001: enum EngineCapacity class="Apple-converted-space"> : int { Small, Medium = 1000, Large, ExtraLarge = 1800 } Using the enumerator Once the enumerator has been assigned it may be used in instances such as that shown below: int RequiredCapacity = 1000; if (RequiredCapacity == (int size="2">) size="2">EngineCapacity.ExtraLarge) { color="#008000" size="2">//Check customer has the required maintenance contract //for the largest engine type if (CheckCustomerHasMaintenenceContract() == false) { return; } } Note that Visual Studio understands enumerators, and will usefully include their value types in the intellisense for that enumerator.

federal bank

2009-05-26T01:45:00.001-07:00

http://www.federalbank.co.in/Careers/jobssep2007/index.htm

Regular Express Tutorial.

2009-05-22T03:40:00.000-07:00

This list of regular expression examples serves several purposes.
Library of useful expressions which you can include in your code
Examples of well written expressions
For advanced examples, see Advanced Regular Expression Examples You can also find some regular expressions on Regular Expressions and Bag of algorithms pages.
Here's a good source-book for useful regular expressions for programmers: http://www.regular-expressions.info/examplesprogrammer.html

Simple examples demonstrating the [ regexp ] command

The regexp command has syntax:
regexp ?switches? exp string ?matchVar? ?subMatchVar subMatchVar ...?
If matchVar is specified, its value will be only the part of the string that was matched by the exp. As an example:
regexp {c.*g} "abcdefghi" matched
puts $matched ;# ==> cdefg
If any subMatchVars are specified, their values will be the part of the string that were matched by parenthesized bits in the exp, counting open parentheses from left to right. For example:
regexp {c((.*)g)(.*)} "abcdefghi" matched sub1 sub2 sub3
puts $matched ;# ==> cdefghi
puts $sub1 ;# ==> defg
puts $sub2 ;# ==> def
puts $sub3 ;# ==> hi
Many times, people only care about the subMatchVars and want to ignore matchVar. They use a "dummy" variable as a placeholder in the command for the matchVar. You will often see things like
regexp $exp $string -> sub1 sub2
where ${->} holds the matched part. It is a sneaky but legal Tcl variable name.

Splitting a String Into Words

"How do I split an arbitrary string into words?" is a frequently asked question. If you use [split $string " "], then multiple spaces will produce a list with empty elements. If you try to use [foreach] or [lindex] or some other list operation, then you must be sure that the string is a well-formed list. (Braces could cause problems.) So use a regular expression like this very simple shorthand for non-space characters.
{\S+}
You can even split a string of text with arbitrary spaces and special characters into a list of words by using [regexp]s -inline and -all switches.
set text "Some arbitrary text which might include \$ or {"
set wordList [regexp -inline -all -- {\S+} $text]

Floating Point Number

This expression includes options for leading +/- character, digits, decimal points, and a trailing exponent. Note the use of nearly duplicate expressions joined with the or operator "|" to permit the decimal point to lead or follow digits. This was posted to comp.lang.tcl by Roland B. Roberts.
{[-+]?([0-9]+\.?[0-9]*|\.[0-9]+)([eE][-+]?[0-9]+)?}

Letters

Thanks to Brent Welch for these examples, showing the difference between a traditional character matching and "the Unicode way."
{^[A-Za-z]+$} Only letters.

{^[[:alpha:]]+$} Only letters, the Unicode way.

Special Characters

Thanks again to Brent Welch for these two examples.
{[][${}\\]} The set of Tcl special characters: ] [ $ { } \

{[][$^?+*()|\\]} The set of regular expression special characters: ] [ $ ^ ? + * ( ) | \
I don't understand these examples. Why have [, ], and then the rest of the characters inside a [] - that just makes the string have [ and ] there twice, right?
LV: the first regular expression should be seen like this:
{ ... } - protect the 9 inner characters
[ ... ] - these two define a set of characters to process
] - if your set of characters is going to include the right bracket character (]) as a specific matching character, then it needs to be first in the set/class definition.
[${} - these are more individual characters
\\ - this is doubled because when regexp goes to evaluate the characters, it would otherwise treat a single backslash (\) as a request to quote the next character, the ending right bracket of the set/class.
The second regular expresesion is interpreted in a similar fashion. There are more characters because there are more metacharacters.
Also, not all characters are there - where are the period, equals, bang (exclamation sign), dash, colon, alphas that are a part of character entry escapes or classes, 0, hash/pound sign, and angle brackets (< and >)? These special characters all have meta meanings within regular expressions...
LV Apparently no one has come along and updated the above expression to cover these.
Example posted by KC:
{[\<\>]} - defines a set containing both angle brackets

IP Numbers

You can create a regular expression to check an IP address for correct syntax. Note that this regular expression only checks for groups of 1-3 digits separated by periods. If you want to ensure that the digit groups are from 0-255, or that you have a valid IP address, you'll have to do additional (non regexp) work. This code posted to comp.lang.tcl by George Peter Staplin
set str 66.70.7.154

regexp "(\[0-9]{1,3})\.(\[0-9]{1,3})\.(\[0-9]{1,3})\.(\[0-9]{1,3})" $str all first second third fourth

puts "$all \n $first \n $second \n $third \n $fourth \n"
The above regular expression matches any string where there are four groups of 1-3 digits separated by periods. Since it's not anchored to the start and end of the string (with ^ and $) it will match any string that contains four groups of 1-3 digits separated by periods, such as: "66.70.7.154.9".
If you don't mind a longer regexp, there is no reason you can't ensure that each group of 1-3 digits is in the range of 0-255. For example (broken up a bit to make it more readable):
set octet {(\d|[1-9]\d|1\d\d|2[0-4]\d|25[0-5])}
set RE "^[join [list $octet $octet $octet $octet] {\.}]\$"
regexp $RE $str all first second third fourth ;# Michael A. Cleverly
recently on comp.lang.tcl, someone mentioned that http://www.oreilly.com/catalog/regex/chapter/ch04.html#Be_Specific talks about matching IP addresses.

Domain names First shot

^[a-zA-Z]([a-zA-Z0-9-]{0,61}[a-zA-Z0-9])?\.[a-zA-Z]([a-zA-Z0-9-]{0,61}[a-zA-Z0-9])?(\.[a-zA-Z]([a-zA-Z0-9-]{0,61}[a-zA-Z0-9])?)?$
This code does NOT attempt, obviously, to ensure that the last level of the regular expression matches a known domain...

E-mail addresses: No warranty, just a first shot:
{^[A-Za-z0-9._-]+@[[A-Za-z0-9.-]+$} ;# RS

Understand that this expression is an attempt to see if a string has a format that is compatible with normal RFC SMTP email address formats. It does not attempt to see whether the email address is correct. Also, it does not account for comments embedded within email addresses, which are defined even though seldom used.

XML-like data

To match something similar to XML-tags you can use regular-expressions, too. Let's assume we have this text:
% set text {sM}
We can match the body of bo with this regexp:
% regexp "<(bo)>(.*?)" $text dummy tag body
Now we extend our XML-text with some attributes for the tags, say:
% set text2 {sM}
If we try to match this with:
% regexp "<(bo)\\s+(.+?)>(.*?)" $text2 dummy tag attributes body
it won't work anymore. This is because \\s+ is greedy (in contrary to the non-greedy (.+?) and (.*?)) and that (the one greedy-operator) makes the whole expression greedy. (Refer to this [1] Sept. 1999 posting from Henry Spenter to c.l.t.)
The correct way is:
% regexp "<(bo)\\s+?(.+?)>(.*?)" $text2 dummy tag attributes body
Now we can write a more general XML-to-whatever-translater like this:
Substitute [ and ] with their corresponding [and] to avoid confusion with "subst" in 3.
Substitute the tags and attributes with commands
Do a "subst" on the whole text, thereby calling the inserted commands
proc xml2whatever {text userCallback} {
set text [string map {[ [ ] ]} $text]
# replace all tags with a call to userCallback
# this has to be done multiple times, because of nested tags
# match each tag (everything not space after <)
# and all the attributes (everything behind the tag until >)
# than match body and the end-tag (which should be the same as the
# first matched one (\1))
while {[regsub -all {<(\S+?)(.*?)>(.*?)} $text "\[[list $userCallback \\1 \\2 \\3]\]" text]} {
# do nothing
}
return [subst -novariables -nobackslashes $text]
}

# is called from xml2whatever with
# element: the xml-element
# attributes: the attributes of xml-element
# body: body of xml-element
proc myTranslate {element attributes body} {
# map bo - b; it - i (leave rest alone)
# do a subst for the body, because of possible nested tags
switch -- $element {
bo { return "[subst -novariables -nobackslashes $body]"}
it { return "[subst -novariables -nobackslashes $body]"}
default { return "<$element$attributes>[subst -novariables -nobackslashes $body]" }
}
}
Call the parser with:
% xml2whatever $text2 myTranslate
You have to be careful, though. Don't do this for large texts or texts with many nested xml-tags because the regular-expression-machine is not the the right tool to parse large,nested files efficiently. (Stefan Vogel)
DKF - I agree with that last point. If you are really dealing with XML, it is better to use a proper tool like TclDOM or tDOM.

Negated string:

Bruce Hartweg wrote in comp.lang.tcl: You can't negate a regexp, but you CAN negate a regexp that is only a simple string. Logically, it's the follow ing:
match any single char except first letter in the string.
match the first char in string if followed by any letter except the 2nd
match the first two if followed by any but the third, et cetera
Then the only thing more is to allow a partial match of the string at end of line. So for a regexp that matches
any line that DOES NOT have the word ''foo'':

set exp {^([^f]|f[^o]|fo[^o])*.{0,2}$}
The following proc will build the expression for any given string
proc reg_negate {str} {
set partial ""
set branches [list]
foreach c [split $str ""] {
lappend branches [format {%s[^%s]} $partial $c]
append partial $c
}
set exp [format {^(%s)*.{0,%d}$} [join $branches "|"] \
[expr [string length $str] -1]]
}
Donal Fellows followed up with:
That's just set me thinking; you can do this by specifying that the whole string must be either not the character of the antimatch*, or the first character of the antimatch so long as it is not followed by the rest of the antimatch. This leads to a fairly simply expressed pattern.
set exp {^(?:[^f]|f(?!oo))*$}
In fact, this allows us to strengthen what you say above to allow the matching of any negated regexp directly so long as the first component of the antimatch is a literal, and the rest of the antimatch is expressible in an ERE lookahead constraint (which imposes a number of restrictions, but still allows for some fairly sophisticated patterns.)
* Anything's better than overloading 'string' here!
JMN 2005-12-22 Could someone please explain what is meant by a 'negated string' here? Specifically - what do the above achieve that isn't satisfied by the simpler:
set exp {^(?!(.*foo.*))}
Doesn't the following snippet from the regexp manpage indicate that a regexp can be negated? where does(or did?) the 'simple string' requirement come in? - is this info no longer current?
(?!re)
negative lookahead (AREs only), matches at any point where no substring matching re begins
Lars H: It indeed seems the entire problem is rather trivial. In Tcl 7 (before AREs) one sometimes had to do funny tricks like the ones Bruce Hartweg performs above, but his use of {0,2} means he must be assuming AREs. Perhaps there was a transitory period where one was available but not the other.
VisualRegExp is a good way to learn about REs.
Visual Regexp is a terrific way to learn about REs.
Redet is another tool for learning about and working with REs.

Turn a string into %hex-escaped (url encoded) characters:

e.g. Csan -> %43%73%61%6E

regsub -all -- {(.)} $string {%[format "%02lX" [scan \1 "%c"]]} new_string
subst $new_string
This demonstrates the power of using regsub together with subst, which is regarded as one of the most powerful ways to use regular expressions in Tcl.

Turn a string into %hex-escaped (url encoded) characters (part 2)

This one makes the result more readable and still quite safe to use in URLs e.g. http://wiki.tcl.tk -> http%3A%2F%2Fwiki%2Etcl%2Etk
regsub -all -- {([^A-Za-z0-9_-])} $string {%[format "%02lX" [scan \1 "%c"]]} new_string
subst $new_string
nl
Joe Mistachkin
The inverse of the above (not optimized):
regsub -all -- {%([0123456789ABCDEF][0123456789ABCDEF])} $string {[format "%c" 0x\1]} new_string
subst $new_string

Caveats about using [regsub] with [subst]

glennj 20081216: It can be dangerous to blindly apply [subst] to the results of [regsub], particularly if you have not validated the input string. Here's an example that's not too contrived:
set string {[some malicious command]}
regsub -all {\w+} $string {[string totitle &]} result
subst $result
This results in "invalid command name "Some"". What if $string was {[exec format c:]}?
See DKF's "proc regsub-eval" contribution in regsub to properly prepare the input string for substitution. Paraphrased:
set string {[some malicious command]}
set escaped [string map {\[ \\[ \] \\] \$ \\$ \\ \\\\} $string]
regsub -all {\w+} $escaped {[string totitle &]} result
subst $result
which results in what you'd expect: the string "[Some Malicious Command]"

Maintain proper spacing when formatting for HTML

DG got this from Kevin Kenny on c.l.t.
regsub -all { (?= )} $line {\ } line

set line {this is an example}
regsub -all { (?= )} $line {\ } line
set line
this is an example
And tabs require replacement, too:
set tabFill "[string repeat \\ \; 7] "
regsub -all {\t} $line $tabFill line
glennj taken from comp.lang.perl.misc, transform variable names into StudlyCapsNames:
set old_vars {VARIABLE_ONE VARIABLE_NUMBER_TWO a_really_long_VARIABLE_name}
set NewVars {}
foreach v $old_vars {
regsub -all {_?(.)([^_]*)} $v {[string toupper "\1"][string tolower "\2"]} new
lappend NewVars [subst $new]
}
When using [ASED]'s syntax checker you get an error of you don't insert " -- " after "regexp". Instead of "regexp {([^A-Za-z0-9_-])} $string" you have to write "regexp -- {([^A-Za-z0-9_-])} $string"
LV A user recently asked:
I have a string that I'm trying to parse. Why doesn't this seem to work?
% set str {Acc No: 12345}
% set num [regexp {.*?(\d+).*} $str junk result]
% puts $result
1
It looks to me like the *? causes the subsequent \d+ to also be greedy and only match the first hit. Did I figure that out correctly? I presume that we currently don't have a way to turn off the greediness item?
Of course, in this simplified problem, one could just drop the greediness and code
% set num [regexp {(\d+)} $str junk result]
% puts $result
12345
I'll let the user decide if that suffices.
How do you select from two words?
% set word "foo"
% set result [regexp {(foo|bar)} match zzz]
% set zzz
can't read "zzz": no such variable
???
LES: You got the regexp syntax wrong and tried to match the regular expression with the string "match". There is no "zzz" variable (the actual match variable in your code) because your regular expression does not match the string "match". Try this:
% set word "foo"
% set result [regexp {(foo|bar)} $word match zzz]
% set match
Note that I could have dropped the "zzz" variable, but left it there as a second match variable, as an exercise to you. You should understand why and what it does if you read the regexp page and assimilate the syntax.
RUJ: Could you match the following pattern of following string: infinite spaces at start and end.
% set str " sjkhf sdhj "
LV try
set rest [regexp {^ +.* +$} $str match]
puts $rest
which should have a value of 1 (in other words, it matched). Of course, if those leading and trailing spaces are optional, then change the + to a *.

reference:
http://regexlib.com/DisplayPatterns.aspx?cattabindex=2&categoryId=3

Converting Datetime column type to any Datetime formats in Sql Server from Query

2009-05-22T02:47:00.000-07:00

What are the valid styles for converting datetime to string?

I wrote this little table and procedure to help me remember what style 112 did, or how to get HH:MM AM/PM out of a DATETIME column. Basically, it populates a table with the valid style numbers, then loops through those, and produces the result (and the syntax for producing that result) for each style, given the current date and time.

Yes, it uses a cursor. This is designed to be a helper function, not something you would use as part of a production environment, so I don't think the performance implications should be a big concern. But if you have

USE tempdb;
GO

CREATE PROCEDURE dbo.help_DateTimeFormats
@styleID TINYINT = NULL
AS
BEGIN
SET NOCOUNT ON;

IF OBJECTPROPERTY
(
OBJECT_ID('dbo.DateTimeFormats'),
'IsUserTable'
) = 1
BEGIN
DROP TABLE dbo.DateTimeFormats;
END

CREATE TABLE dbo.DateTimeFormats
(
styleID TINYINT PRIMARY KEY,
outputLength TINYINT,
outputSyntax VARCHAR(64),
outputSample VARCHAR(255)
);

INSERT dbo.DateTimeFormats(styleID, outputLength)
SELECT style = 0, outputLength = 19
UNION SELECT 1, 8
UNION SELECT 2, 8
UNION SELECT 3, 8
UNION SELECT 4, 8
UNION SELECT 5, 8
UNION SELECT 6, 9
UNION SELECT 7, 10
UNION SELECT 8, 8
UNION SELECT 9, 26
UNION SELECT 10, 8
UNION SELECT 11, 8
UNION SELECT 12, 6
UNION SELECT 13, 24
UNION SELECT 14, 12
UNION SELECT 20, 19
UNION SELECT 21, 23
UNION SELECT 22, 20
UNION SELECT 23, 10
UNION SELECT 24, 8
UNION SELECT 25, 23
UNION SELECT 100, 19
UNION SELECT 101, 10
UNION SELECT 102, 10
UNION SELECT 103, 10
UNION SELECT 104, 10
UNION SELECT 105, 10
UNION SELECT 106, 11
UNION SELECT 107, 12
UNION SELECT 108, 8
UNION SELECT 109, 26
UNION SELECT 110, 10
UNION SELECT 111, 10
UNION SELECT 112, 8
UNION SELECT 113, 24
UNION SELECT 114, 12
UNION SELECT 120, 19
UNION SELECT 121, 23
UNION SELECT 126, 23
UNION SELECT 130, 32
UNION SELECT 131, 25;

IF CHARINDEX('SQL Server 2005', @@VERSION) > 0
INSERT dbo.DateTimeFormats(styleID, outputLength)
SELECT 127, 23; -- 127 is new in 2005

UPDATE dbo.DateTimeFormats
SET outputSyntax = 'CONVERT(CHAR('
+ RTRIM(outputLength) + '), CURRENT_TIMESTAMP, '
+ RTRIM(styleID) + ')';

DECLARE
@sql VARCHAR(1024),
@style TINYINT,
@syntax VARCHAR(64);

DECLARE c CURSOR
LOCAL FORWARD_ONLY STATIC READ_ONLY FOR
SELECT styleID, outputSyntax
FROM dbo.DateTimeFormats;

OPEN c; FETCH NEXT FROM c INTO @style, @syntax;

WHILE (@@FETCH_STATUS = 0)
BEGIN
SET @sql = 'UPDATE dbo.DateTimeFormats
SET outputSample = ' + @syntax + '
WHERE styleID = ' + RTRIM(@style) + ';';

EXEC(@sql);

FETCH NEXT FROM c INTO @style, @syntax;
END

CLOSE c; DEALLOCATE c;

SELECT
styleID,
outputSample,
outputSyntax
FROM
dbo.DateTimeFormats
WHERE
styleID = COALESCE(@styleID, styleID);

DROP TABLE dbo.DateTimeFormats;
END
GO

EXEC dbo.help_DateTimeFormats;
EXEC dbo.help_DateTimeFormats @styleID = 112;

-- DROP PROCEDURE dbo.help_DateTimeFormats;

The output should look like this:

0 : Feb 22 2006 4:26PM ----- CONVERT(CHAR(19), CURRENT_TIMESTAMP, 0)
1 : 02/22/06 ----- CONVERT(CHAR(8), CURRENT_TIMESTAMP, 1)
2 : 06.02.22 ----- CONVERT(CHAR(8), CURRENT_TIMESTAMP, 2)
3 : 22/02/06 ----- CONVERT(CHAR(8), CURRENT_TIMESTAMP, 3)
4 : 22.02.06 ----- CONVERT(CHAR(8), CURRENT_TIMESTAMP, 4)
5 : 22-02-06 ----- CONVERT(CHAR(8), CURRENT_TIMESTAMP, 5)
6 : 22 Feb 06 ----- CONVERT(CHAR(9), CURRENT_TIMESTAMP, 6)
7 : Feb 22, 06 ----- CONVERT(CHAR(10), CURRENT_TIMESTAMP, 7)
8 : 16:26:08 ----- CONVERT(CHAR(8), CURRENT_TIMESTAMP, 8)
9 : Feb 22 2006 4:26:08:020PM ----- CONVERT(CHAR(26), CURRENT_TIMESTAMP, 9)
10 : 02-22-06 ----- CONVERT(CHAR(8), CURRENT_TIMESTAMP, 10)
11 : 06/02/22 ----- CONVERT(CHAR(8), CURRENT_TIMESTAMP, 11)
12 : 060222 ----- CONVERT(CHAR(6), CURRENT_TIMESTAMP, 12)
13 : 22 Feb 2006 16:26:08:020 ----- CONVERT(CHAR(24), CURRENT_TIMESTAMP, 13)
14 : 16:26:08:037 ----- CONVERT(CHAR(12), CURRENT_TIMESTAMP, 14)
20 : 2006-02-22 16:26:08 ----- CONVERT(CHAR(19), CURRENT_TIMESTAMP, 20)
21 : 2006-02-22 16:26:08.037 ----- CONVERT(CHAR(23), CURRENT_TIMESTAMP, 21)
22 : 02/22/06 4:26:08 PM ----- CONVERT(CHAR(20), CURRENT_TIMESTAMP, 22)
23 : 2006-02-22 ----- CONVERT(CHAR(10), CURRENT_TIMESTAMP, 23)
24 : 16:26:08 ----- CONVERT(CHAR(8), CURRENT_TIMESTAMP, 24)
25 : 2006-02-22 16:26:08.037 ----- CONVERT(CHAR(23), CURRENT_TIMESTAMP, 25)
100 : Feb 22 2006 4:26PM ----- CONVERT(CHAR(19), CURRENT_TIMESTAMP, 100)
101 : 02/22/2006 ----- CONVERT(CHAR(10), CURRENT_TIMESTAMP, 101)
102 : 2006.02.22 ----- CONVERT(CHAR(10), CURRENT_TIMESTAMP, 102)
103 : 22/02/2006 ----- CONVERT(CHAR(10), CURRENT_TIMESTAMP, 103)
104 : 22.02.2006 ----- CONVERT(CHAR(10), CURRENT_TIMESTAMP, 104)
105 : 22-02-2006 ----- CONVERT(CHAR(10), CURRENT_TIMESTAMP, 105)
106 : 22 Feb 2006 ----- CONVERT(CHAR(11), CURRENT_TIMESTAMP, 106)
107 : Feb 22, 2006 ----- CONVERT(CHAR(12), CURRENT_TIMESTAMP, 107)
108 : 16:26:08 ----- CONVERT(CHAR(8), CURRENT_TIMESTAMP, 108)
109 : Feb 22 2006 4:26:08:067PM ----- CONVERT(CHAR(26), CURRENT_TIMESTAMP, 109)
110 : 02-22-2006 ----- CONVERT(CHAR(10), CURRENT_TIMESTAMP, 110)
111 : 2006/02/22 ----- CONVERT(CHAR(10), CURRENT_TIMESTAMP, 111)
112 : 20060222 ----- CONVERT(CHAR(8), CURRENT_TIMESTAMP, 112)
113 : 22 Feb 2006 16:26:08:067 ----- CONVERT(CHAR(24), CURRENT_TIMESTAMP, 113)
114 : 16:26:08:067 ----- CONVERT(CHAR(12), CURRENT_TIMESTAMP, 114)
120 : 2006-02-22 16:26:08 ----- CONVERT(CHAR(19), CURRENT_TIMESTAMP, 120)
121 : 2006-02-22 16:26:08.080 ----- CONVERT(CHAR(23), CURRENT_TIMESTAMP, 121)
126 : 2006-02-22T16:26:08.080 ----- CONVERT(CHAR(23), CURRENT_TIMESTAMP, 126)
127 : 2006-02-22T16:26:08.080 ----- CONVERT(CHAR(23), CURRENT_TIMESTAMP, 127)
130 : 24 ???? 1427 4:26:08:080PM ----- CONVERT(CHAR(32), CURRENT_TIMESTAMP, 130)
131 : 24/01/1427 4:26:08:080PM ----- CONVERT(CHAR(25), CURRENT_TIMESTAMP, 131)

Debug while Running a Test in an ASP.NET Solution

2009-05-10T21:25:00.000-07:00

How to: Debug while Running a Test in an ASP.NET Solution

You can debug both unit tests and Web tests that you are using to test ASP.NET Web projects. You can also debug your ASP.NET production code while a test is running.

However, when you are testing ASP.NET code, the test code does not run in the typical way, under the VSTestHost process. Instead, it runs in either the IIS process, or if your Web site is file-based, in an ASP.NET Development Server process. Because the test runs in other than the typical test process, choosing the Debug Selection option in the Test View window or the Debug Checked tests option in the Test List Editor does not debug while the test is running.

Similarly, ASP.NET production code cannot be stepped into unless debugging is enabled and the debugger is attached to the ASP.NET Development Server or the IIS process.

In each of the following procedures, you create an ASP.NET Web site project by using the New Web Site dialog box. In this dialog box, you use the Location list box to choose a location for the Web site. This choice determines the process to which you will later attach the debugger, and the steps that you follow to debug while running a test in an ASP.NET solution. The two options are IIS and ASP.NET Development Server.

--> Debugging While Running on IIS
--> Debugging While Running on ASP.NET Development Server

Debugging While Running on IIS
In the following procedure, you will attach the debugger to a process. The name of the process depends on the operating system you are using, because the operating system determines the version of IIS that is installed. The following table shows what process is used on each operating system. For an operating system in the first column, use the name of the process specified in the third column in the Available Processes section of the Attach to Process dialog box.

Operating System
Host process
ASP.NET Process name

Windows Server 2003
IIS 6.0
w3wp.exe

Windows XP
IIS 5.1
aspnet_wp.exe

Windows 2000
IIS 5.0
aspnet_wp.exe

To debug while running an ASP.NET test on IIS
Create an ASP.NET Web site project that you want to test, and an ASP.NET unit test to test it.

When you create this Web site project, in the New Web Site dialog box, select HTTP or FTP as the Location. This guarantees that the host process will be IIS.

For more information, see How to: Create an ASP.NET Unit Test.

Enable debugging in the ASP.NET Web project. To do this, edit the project's Web configuration file. If your project already has a Web.config file, go to step 4. If not, add one now: Right-click the Web site project in your solution, and then click Add New Item.

The Add New Item dialog box is displayed.

In the Add New Item dialog box, click Web Configuration File and then click Add.

A Web.config file is added to your Web site project. For more information about how to use Web.config files, see How to: Enable Debugging for ASP.NET Applications.

In the Web.config file, change the line that reads to .

(Optional) Set breakpoints in the ASP.NET unit test and in the production code for your Web site.

Attach the debugger to the IIS process. To do this, click Debug and then click Attach to Process.

The Attach to Process dialog box is displayed.

Under Available Processes, locate the name of the process to which you want to attach the debugger.

If the process you need is not displayed, you can display more processes that are running. To do this, check Show processes from all users and Show processes in all sessions.

Under Available Processes, click the name of the process and then click Attach.

If the process to which you have to attach is not running, click Cancel and then start the process. To do this, in Solution Explorer, right-click the Web site project and then click View in Browser. Next, click Debug and then click Attach to Process one more time; the process has started running and is displayed under Available Processes. Click the process name and then click Attach.

Start your test.

To do this, in the Test View window, right-click the test your want to debug and select Debug Selection.

Note:
When running tests, you can choose Run Selection instead of Debug Selection. The difference is that if you choose Debug Selection, the debugger automatically detaches after the test finishes, but if you choose Run Selection, the debugger stays attached. You may find Run Selection more useful, especially if you plan to rerun the test several times while debugging, and you do not want to have to reattach the process every time. If you have chosen Run Selection, to detach the process when you have finished debugging, choose Stop Debugging from the Debug menu or press Shift+F5.

Debugging While Running on ASP.NET Development Server
To debug while running a test on ASP.NET Development Server
Create an ASP.NET Web site project that you want to test, and an ASP.NET unit test to test it.

When you create this Web site project, in the New Web Site dialog box, select File System as the Location. This guarantees that the host process will be ASP.NET Development Server.

For more information, see How to: Create an ASP.NET Unit Test.

Enable debugging in the ASP.NET Web project. To do this, edit the project's Web configuration file. If your project already has a Web.config file, go to step 4. If not, add one now: Right-click the Web site project in your solution, and then click Add New Item.

The Add New Item dialog box is displayed.

In the Add New Item dialog box, click Web Configuration File and then click Add.

A Web.config file is added to your Web site project. For more information about how to use Web.config files, see How to: Enable Debugging for ASP.NET Applications.

In the Web.config file, change the line that reads to .

Add the statement System.Diagnostics.Debugger.Break() to the beginning of your ASP.NET unit test.

Note:
Breakpoints in your code will be hit only if they follow this System.Diagnostics.Debugger.Break() statement.

Note:
In C++, this statement is System::Diagnostics::Debugger::Break(). For information about how to use unit tests in Visual C++, see Unit Tests and C++.

Set breakpoints in the ASP.NET unit test and in the production code for your Web site.

Start your test.

To do this, in the Test View window, right-click the test you want to run and select Run Selection.

As soon as the test starts to run, a dialog box appears. This dialog box indicates that the program has encountered a breakpoint.

Click Debug, choose the instance of Visual Studio that has your solution loaded, and then click Yes.

Visual Studio will attach to the process, with execution paused at the System.Diagnostics.Debugger.Break() statement. You can choose Continue from the Debug menu or press F5 to allow execution to continue to your next breakpoint.

Page life cycle of asp.net 2.0

2009-05-02T03:07:00.000-07:00

Page Event	Typical Use
PreInit	Use this event for the following: Check the href="http://msdn.microsoft.com/en-us/library/system.web.ui.page.ispostback.aspx" onclick="javascript:Track('ctl00_mainContentContainer_cpe74103_c\|ctl00_mainContentContainer_ctl82',this);" style="color: rgb(0,51,204); text-decoration: none">IsPostBack property to determine whether this is the first time the page is being processed. Create or re-create dynamic controls. Set a master page dynamically. Set the href="http://msdn.microsoft.com/en-us/library/system.web.ui.page.theme.aspx" onclick="javascript:Track('ctl00_mainContentContainer_cpe74103_c\|ctl00_mainContentContainer_ctl83',this);" style="color: rgb(0,51,204); text-decoration: none">Theme property dynamically. Read or set profile property values. Note: If the request is a postback, the values of the controls have not yet been restored from view state. If you set a control property at this stage, its value might be overwritten in the next event.
Init	Raised after all controls have been initialized and any skin settings have been applied. Use this event to read or initialize control properties.
InitComplete	Raised by the href="http://msdn.microsoft.com/en-us/library/system.web.ui.page.aspx" onclick="javascript:Track('ctl00_mainContentContainer_cpe74103_c\|ctl00_mainContentContainer_ctl88',this);" style="color: rgb(0,51,204); text-decoration: none">Page object. Use this event for processing tasks that require all initialization be complete.
PreLoad	Use this event if you need to perform processing on your page or control before the Load event. Before the href="http://msdn.microsoft.com/en-us/library/system.web.ui.page.aspx" onclick="javascript:Track('ctl00_mainContentContainer_cpe74103_c\|ctl00_mainContentContainer_ctl91',this);" style="color: rgb(0,51,204); text-decoration: none">Page instance raises this event, it loads view state for itself and all controls, and then processes any postback data included with the onclick="javascript:Track('ctl00_mainContentContainer_cpe74103_c\|ctl00_mainContentContainer_ctl92',this);" style="color: rgb(0,51,204); text-decoration: none">Request instance.
Load	The href="http://msdn.microsoft.com/en-us/library/system.web.ui.page.aspx" onclick="javascript:Track('ctl00_mainContentContainer_cpe74103_c\|ctl00_mainContentContainer_ctl94',this);" style="color: rgb(0,51,204); text-decoration: none">Page calls the href="http://msdn.microsoft.com/en-us/library/system.web.ui.control.onload.aspx" onclick="javascript:Track('ctl00_mainContentContainer_cpe74103_c\|ctl00_mainContentContainer_ctl95',this);" style="color: rgb(0,51,204); text-decoration: none">OnLoad event method on the href="http://msdn.microsoft.com/en-us/library/system.web.ui.page.aspx" onclick="javascript:Track('ctl00_mainContentContainer_cpe74103_c\|ctl00_mainContentContainer_ctl96',this);" style="color: rgb(0,51,204); text-decoration: none">Page, then recursively does the same for each child control, which does the same for each of its child controls until the page and all controls are loaded. Use the href="http://msdn.microsoft.com/en-us/library/system.web.ui.control.onload.aspx" onclick="javascript:Track('ctl00_mainContentContainer_cpe74103_c\|ctl00_mainContentContainer_ctl97',this);" style="color: rgb(0,51,204); text-decoration: none">OnLoad event method to set properties in controls and establish database connections.
Control events	Use these events to handle specific control events, such as a onclick="javascript:Track('ctl00_mainContentContainer_cpe74103_c\|ctl00_mainContentContainer_ctl98',this);" style="color: rgb(0,51,204); text-decoration: none">Button control's href="http://msdn.microsoft.com/en-us/library/system.web.ui.webcontrols.button.click.aspx" onclick="javascript:Track('ctl00_mainContentContainer_cpe74103_c\|ctl00_mainContentContainer_ctl99',this);" style="color: rgb(0,51,204); text-decoration: none">Clickevent or a href="http://msdn.microsoft.com/en-us/library/system.web.ui.webcontrols.textbox.aspx" onclick="javascript:Track('ctl00_mainContentContainer_cpe74103_c\|ctl00_mainContentContainer_ctl100',this);" style="color: rgb(0,51,204); text-decoration: none">TextBox control's href="http://msdn.microsoft.com/en-us/library/system.web.ui.mobilecontrols.textbox.textchanged.aspx" onclick="javascript:Track('ctl00_mainContentContainer_cpe74103_c\|ctl00_mainContentContainer_ctl101',this);" style="color: rgb(0,51,204); text-decoration: none">TextChanged event. Note: In a postback request, if the page contains validator controls, check the href="http://msdn.microsoft.com/en-us/library/system.web.ui.page.isvalid.aspx" onclick="javascript:Track('ctl00_mainContentContainer_ctl102\|ctl00_mainContentContainer_ctl104',this);" style="color: rgb(0,51,204); text-decoration: none">IsValidproperty of the href="http://msdn.microsoft.com/en-us/library/system.web.ui.page.aspx" onclick="javascript:Track('ctl00_mainContentContainer_ctl102\|ctl00_mainContentContainer_ctl105',this);" style="color: rgb(0,51,204); text-decoration: none">Page and of individual validation controls before performing any processing.
LoadComplete	Use this event for tasks that require that all other controls on the page be loaded.
PreRender	Before this event occurs: The href="http://msdn.microsoft.com/en-us/library/system.web.ui.page.aspx" onclick="javascript:Track('ctl00_mainContentContainer_cpe74103_c\|ctl00_mainContentContainer_ctl108',this);" style="color: rgb(0,51,204); text-decoration: none">Page object calls href="http://msdn.microsoft.com/en-us/library/system.web.ui.control.ensurechildcontrols.aspx" onclick="javascript:Track('ctl00_mainContentContainer_cpe74103_c\|ctl00_mainContentContainer_ctl109',this);" style="color: rgb(0,51,204); text-decoration: none">EnsureChildControls class="Apple-converted-space"> for each control and for the page. Each data bound control whose id="ctl00_mainContentContainer_ctl110" href="http://msdn.microsoft.com/en-us/library/system.web.ui.webcontrols.databoundcontrol.datasourceid.aspx" onclick="javascript:Track('ctl00_mainContentContainer_cpe74103_c\|ctl00_mainContentContainer_ctl110',this);" style="color: rgb(0,51,204); text-decoration: none">DataSourceID class="Apple-converted-space"> property is set calls its href="http://msdn.microsoft.com/en-us/library/system.web.ui.control.databind.aspx" onclick="javascript:Track('ctl00_mainContentContainer_cpe74103_c\|ctl00_mainContentContainer_ctl111',this);" style="color: rgb(0,51,204); text-decoration: none">DataBind method. For more information, see Data Binding Events for Data-Bound Controls later in this topic. The href="http://msdn.microsoft.com/en-us/library/system.web.ui.control.prerender.aspx" onclick="javascript:Track('ctl00_mainContentContainer_cpe74103_c\|ctl00_mainContentContainer_ctl112',this);" style="color: rgb(0,51,204); text-decoration: none">PreRender event occurs for each control on the page. Use the event to make final changes to the contents of the page or its controls.
SaveStateComplete	Before this event occurs, href="http://msdn.microsoft.com/en-us/library/system.web.ui.control.viewstate.aspx" onclick="javascript:Track('ctl00_mainContentContainer_cpe74103_c\|ctl00_mainContentContainer_ctl114',this);" style="color: rgb(0,51,204); text-decoration: none">ViewState has been saved for the page and for all controls. Any changes to the page or controls at this point will be ignored. Use this event perform tasks that require view state to be saved, but that do not make any changes to controls.
Render	This is not an event; instead, at this stage of processing, the onclick="javascript:Track('ctl00_mainContentContainer_cpe74103_c\|ctl00_mainContentContainer_ctl116',this);" style="color: rgb(0,51,204); text-decoration: none">Page object calls this method on each control. All ASP.NET Web server controls have a href="http://msdn.microsoft.com/en-us/library/system.web.ui.control.render.aspx" onclick="javascript:Track('ctl00_mainContentContainer_cpe74103_c\|ctl00_mainContentContainer_ctl117',this);" style="color: rgb(0,51,204); text-decoration: none">Render method that writes out the control's markup that is sent to the browser. If you create a custom control, you typically override this method to output the control's markup. However, if your custom control incorporates only standard ASP.NET Web server controls and no custom markup, you do not need to override the onclick="javascript:Track('ctl00_mainContentContainer_cpe74103_c\|ctl00_mainContentContainer_ctl118',this);" style="color: rgb(0,51,204); text-decoration: none">Rendermethod. For more information, see href="http://msdn.microsoft.com/en-us/library/zt27tfhy.aspx" onclick="javascript:Track('ctl00_mainContentContainer_cpe74103_c\|ctl00_mainContentContainer_ctl119',this);" style="color: rgb(0,51,204); text-decoration: none">Developing Custom ASP.NET Server Controls. A user control (an .ascx file) automatically incorporates rendering, so you do not need to explicitly render the control in code.
Unload	This event occurs for each control and then for the page. In controls, use this event to do final cleanup for specific controls, such as closing control-specific database connections. For the page itself, use this event to do final cleanup work, such as closing open files and database connections, or finishing up logging or other request-specific tasks. Note: During the unload stage, the page and its controls have been rendered, so you cannot make further changes to the response stream. If you attempt to call a method such as the class="input" style="font-weight: 700">Response.Write method, the page will throw an exception.

Configure SQL Server to Store ASP.NET Session State

2009-05-01T18:34:00.000-07:00

Modify the Web.config File of Your Application
To implement ASP.NET SQL Server mode session state management, you must modify the <sessionState> element of your application's Web.config file as follows:

1. Set the mode attribute of the <sessionState> element to SQLServer to indicate that session state is stored in SQL Server.
2. Set the sqlConnectionString attribute to specify the connection string for SQL Server. For example:
sqlConnectionString="data source=MySQLServer;user id=<username>;password=<strongpassword>"

Note The user, <user name>, must have permissions to perform this operation on the database.

The modified <sessionState> element should appear as follows:
<sessionState
mode="SQLServer"
sqlConnectionString="data source=127.0.0.1;user id=<username>;password=<strongpassword>"
cookieless="false"
timeout="20"
/>

Note Ensure that you use the correct case when you specify the <sessionState> element and the associated attribute values. This code is case sensitive.

Troubleshooting
If you do not stop the w3svc process before you run the UninstallSqlState.sql script file, you receive the following error message:

Cannot drop the database 'ASPState' because it is currently in use

--> If entries in the ASPStateTempSessions table are not removed after the related sessions expire, make sure that the SQL Server agent is running. You can implement this functionality through stored procedures that are scheduled through jobs in SQL Server. The SQL Server agent manages these jobs.
--> When you use the default InstallSqlState.sql and UninstallSqlState.sql script files to configure ASP.NET SQL Server mode session state management, note that these files add the ASPStateTempSessions and the ASPStateTempApplications tables to the tempdb database in SQL Server by default. Furthermore, if you restart SQL Server, you lose the session state data that was stored in the ASPStateTempSessions and the ASPStateTempApplications tables.For additional information about how to run alternative scripts to configure persistent SQL Server session state management so that the session data is not lost when you restart the server, click the article number below to view the article in the Microsoft Knowledge Base:

311209 HOW TO: Configure ASP.NET for Persistent SQL Server Session State Management

Encrypting and DeCrypting a string with a key password

2009-04-27T22:53:00.000-07:00

using System.Security.Cryptography;

private static string EncryptString(string Message, string Passphrase)
{
byte[] Results;
System.Text.UTF8Encoding UTF8 = new System.Text.UTF8Encoding();

// Step 1. We hash the passphrase using MD5
// We use the MD5 hash generator as the result is a 128 bit byte array
// which is a valid length for the TripleDES encoder we use below

MD5CryptoServiceProvider HashProvider = new MD5CryptoServiceProvider();
byte[] TDESKey = HashProvider.ComputeHash(UTF8.GetBytes(Passphrase));

// Step 2. Create a new TripleDESCryptoServiceProvider object
TripleDESCryptoServiceProvider TDESAlgorithm = new TripleDESCryptoServiceProvider();

// Step 3. Setup the encoder
TDESAlgorithm.Key = TDESKey;
TDESAlgorithm.Mode = CipherMode.ECB;
TDESAlgorithm.Padding = PaddingMode.PKCS7;

// Step 4. Convert the input string to a byte[]
byte[] DataToEncrypt = UTF8.GetBytes(Message);

// Step 5. Attempt to encrypt the string
try
{
ICryptoTransform Encryptor = TDESAlgorithm.CreateEncryptor();
Results = Encryptor.TransformFinalBlock(DataToEncrypt, 0, DataToEncrypt.Length);
}
finally
{
// Clear the TripleDes and Hashprovider services of any sensitive information
TDESAlgorithm.Clear();
HashProvider.Clear();
}

// Step 6. Return the encrypted string as a base64 encoded string
return Convert.ToBase64String(Results);
}

private static string DecryptString(string Message, string Passphrase)
{
byte[] Results;
System.Text.UTF8Encoding UTF8 = new System.Text.UTF8Encoding();

// Step 1. We hash the passphrase using MD5
// We use the MD5 hash generator as the result is a 128 bit byte array
// which is a valid length for the TripleDES encoder we use below

MD5CryptoServiceProvider HashProvider = new MD5CryptoServiceProvider();
byte[] TDESKey = HashProvider.ComputeHash(UTF8.GetBytes(Passphrase));

// Step 2. Create a new TripleDESCryptoServiceProvider object
TripleDESCryptoServiceProvider TDESAlgorithm = new TripleDESCryptoServiceProvider();

// Step 3. Setup the decoder
TDESAlgorithm.Key = TDESKey;
TDESAlgorithm.Mode = CipherMode.ECB;
TDESAlgorithm.Padding = PaddingMode.PKCS7;

// Step 4. Convert the input string to a byte[]
byte[] DataToDecrypt = Convert.FromBase64String(Message);

// Step 5. Attempt to decrypt the string
try
{
ICryptoTransform Decryptor = TDESAlgorithm.CreateDecryptor();
Results = Decryptor.TransformFinalBlock(DataToDecrypt, 0, DataToDecrypt.Length);
}
finally
{
// Clear the TripleDes and Hashprovider services of any sensitive information
TDESAlgorithm.Clear();
HashProvider.Clear();
}

// Step 6. Return the decrypted string in UTF8 format
return UTF8.GetString(Results);
}
public static void Main(string[] args)
{
// The message to encrypt.
string Msg = "This world is round, not flat, don't believe them!";
string Password = "secret";

string EncryptedString = EncryptString(Msg, Password);
string DecryptedString = DecryptString(EncryptedString, Password);
}

validating textbox to enter only numeric values using javascript

2009-04-14T02:30:00.000-07:00

function isNumberKey(evt)
{
var charCode = (evt.which) ? evt.which : event.keyCode
if (charCode > 31 && (charCode < 48 || charCode > 57))
return false;

return true;
}

<asp:TextBox ID="txtOnlyNumbers" onkeypress="return isNumberKey(event)" runat="server" TabIndex="00001"></asp:TextBox>

Select and UnSelect Checkbox in Gridview using Javascript

2009-04-09T23:47:00.000-07:00

In Valid Postback in asp.net

2009-04-09T23:29:00.000-07:00

Invalid Post back or callback argument . Event validations enabled usingin configeration

In .aspx file

<%@ Page Language="C#" AutoEventWireup="true" EnableEventValidation="false" CodeFile="Default5.aspx.cs" Inherits="Default5" %>

or

In web.config file

<pages enableEventValidation="false">

opening child web page and tranfer data between pages in javascript

2009-03-29T21:22:00.000-07:00

2009-03-26T03:52:00.001-07:00

Javascript validations in asp.net

2009-03-26T03:35:00.000-07:00

In this just make a form as follows:

Name : <asp:TextBox ID="txtName" />
Email : <asp:TextBox ID="txtEmail" />
Web URL : <asp:TextBox ID="txtWebUrl" />
Zip : <asp:TextBox ID="txtZip" />
<asp:Button ID="btnSubmit" OnClientClick=" return validate()"runat="server" Text="Submit" />

Now on the source code of this form in script tag write the following code:

And in code behind file just write the below code.

Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load
btnSubmit.Attributes.Add("onclick", "return validate()")
End Sub

Now you will get a form with proper validation.

encrypting and decrypting data or password in c#

2009-03-26T03:07:00.000-07:00

Encrypting and decrypting data

Encryption software

I am seeing a lot of questions people are asking on how to do encryption/decryption. To help those people I have written a simple class encorporating several encryption/decryption functions:

byte[] Encrypt(byte[] clearData, byte[] Key, byte[] IV) - encrypts a byte array with a key and an IV and returns a byte array;
string Encrypt(string clearText, string Password) - encrypts a string with a password and returns a string;
byte[] Encrypt(byte[] clearData, string Password) - encrypts a byte array with a password and returns a byte array;
void Encrypt(string fileIn, string fileOut, string Password) - encrypts a file with a password and writes the encrypted bytes into another file.

For each of those there is also a corresponding Decrypt function. The Main method is a simpletesting method that exercises some of those functions. The 2nd and the 3rd Encrypt functions call into the 1st function, so you will need to carry the 1st one around if you are using the 2nd or the 3rd. The last Encrypt function (the one that works with files) is standalone. I made it operate in a stream-like manner, without reading the whole file into memory, which makes it possible to encrypt/decrypt gigabytes of data without going out of memory space.

I am using Rijndael algorithm in this sample. The reason for this is that it is 100% implemented in managed code in our libraries, so it does not rely on CryptoAPI or any encryption packs and will work everywhere. If you need performance I would suggest replacing it with TripleDES (it is a one line change), and if you do, also do not forget to change the IV size to 8 bytes and the Key size to 16 bytes.

I have tried to document the code well, and I would like to encourage you to read through it and understand how it works, it should be pretty easy. You can also grab the whole thing, stick it into a .cs file and it should compile. If you run it you will see it make some test encryption/decryption roundtrip; you can also provide a file name as a parameter, and it will encrypt the file into a .encrypted file and then decrypt it back into a .decrypted.

Enjoy!

P.S. A crypto-related FAQ can be found at http://www.gotdotnet.com/team/clr/cryptofaq.htm and there is a good chapter on how to use crypto in "Writing Secure Code" by Michael Howard (2nd edition came out recently). For in depth information on crypto in general "Applied Cryptography" by Bruce Schneier is an excellent resource.

// This sample code is provided "AS IS" with no warranties, and confers no rights.

// ATTENTION: This sample is designed to be more of a tutorial rather than something

// you can copy and paste in the production code!

// See the topic on "making it industry strength" in the blog.

using System;

using System.IO;

using System.Security.Cryptography;

// Sample encrypt/decrypt functions

// Parameter checks and error handling are ommited for better readability

public class EncDec

{

// Encrypt a byte array into a byte array using a key and an IV

public static byte[] Encrypt(byte[] clearData, byte[] Key, byte[] IV)

{

// Create a MemoryStream that is going to accept the encrypted bytes

MemoryStream ms = new MemoryStream();

// Create a symmetric algorithm.

// We are going to use Rijndael because it is strong and available on all platforms.

// You can use other algorithms, to do so substitute the next line with something like

// TripleDES alg = TripleDES.Create();

Rijndael alg = Rijndael.Create();

// Now set the key and the IV.

// We need the IV (Initialization Vector) because the algorithm is operating in its default

// mode called CBC (Cipher Block Chaining). The IV is XORed with the first block (8 byte)

// of the data before it is encrypted, and then each encrypted block is XORed with the

// following block of plaintext. This is done to make encryption more secure.

// There is also a mode called ECB which does not need an IV, but it is much less secure.

alg.Key = Key;

alg.IV = IV;

// Create a CryptoStream through which we are going to be pumping our data.

// CryptoStreamMode.Write means that we are going to be writing data to the stream

// and the output will be written in the MemoryStream we have provided.

CryptoStream cs = new CryptoStream(ms, alg.CreateEncryptor(),CryptoStreamMode.Write);

// Write the data and make it do the encryption

cs.Write(clearData, 0, clearData.Length);

// Close the crypto stream (or do FlushFinalBlock).

// This will tell it that we have done our encryption and there is no more data coming in,

// and it is now a good time to apply the padding and finalize the encryption process.

cs.Close();

// Now get the encrypted data from the MemoryStream.

// Some people make a mistake of using GetBuffer() here, which is not the right way.

byte[] encryptedData = ms.ToArray();

return encryptedData;

}

// Encrypt a string into a string using a password

// Uses Encrypt(byte[], byte[], byte[])

public static string Encrypt(string clearText, string Password)

{

// First we need to turn the input string into a byte array.

byte[] clearBytes = System.Text.Encoding.Unicode.GetBytes(clearText);

// Then, we need to turn the password into Key and IV

// We are using salt to make it harder to guess our key using a dictionary attack -

// trying to guess a password by enumerating all possible words.

PasswordDeriveBytes pdb = new PasswordDeriveBytes(Password,

new byte[] {0x49, 0x76, 0x61, 0x6e, 0x20, 0x4d, 0x65, 0x64, 0x76, 0x65, 0x64, 0x65, 0x76});

// Now get the key/IV and do the encryption using the function that accepts byte arrays.

// Using PasswordDeriveBytes object we are first getting 32 bytes for the Key

// (the default Rijndael key length is 256bit = 32bytes) and then 16 bytes for the IV.

// IV should always be the block size, which is by default 16 bytes (128 bit) for Rijndael.

// If you are using DES/TripleDES/RC2 the block size is 8 bytes and so should be the IV size.

// You can also read KeySize/BlockSize properties off the algorithm to find out the sizes.

byte[] encryptedData = Encrypt(clearBytes, pdb.GetBytes(32), pdb.GetBytes(16));

// Now we need to turn the resulting byte array into a string.

// A common mistake would be to use an Encoding class for that. It does not work

// because not all byte values can be represented by characters.

// We are going to be using Base64 encoding that is designed exactly for what we are

// trying to do.

return Convert.ToBase64String(encryptedData);

}

// Encrypt bytes into bytes using a password

// Uses Encrypt(byte[], byte[], byte[])

public static byte[] Encrypt(byte[] clearData, string Password)

{

// We need to turn the password into Key and IV.