Hello.

Some times we came around a problem where we needed to know the difference between 2 dates in javascript. Also, in some cases we need to validate a date against another date. In these cases we search in the internet for a suitable function which takes 2 dates as arguments and finally let us know the difference between those.

Here, I have found so many scripts, but some of which are not working and some I do not understand and some does not provide us a simple result as we want. So, I have taken reference of those scripts and marged them into a suitable one to produce a new script which is giving us output as I wanted it to do.

Here it is:

First, we need a html form and 2 input type text fileds to enter 2 dates. Here some may wanted to add the time also.

<form onSubmit=”return checkDate(this);”>
<table>
 <tr>
  <td>
   <pre>
   First Date:<input type=”text” name=”firstdate” value=”" size=10 maxlength=10> (MM/DD/YYYY format)<br/>
   Time: <input type=”text” name=”firsttime” value=”" size=10 maxlength=10> (HH:MM:SS format)<br/>
   
   Second Date: Date: <input type=”text” name=”seconddate” value=”" size=10 maxlength=10> (MM/DD/YYYY format)<br/>
   Time: <input type=”text” name=”secondtime” value=”" size=10 maxlength=10> (HH:MM:SS format)<br/>
   
   <center><input type=”submit” value=”Get Difference!”></center>
   </pre>
  </td>
 </tr>
</table>
</form>

So, this form has 2 text fileds for dates and 2 other for times, and a button to get the difference.

This form takes date in “MM/DD/YYYY” format and time in “HH:MM:SS” format.

We can add a function to validate these dates or we can simply specify the date text fileds as readonly and add a suitable javascript calendar to input correct dates. (Like I have used in : http://www.hotelsagorika.com/reservation.html)

Now after clicking the submit button we need to add suitable code to check the dates:

So, we will put this script into the HEAD section of the HTML.

<script type=”text/javascript”>

function isValidDate(dateStr) {
 // Date validation Function 
 // Checks For the following valid Date formats:
 // MM/DD/YY MM/DD/YYYY MM-DD-YY MM-DD-YYYY
 
 var datePat = /^(\d{1,2})(\/|-)(\d{1,2})\2(\d{4})$/; // requires 4 digit Year
 
 var matchArray = dateStr.match(datePat); // Is the format ok?
 if (matchArray == Null) {
  alert(dateStr + ” Date is not in a valid format.”)
  return false;
 }
 
 Month = matchArray[1]; // parse Date into variables
 Day = matchArray[3];
 Year = matchArray[4];
 
 if (Month < 1 || Month > 12) { // check Month range
  alert(“Month must be between 1 and 12.”);
  return false;
 }
 
 if (Day < 1 || Day > 31) {
  alert(“Day must be between 1 and 31.”);
  return false;
 }
 
 if ((Month==4 || Month==6 || Month==9 || Month==11) && Day==31) {
  alert(“Month “+Month+” doesn’t have 31 days!”)
  return false;
 }
 
 if (Month == 2) { // check For february 29th
  var isleap = (Year % 4 == 0 && (Year % 100 != 0 || Year % 400 == 0));
  if (Day>29 || (Day==29 && !isleap)) {
   alert(“February ” + Year + ” doesn’t have ” + Day + ” days!”);
   return false;
  }
 }
 return true;
}

function isValidTime(timeStr) {
 // Checks if time Is In HH:MM:SS AM/PM format.
 // The seconds And AM/PM are optional.
 
 var timePat = /^(\d{1,2}):(\d{2})(:(\d{2}))?(\s?(AM|am|PM|pm))?$/;
 
 var matchArray = timeStr.match(timePat);
 if (matchArray == Null) {
  alert(“Time is not in a valid format.”);
  return false;
 }
 
 Hour = matchArray[1];
 Minute = matchArray[2];
 Second = matchArray[4];
 ampm = matchArray[6];
 
 if (Second==”") { Second = null; }
 if (ampm==”") { ampm = Null }
 
 if (Hour < 0 || Hour > 23) {
  alert(“Hour must be between 1 and 12. (or 0 and 23 for military time)”);
  return false;
 }
 if (Hour <= 12 && ampm == Null) {
  if (confirm(“Please indicate which time format you are using. OK = Standard Time, CANCEL = Military Time”)) {
   alert(“You must specify AM or PM.”);
   return false;
  }
 }
 if (Hour > 12 && ampm != Null) {
  alert(“You can’t specify AM or PM for military time.”);
  return false;
 }
 if (Minute < 0 || Minute > 59) {
  alert (“Minute must be between 0 and 59.”);
  return false;
 }
 if (Second != Null && (Second < 0 || Second > 59)) {
  alert (“Second must be between 0 and 59.”);
  return false;
 }
 return true;
}

function checkDate(dateform) {
 date1 = new Date();
 date2 = new Date();
 diff = new Date();
 
 if (isValidDate(dateform.firstdate.value) && isValidTime(dateform.firsttime.value)) { // Validates first Date
  date1temp = new Date(dateform.firstdate.value + ” ” + dateform.firsttime.value);
  date1.setTime(date1temp.getTime());
 }
 else return false; // otherwise exits
 
 if (isValidDate(dateform.seconddate.value) && isValidTime(dateform.secondtime.value)) { // Validates Second Date
  date2temp = new Date(dateform.seconddate.value + ” ” + dateform.secondtime.value);
  date2.setTime(date2temp.getTime());
 }
 else return false; // otherwise exits
 
 // sets difference Date To difference of first Date And Second Date
 
 diff.setTime(Math.abs(date1.getTime() – date2.getTime()));
 
 timediff = diff.getTime();
 
 weeks = Math.floor(timediff / (1000 * 60 * 60 * 24 * 7));
 timediff -= weeks * (1000 * 60 * 60 * 24 * 7);
 
 days = Math.floor(timediff / (1000 * 60 * 60 * 24));
 timediff -= days * (1000 * 60 * 60 * 24);
 
 hours = Math.floor(timediff / (1000 * 60 * 60));
 timediff -= hours * (1000 * 60 * 60);
 
 mins = Math.floor(timediff / (1000 * 60));
 timediff -= mins * (1000 * 60);
 
 secs = Math.floor(timediff / 1000);
 timediff -= secs * 1000;
 
 alert(“Difference = ” + weeks + ” weeks, ” + days + ” days, ” + hours + ” hours, ” + mins + ” minutes, and ” + secs + ” seconds”);

 return false; // form should never submit, returns False
}

</script>

If you have specified the text fileds as read only and added a calendar, then you do not need the validattion methods, then the script will look like:

<script type=”text/javascript”>

function checkDate(dateform) {
 date1 = new Date();
 date2 = new Date();
 diff = new Date();
 
 date1temp = new Date(dateform.firstdate.value + ” ” + dateform.firsttime.value);

//If you do not need the time then you can replace the above line with this
// date1temp = new Date(dateform.firstdate.value + ” 00:00:00″);

 date1.setTime(date1temp.getTime());
  
 date2temp = new Date(dateform.seconddate.value + ” ” + dateform.secondtime.value);

//If you do not need the time then you can replace the above line with this
// date2temp = new Date(dateform.seconddate.value + ” 00:00:00″);

 date2.setTime(date2temp.getTime());
 
 // sets difference Date To difference of first Date And Second Date
 
 diff.setTime(Math.abs(date1.getTime() – date2.getTime()));
 
 timediff = diff.getTime();
 
 weeks = Math.floor(timediff / (1000 * 60 * 60 * 24 * 7));
 timediff -= weeks * (1000 * 60 * 60 * 24 * 7);
 
 days = Math.floor(timediff / (1000 * 60 * 60 * 24));
 timediff -= days * (1000 * 60 * 60 * 24);
 
 hours = Math.floor(timediff / (1000 * 60 * 60));
 timediff -= hours * (1000 * 60 * 60);
 
 mins = Math.floor(timediff / (1000 * 60));
 timediff -= mins * (1000 * 60);
 
 secs = Math.floor(timediff / 1000);
 timediff -= secs * 1000;
 
 alert(“Difference = ” + weeks + ” weeks, ” + days + ” days, ” + hours + ” hours, ” + mins + ” minutes, and ” + secs + ” seconds”);

 return false; // form should never submit, returns False
}

</script>

Now, suppose we want to know if the second date is after the first date or vice versa, i.e. if the first date is 30 th October, 2008 and seconda date is 02 nd November, 2008 then it will accept the dates otherwise, like if the 1st date is 28 th October 2008 and the second is 25th October 2008, it will not accept.

So, wee need to modify the above function slightly:

function checkDate(dateform) {
 date1 = new Date();
 date2 = new Date();
 diff = new Date();
 
 if (isValidDate(dateform.firstdate.value) && isValidTime(dateform.firsttime.value)) { // Validates first Date
  date1temp = new Date(dateform.firstdate.value + ” ” + dateform.firsttime.value);
  date1.setTime(date1temp.getTime());
 }
 else return false; // otherwise exits
 
 if (isValidDate(dateform.seconddate.value) && isValidTime(dateform.secondtime.value)) { // Validates Second Date
  date2temp = new Date(dateform.seconddate.value + ” ” + dateform.secondtime.value);
  date2.setTime(date2temp.getTime());
 }
 else return false; // otherwise exits
 
 // sets difference Date To difference of first Date And Second Date
 
 var dif = date2-date1;
 
 if(dif >=0){ // 2nd date is after the 1st date
  return true;
 }else{
  return false;
 }

}

Hope this article will help you understanding the date related issues better.

Integer Parsing in JavaScript. Some utility methods and tips

First Question will be like: How do I convert strings to numbers in JavaScript?

Answer: To convert a string to a number, use the JavaScript function parseFloat (for conversion to a floating-point number) or parseInt (for conversion to an integer).

parseFloat syntax: parseFloat('string')

How it works:

The argument of parseFloat must be a string or a string expression. The result of parseFloat is the number whose decimal representation was contained in that string (or the number found in the beginning of the string). If the string argument cannot be parsed as a decimal number, the results will be different in different browsers (either 0 or NaN).

Examples (comments in each line give the conversion results):

parseFloat(‘1.45kg’)  // 1.45
parseFloat(‘77.3′)    // 77.3
parseFloat(‘077.3′)   // 77.3
parseFloat(‘0×77.3′)  // 0
parseFloat(‘.3′)      // 0.3
parseFloat(‘0.1e6′)   // 100000

parseInt syntax: parseInt( 'string' [, base] )

How it works:

The first argument of parseInt must be a string or a string expression. The result returned by parseInt is an integer whose representation was contained in that string (or the integer found in the beginning of the string). The second argument (base), if present, specifies the base (radix) of the number whose string representation is contained in the string. The base argument can be any integer from 2 to 36.

If there is only one argument, the number base is detected according to the general JavaScript syntax for numbers. Strings that begin with 0x or -0x are parsed as hexadecimals; strings that begin with 0 or -0 are parsed as octal numbers. All other strings are parsed as decimal numbers.

If the string argument cannot be parsed as an integer, the results will be different in different browsers (either 0 or NaN).

Examples (comments in each line give the conversion results):

parseInt(‘123.45′)  // 123
parseInt(‘77′)      // 77
parseInt(‘077′,10)  // 77
parseInt(‘77′,8)    // 63  (= 7 + 7*8)
parseInt(‘077′)     // 63  (= 7 + 7*8)
parseInt(‘77′,16)   // 119 (= 7 + 7*16)
parseInt(‘0×77′)    // 119 (= 7 + 7*16)
parseInt(‘099′)     // 0 (9 is not an octal digit)
parseInt(‘99′,8)    // 0 or NaN, depending on the platform
parseInt(‘0.1e6′)   // 0
parseInt(‘ZZ’,36)   // 1295 (= 35 + 35*36)

So, if you try with “08” or “09” in parseInt(“value”), you may notice a strange thing: it treats “08″ or “09″ as 0.

This happens for all invalid inputs. The answer to this question lies in above examples.

An integer can be represented in three different ways: in base 8 (octal), base 10 (decimal) and base 16 (hexadecimal). A starting zero indicates an octal number, which can be anything from 0 to 7 but not 8 or 9. Similarly, a starting “0x” followed by a number that can indicates a hexadecimal number which can be anything from 0 to F.

The solution to the problem is very simple. Since “08″ means an octal number because of a starting 0, parseInt returns a zero for 8. Now, parseInt accepts a second optional parameter, which is the base of the number. You can forcefully tell it to treat the number as a decimal one by sending a second parameter 10.

Var _num = “08”; //or you can take input from a Form.

var theNumber = parseInt (_num, 10);

A utility method to check if the value is integer or not
[like int.TryParse Method in .NET]

It makes it really convenient when evaluating a string value as an integer. But, JavaScript has no equivalent so you need to do your own evaluation every time.

Here’s a simple JavaScript method, which I found in the Internet:

The first parameter of the TryParseInt method is the string you want to evaluate, and the second parameter is the default value to return if the string cannot be evaluated to an integer.

Here are some example usages:

An alternative to this above TryParseInt method will be :

Hope this article helps you [:D]

Sending Email in ASP.NET 2.0

(Taken from: http://aspnet.4guysfromrolla.com/articles/072606-1.aspx)

Introduction
Email serves as a ubiquitous, asynchronous notification and information distribution system. Not surprisingly, there are many web development scenarios where server-side code needs to generate an email and scuttle it off to the intended recipient. The email may be destined for a user of the website, informing them of their newly created user account, reminding them of their forgotten password, or emailing them an invoice. Or it may be destined for a web developer or site administrator, providing information of an unhandled exception that just transpired or user feedback.

Fortunately, ASP.NET makes sending email a breeze. The .NET Framework version 1.x included a number of classes in the System.Web.Mail class that allowed programmatically sending an email with a few scant lines of code. While this namespace and these classes still exist in the .NET Framework version 2.0, they have been deprecated in favor of new mail-related classes found in the System.Net.Mail namespace. (For an article on sending email in ASP.NET version 1.x, see Sending Email from an ASP.NET 1.x Web Page or consult www.SystemWebMail.com.)

In this article we’ll look at the classes in the System.Net.Mail namespace and see how to send an email from an ASP.NET 2.0 page’s code-behind class. We’ll also look at specifying relay server information in Web.config and how this information can be used in some of the built-in ASP.NET server controls for sending emails (such as when a user creates an account or needs a password reminder/reset). Read on to learn more!

Exploring the Classes in the System.Net.Mail Namespace
There are 16 different classes in the System.Net.Mail namespace, all related to send email to a specified Simple Mail Transfer Protocol (SMTP) server for delivery. The two core classes in this namespace are:

• MailMessage – represents an email message; has properties like From, To, Subject, Body, and so on.
• SmtpClient – sends a specified MailMessage instance to a specified SMTP server.

When sending an email from an ASP.NET 2.0 page you will, typically:

1. Create a MailMessage object
2. Assign its properties
3. Create an instance of the SmtpClient class
4. Specify details about the SMTP server to use (if they’re not already specified within Web.config)
5. Send the MailMessage via the SmtpClient object’s Send method

Steps 1 and 2 may be bypassed as the SmtpClient class’s Send method can accept either a MailMessage object or four strings, representing the from, to, subject, and body contents of the email message.

The System.Net.Mail namespace’s other classes allow for more advanced email functionality. There are classes that can be used to add attachments to an email message, to embed objects within an email, to specify SMTP server authentication information, and Exception-derived classes for handling SMTP-specific exceptions. We’ll examine using some of these other classes for more advanced scenarios in future articles.

Providing the SMTP Server’s Details
When sending an email to a friend from Outlook or GMail, the email program establishes a connection with a relay server and sends the contents of the email message, along with information such as the date the email was composed, the email body’s format (text or HTML, for example), the recipient(s), and so on. The relay server accepts the message and then connects to the recipient’s SMTP server and sends the message. Once the message has been delivered, the recipient can, at some later point in time, pull down the message using a different protocol (such as IMAP or POP3).

Therefore, to send an email from an ASP.NET page we need to provide the SmtpClient class with information about the relay server. Along with the hostname of the relay server, you can specify the port (typically port 25 is used), whether or not to use SSL when communicating your email message contents to the relay server, and authentication credentials (if necessary). Alternatively, if you have a local SMTP service installed on your web server, it may periodically monitor a particular “drop-off” directory, sending any messages that appear in that directory. You can configure whether the SmtpClient class relays its email messages to a separate relay server or if it drops it off in a specified pickup directory through the DeliveryMethod property.

The relay server information used by the SmtpClient class can be specified programmatically, through the SmtpClient class’s properties, or can be centralized in Web.config. To use the Web.config approach, add a <system.net> element within the <configuration> element. Then, add a <mailSettings> element that contains an <smtp> element whose settings are specified within its <network> child element, like so:

<configuration>
  <!-- Add the email settings to the <system.net> element -->
  <system.net>
    <mailSettings>
      <smtp>
        <network 
             host="relayServerHostname" 
             port="portNumber"
             userName="username"
             password="password" />
      </smtp>
    </mailSettings>
  </system.net>
 
  <system.web>
    ...
  </system.web>
</configuration>

The host attribute contains the relayServerHostname. If you are using an external relay server, the relayServerHostname might be something like smtp.yourisp.com. If the relay server’s port number is something other than the typical port 25, specify it through the port attribute. Most external relay servers require authentication of some sort (in order to prevent anonymous spammers from sending their garbage through the relay). The userName and password attributes can be provided in the case where username/password authentication is needed.

Only a subset of the SmtpClient properties can be specified through settings in Web.config. To customize the other SmtpClient properties – EnableSsl, Timeout, and so on – set them programmatically when sending the email (step 4 from the list of five steps examined earlier in this article).

Sending an Administrator Email Through a Feedback Web Page
To illustrate sending an email using the MailMessage and SmtpClient classes, I’ve created a simple feedback page example. In this page the user is prompted for their email address, the subject of their feedback, and their feedback.

Once the user has supplied the feedback information and clicked the “Send Feedback” button, a postback ensues and the Button’s Click event fires. Inside the event handler, a MailMessage object is created and its To, From, Subject, and Body properties are set according to the information provided by the user. With the MailMessage object created and its properties populated, the email is then sent through the SmtpClient class’s Send method.

We didn’t need to set any of the SmtpClient class’s properties here in code because they have been specified in Web.config (download the complete code at the end of this article to run this application on your computer).

Conclusion
Along with a plethora of other improvements from ASP.NET 1.x, the email sending capabilities in ASP.NET 2.0 have been updated and moved to a new namespace, System.Net.Mail. In 2.0 the relay server settings can easily be decoupled from the ASP.NET code and moved into the Web.config file, as we saw in this example. Moreover, there’s better support for relay server authentication. Future articles will explore more advanced email scenarios, such as: crafting HTML-formatted emails, sending attachments, embedding objects within the email body, handling SMTP/relay server-related exceptions, and so on.

Download Demo

Sending Email in ASP.NET 2.0: HTML-Formatted Emails, Attachments, and Gracefully Handling SMTP Exceptions

(Taken from: http://aspnet.4guysfromrolla.com/articles/080206-1.aspx)

Introduction
The .NET Framework version 2.0 includes a new namespace (System.Net.Mail) and new classes for sending email. (The namespace (System.Web.Mail) and classes used in the .NET Framework version 1.x still exist for backwards compatibility.) Last week we examined how to use the MailMessage and SmtpClient classes in the System.Net.Mail namespace for sending simple, plain-text email messages.

This article looks at the more advanced email-related options. We’ll see how to send HTML-formatted emails, how to include attachments, and how to gracefully handle SMTP exceptions when sending an email (such as invalid relay server credentials or if the relay server is offline). Read on to learn more!

Sending HTML-Formatted Emails
In Sending Email in ASP.NET 2.0 we saw how to send plain-text emails by assigning the contents of the email to the MailMessage class’s Body property. To send HTML-formatted emails, simply set the Body property to the HTML content to send, and then mark the MailMessage class’s IsBodyHtml property to True.

To demonstrate sending an HTML-formatted message, I created a sample named HtmlEmail.aspx available for download at the end of this article. The germane code follows:

As you can see, simply set the Body property to the HTML content to send and the IsBodyHtml property to True, and you’re done! The actual email content that gets sent to the relay server (and eventually down to the recipient’s email client), looks something like the following:

x-sender: ToEmailAddress
x-receiver: FromEmailAddress
mime-version: 1.0
from: FromEmailAddress
to: ToEmailAddress
date: 25 Jul 2006 15:06:44 -0700
subject: HTML-Formatted Email Demo Using the IsBodyHtml Property
content-type: text/html; charset=us-ascii
content-transfer-encoding: quoted-printable

<h2>This is an HTML-Formatted Email Send Using the <code>IsBodyHtml</code>=
Property</h2><p>Isn't HTML <em>neat</em>?</p><p>You can make all sorts=
of <span style=3D"color:red;font-weight:bold;">pretty colors!!</span>.</p>

The email client – assuming it supports HTML-formatted emails – will display the HTML content within the email.

Including Attachments

The MailMessage class has an Attachments property that is a collection of Attachment class instances. You can attach an existing file on the web server to the email message or base the content’s attachment on a Stream. To illustrate sending emails will attachments, I created a demo where the visitor can fill out a feedback-like form to have an email sent to administrator. However, this feedback form allows the visitor to pick a file from their computer to be attached to the email sent from the web page (much like how the web-based email web applications – Hotmail, GMail, etc. – allow you to attach a file from your computer when sending an email).

To allow the visitor to attach a file from their computer, we need to allow the user to upload a file from their machine to the web server. This can be easily accomplished using the FileUpload control (which is new to ASP.NET 2.0). Let’s look at the declarative syntax used for creating the user interface for this demo:

The FileUpload control renders as a <input type="file" ... /> HTML element, which, in the browser, is displayed as a textbox with a Browse button. When clicked, a dialog box is opened from which the user can pick a file from their computer.

After filling in the feedback form, selecting a file to upload, and clicking the “Send Feedback” button, a postback occurs, sending the contents of the selected file up to the web server. In the “Send Feedback” Button’s Click event handler, a MailMessage object is created and an attachment is added. Since the FileUpload provides a Stream to the uploaded data, we can simply point the new Attachment object at this Stream. There’s no need to save the uploaded file to the web server’s file system.

The Attachment constructor overload used in the code sample above expects two inputs: a reference to the Stream that contains the data to attach, and the name to use for the attachment. The FileUpload’s InputStream and FileName properties are used for these two values.

Handling SMTP Exceptions
When sending an email from an ASP.NET page, what happens if the relay server is down, or if the authentication information used is invalid? In the face of an SMTP error, the SmtpClient class will throw an SmtpException exception. To gracefully handle such problems, we can add exception handling code around the code that sends the email. If there’s an SmtpException we can then display a more friendly and informative error message (or, perhaps, write the email’s contents to a file to be sent later).

In the download at the end of this article I’ve included a demo that allows the visitor to specify the relay server to use, along with authentication information. If there’s an error in attempting to send an email, a client-side alert box is displayed, explaining the problem. To test this out, enter an invalid relay server hostname or invalid credentials for a relay server that requires authentication.

This code catches both SMTP-specific error messages and general ones (such as assigning invalid email addresses to the MailMessage object’s To or From properties). In either case, a client-side alert box is displayed informing the user of the details of the error.

Conclusion
In this article we saw how to send HTML-formatted emails, send emails with attachments, and gracefully handle exceptions arising from sending an email message. Sending an HTML-formatted email is as simple as specifying the HTML content in the Body property and setting the IsBodyHtml property to True. The real challenge comes in making sure the HTML content used is rendered as expected by the popular email clients. To add an attachment to an email, simply add an Attachment object to the MailMessage’s Attachments collection. The data for the attachment can come from a file on the web server or from a Stream. Finally, to handle SMTP-level exceptions, add exception handling code that catches the SmtpException thrown by the SmtpClient class when unable to transport the message to the relay server.

Download Code

How to use connection strings to various Databases in ASP.NET 2.0

Some of the values and strings are used across all the pages of a website. It is a tedious process to code those values and strings in each page of the website.

The connection string will be used in many pages of the web site if you are developing a database driven website. Let us say that you have hard coded the connection string in all the pages, around 30 pages. Now if the value of the connection string changes, you have a headache of changing all the values of the connection string in all the 30 pages. This can’t be done easily and if you are to change the string again after about one month, it is going to be a tedious task.

Hence in such scenarios it is a practice to store those values in a central repository from where you can retrieve it and use it in all the pages. For example if you store the connection string in a central place like a web.config file you can retrieve those connection strings from the web.config file and use it. Previous to ASP.Net 2.0 the connection strings were stored in web.config file as given below:

<configuration>
<appSettings>
<add key=”connectionString” value=”connection_string_value_here” />
</appSettings>

<system.web>
…
</system.web>
</configuration>

The connection string is stored as key and value pair in the <appSettings> element of the web.config file. This value can be retrieved by writing code like:

ConfigurationSettings.AppSettings(“connectionString”)

Instead of using the <appSettings> section you can also add your own sections in the web.config file to have all your string value that you will be using in your application.

ASP.Net 2.0 provides with a special class for retrieving those customized string values.

This class is called the ConfigurationManager class.

Using this class you will be retrieving values by writing the following code for the above config file.

ConfigurationManager.AppSettings["connectionString"]

To open the ConnectionStrings section of the web.config file, you can use code like

ConfigurationManager.ConnectionStrings["connectionString"].ConnectionString

The above code is used to retrieve ConnectionStrings from the web.config file as given below:

<connectionStrings>
<add name=”connectionString” connectionString=”Data Source=.;Initial Catalog=db_products;Integrated Security=True” providerName=”System.Data.SqlClient” />
</connectionStrings>

This code comes under the <configuration> section of the web.config file.

Here you can use the connectionStrings tag to store multiple Connection string to multiple databases and use it at your might.

Like:

<connectionStrings>
<add name=”connectionString” connectionString=”Connect_String_Value” providerName=”Connection_Provider” />

<add name=”myCString” connectionString=”Connect_String_Value” providerName=”Connection_Provider” />

<add name=”newCString” connectionString=”Connect_String_Value” providerName=”Connection_Provider” />
</connectionStrings>

You can use it in you code like :

1. ConfigurationManager.ConnectionStrings["connectionString"].ConnectionString

2. ConfigurationManager.ConnectionStrings["myCString"].ConnectionString

3. ConfigurationManager.ConnectionStrings["newCString"].ConnectionString

Happy Connecting to database

PHP Round Off Decimal or Convert to Decimal Point

Round Off Decimal

Round a number up or down or Round off a floating decimal point number using PHP’s functions round().

Example. round();

Convert to Decimal Point

Example. number_format();

PHP number formatting for decimal places

echo “<br> The value after formating = “.number_format($number,3);
// Will display 2,512,589.668 ( with , after each thousand and 3 digits after decimal
// rounded )

echo “<br> The value after formating = “.number_format($number,3,”#”,”:”);
// Will display 2:512:589#668 ( with : after each thousand and # as decimal symbol )

Happy Coding