How to Blogging?
Exactly what is a “Blog”? A Blog, shortened from “weblog”, is basically an online journal where you can digitally put down your ideas, thoughts, opinions and practically anything that you want people to read. Blogging is very popular all over the world and basically there are no rules when it comes to blogging. Bloggers have the freedom to express themselves however way they want, and the best thing about blogging, is that most blogging sites are free.
Blogs can come in all different styles, formats and settings, depending on the users preferences. Many blogging sites, offer built in features such as hyperlinks, pictures, mp3’s, videos, etc. Some bloggers choose to make their blogs more audio friendly, by using spoken word entries. This is called audio blogging. There are also video logs.
Blogging is really for everyone. Overall, it can be lots of fun, very simple and easy to do. Basically, a blog will contain these features at a minimum:
- archive- list of older articles
- title- where you label your post
- body- the content of your post
- blogroll- other sites can be linked back to your blog
- comments- this allow readers to post comments on your blog
Unlike other websites that are made up of numerous individual pages, blogs are usually made up of only a few templates making it easier for blog users to create new pages. This can be very helpful for beginners, since they can start blogging right away once they’ve set up their account. One of the appeals of blogging is that it creates a community of people sharing similar ideas, thoughts, and comments with each other.
The most popular blog type by far is the personal journal. This is the type that is normally used by first time bloggers. Individuals who want to document the daily struggle of their everyday lives, rants, poems, writings, ideas, and opinions find that blogging offers them a medium in which to express themselves.
Blogging is not just limited to personal usage. There are a lot of blogs that follow a theme such as: philosophy, mobile technology, sports, politics, social commentary, web design, pets, etc. These blogs focus on their specific themes. In this way blogging becomes a medium where people can share their knowledge and opinions about a variety of themes and topics.
There are a lot of other things you can do with a blog. Some bloggers use their blogs as a means to advertise and earn money. Some authors advertise their books or products on their blogs while other bloggers use their blogs to shed light on currents issues, news, family issues, personal thoughts and discoveries, events or catastrophes.
A lot of entrepreneurs benefit from blogging by promoting their products and businesses on their own blogs. With millions and millions of people logging onto the net each and everyday, blogging has become a lucrative move. Some bloggers who run online businesses promote their merchandise online. Others profit through advertisements placed on their blogs.
Blogs can also play an important part in education. Professors can use blogging to document the lessons that they have previously discussed and taught. This is one way students who missed class can easily catch up with their assignments.
Want to learn more about blogging in general or a topic in particular? Blogs varying in topics, themes, and set-ups, and can be found in blog directories. First time users who want to get an idea of what the blogging world is all about can browse through a number of blogs using these kinds of directories. In this way people can get an idea of what these blogging communities, and blogging in general, are all about.
How to connect database in ASP
This is a compiled connection strings reference list on how to connect to SQL Server 2005.
SQL Native Client ODBC Driver
Standard security
Driver={SQL Native Client};Server=myServerAddress;Database=myDataBase; Uid=myUsername;Pwd=myPassword;
Are you using SQL Server 2005 Express? Don’t miss the server name syntax Servername\SQLEXPRESS where you substitute Servername with the name of the computer where the SQL Server 2005 Express installation resides.
Trusted Connection
Driver={SQL Native Client};Server=myServerAddress;Database=myDataBase; Trusted_Connection=yes;
Equivalent key-value pair: “Integrated Security=SSPI” equals “Trusted_Connection=yes”
Connecting to an SQL Server instance
The syntax of specifying the server instance in the value of the server key is the same for all connection strings for SQL Server.
Driver={SQL Native Client};Server=myServerName\theInstanceName;Database=myDataBase; Trusted_Connection=yes;
Prompt for username and password
This one is a bit tricky. First you need to set the connection object’s Prompt property to adPromptAlways. Then use the connection string to connect to the database.
oConn.Properties(”Prompt”) = adPromptAlways
Driver={SQL Native Client};Server=myServerAddress;Database=myDataBase;
Enabling MARS (multiple active result sets)
Driver={SQL Native Client};Server=myServerAddress;Database=myDataBase; Trusted_Connection=yes;MARS_Connection=yes;
Equivalent key-value pair: “MultipleActiveResultSets=true” equals “MARS_Connection=yes”
Use ADO.NET 2.0 for MARS functionality. MARS is not supported in ADO.NET 1.0 nor ADO.NET 1.1.
Encrypt data sent over network
Driver={SQL Native Client};Server=myServerAddress;Database=myDataBase; Trusted_Connection=yes;Encrypt=yes;
Attach a database file on connect to a local SQL Server Express instance
Driver={SQL Native Client};Server=.\SQLExpress;AttachDbFilename=c:\mydbfile.mdf; Database=dbname;Trusted_Connection=Yes;
Why is the Database parameter needed? If the named database have already been attached, SQL Server does not reattach it. It uses the attached database as the default for the connection.
Attach a database file, located in the data directory, on connect to a local SQL Server Express instance
Driver={SQL Native Client};Server=.\SQLExpress; AttachDbFilename=|DataDirectory|mydbfile.mdf;Database=dbname;Trusted_Connection=Yes;
Why is the Database parameter needed? If the named database have already been attached, SQL Server does not reattach it. It uses the attached database as the default for the connection.
Database mirroring
If you connect with ADO.NET or the SQL Native Client to a database that is being mirrored, your application can take advantage of the drivers ability to automatically redirect connections when a database mirroring failover occurs. You must specify the initial principal server and database in the connection string and the failover partner server.
Data Source=myServerAddress;Failover Partner=myMirrorServer;Initial Catalog=myDataBase;Integrated Security=True;
There is ofcourse many other ways to write the connection string using database mirroring, this is just one example pointing out the failover functionality. You can combine this with the other connection strings options available.
SQL Native Client OLE DB Provider
Standard security
Provider=SQLNCLI;Server=myServerAddress;Database=myDataBase;Uid=myUsername; Pwd=myPassword;
Are you using SQL Server 2005 Express? Don’t miss the server name syntax Servername\SQLEXPRESS where you substitute Servername with the name of the computer where the SQL Server 2005 Express installation resides.
Trusted connection
Provider=SQLNCLI;Server=myServerAddress;Database=myDataBase;Trusted_Connection=yes;
Equivalent key-value pair: “Integrated Security=SSPI” equals “Trusted_Connection=yes”
Connecting to an SQL Server instance
The syntax of specifying the server instance in the value of the server key is the same for all connection strings for SQL Server.
Provider=SQLNCLI;Server=myServerName\theInstanceName;Database=myDataBase; Trusted_Connection=yes;
Prompt for username and password
This one is a bit tricky. First you need to set the connection object’s Prompt property to adPromptAlways. Then use the connection string to connect to the database.
oConn.Properties(”Prompt”) = adPromptAlways
oConn.Open “Provider=SQLNCLI;Server=myServerAddress;DataBase=myDataBase;
Enabling MARS (multiple active result sets)
Provider=SQLNCLI;Server=myServerAddress;Database=myDataBase; Trusted_Connection=yes;MarsConn=yes;
Equivalent key-value pair: “MultipleActiveResultSets=true” equals “MARS_Connection=yes”
Use ADO.NET 2.0 for MARS functionality. MARS is not supported in ADO.NET 1.0 nor ADO.NET 1.1.
Encrypt data sent over network
Provider=SQLNCLI;Server=myServerAddress;Database=myDataBase; Trusted_Connection=yes;Encrypt=yes;
Attach a database file on connect to a local SQL Server Express instance
Provider=SQLNCLI;Server=.\SQLExpress;AttachDbFilename=c:\mydbfile.mdf; Database=dbname;Trusted_Connection=Yes;
Why is the Database parameter needed? If the named database have already been attached, SQL Server does not reattach it. It uses the attached database as the default for the connection.
Attach a database file, located in the data directory, on connect to a local SQL Server Express instance
Provider=SQLNCLI;Server=.\SQLExpress;AttachDbFilename=|DataDirectory|mydbfile.mdf; Database=dbname;Trusted_Connection=Yes;
Why is the Database parameter needed? If the named database have already been attached, SQL Server does not reattach it. It uses the attached database as the default for the connection.
Database mirroring
If you connect with ADO.NET or the SQL Native Client to a database that is being mirrored, your application can take advantage of the drivers ability to automatically redirect connections when a database mirroring failover occurs. You must specify the initial principal server and database in the connection string and the failover partner server.
Data Source=myServerAddress;Failover Partner=myMirrorServer;Initial Catalog=myDataBase;Integrated Security=True;
There is ofcourse many other ways to write the connection string using database mirroring, this is just one example pointing out the failover functionality. You can combine this with the other connection strings options available.
SqlConnection (.NET)
Standard Security
Data Source=myServerAddress;Initial Catalog=myDataBase;User Id=myUsername;Password=myPassword;
Use serverName\instanceName as Data Source to connect to a specific SQL Server instance.
Are you using SQL Server 2005 Express? Don’t miss the server name syntax Servername\SQLEXPRESS where you substitute Servername with the name of the computer where the SQL Server 2005 Express installation resides.
Standard Security alternative syntax
This connection string produce the same result as the previous one. The reason to include it is to point out that some connection string keywords have many equivalents.
Server=myServerAddress;Database=myDataBase;User ID=myUsername;Password=myPassword;Trusted_Connection=False;
Trusted Connection
Data Source=myServerAddress;Initial Catalog=myDataBase;Integrated Security=SSPI;
Trusted Connection alternative syntax
This connection string produce the same result as the previous one. The reason to include it is to point out that some connection string keywords have many equivalents.
Server=myServerAddress;Database=myDataBase;Trusted_Connection=True;
Connecting to an SQL Server instance
The syntax of specifying the server instance in the value of the server key is the same for all connection strings for SQL Server.
Server=myServerName\theInstanceName;Database=myDataBase;Trusted_Connection=True;
Trusted Connection from a CE device
Often a Windows CE device is not authenticated and logged in to a domain. To use SSPI or trusted connection / authentication from a CE device, use this connection string.
Data Source=myServerAddress;Initial Catalog=myDataBase;Integrated Security=SSPI;User ID=myDomain\myUsername;Password=myPassword;
Connect via an IP address
Data Source=190.190.200.100,1433;Network Library=DBMSSOCN;Initial Catalog=myDataBase;User ID=myUsername;Password=myPassword;
DBMSSOCN=TCP/IP. This is how to use TCP/IP instead of Named Pipes. At the end of the Data Source is the port to use. 1433 is the default port for SQL Server.
Enabling MARS (multiple active result sets)
Server=myServerAddress;Database=myDataBase;Trusted_Connection=True; MultipleActiveResultSets=true;
Use ADO.NET 2.0 for MARS functionality. MARS is not supported in ADO.NET 1.0 nor ADO.NET 1.1.
Attach a database file on connect to a local SQL Server Express instance
Server=.\SQLExpress;AttachDbFilename=c:\mydbfile.mdf;Database=dbname; Trusted_Connection=Yes;
Why is the Database parameter needed? If the named database have already been attached, SQL Server does not reattach it. It uses the attached database as the default for the connection.
Attach a database file, located in the data directory, on connect to a local SQL Server Express instance
Server=.\SQLExpress;AttachDbFilename=|DataDirectory|mydbfile.mdf; Database=dbname;Trusted_Connection=Yes;
Why is the Database parameter needed? If the named database have already been attached, SQL Server does not reattach it. It uses the attached database as the default for the connection.
Using an User Instance on a local SQL Server Express instance
The User Instance functionality creates a new SQL Server instance on the fly during connect. This works only on a local SQL Server 2005 instance and only when connecting using windows authentication over local named pipes. The purpose is to be able to create a full rights SQL Server instance to a user with limited administrative rights on the computer.
Data Source=.\SQLExpress;Integrated Security=true; AttachDbFilename=|DataDirectory|\mydb.mdf;User Instance=true;
To use the User Instance functionality you need to enable it on the SQL Server. This is done by executing the following command: sp_configure ‘user instances enabled’, ‘1′. To disable the functionality execute sp_configure ‘user instances enabled’, ‘0′.
Database mirroring
If you connect with ADO.NET or the SQL Native Client to a database that is being mirrored, your application can take advantage of the drivers ability to automatically redirect connections when a database mirroring failover occurs. You must specify the initial principal server and database in the connection string and the failover partner server.
Data Source=myServerAddress;Failover Partner=myMirrorServer;Initial Catalog=myDataBase;Integrated Security=True;
There is ofcourse many other ways to write the connection string using database mirroring, this is just one example pointing out the failover functionality. You can combine this with the other connection strings options available.
Asynchronous processing
A connection to SQL Server 2005 that allows for the issuing of async requests through ADO.NET objects.
Server=myServerAddress;Database=myDataBase;Integrated Security=True;Asynchronous Processing=True;
SQLXMLOLEDB
Using SQL Server Native Client provider
Provider=SQLXMLOLEDB.4.0;Data Provider=SQLNCLI;Data Source=myServerAddress;Initial Catalog=myDataBase;User Id=myUsername;Password=myPassword;
SQL Server 2005 specials
Context Connection
Connecting to “self” from within your CLR stored prodedure/function. The context connection lets you execute Transact-SQL statements in the same context (connection) that your code was invoked in the first place.
C#
using(SqlConnection connection = new SqlConnection(”context connection=true”))
{
connection.Open();
// Use the connection
}
VB.Net
Using connection as new SqlConnection(”context connection=true”)
connection.Open()
‘ Use the connection
End Using
How to get IP address?
Get IP address
By ASP <%= Request.ServerVariables(”REMOTE_ADDR”) %>
By PHP <?php echo $ip=$_SERVER[’REMOTE_ADDR’]; ?>
By JAVA
import java.net.*;
import java.io.*;
import java.applet.*;
public class GetClientIP extends Applet {
public void init() {
try {
InetAddress thisIp =
InetAddress.getLocalHost();
System.out.println(”IP:”+thisIp.getHostAddress());
}
catch(Exception e) {
e.printStackTrace();
}
}
}
//HTML Page
<HTML><HEAD></HEAD><BODY>
<APPLET CODE=”GetClientIP.class”
HEIGHT=10 WIDTH=10>
</APPLET>
Check JAVA console for output
</BODY></HTML>
BY Coldfusion
<cfoutput>#CGI.REMOTE_ADDR#</cfoutput>
BY CGI
import cgi
import os
print “Content-type: text/html”
print “”
print cgi.escape(os.environ[”REMOTE_ADDR”])
Dfference between web 1.0 and web 2.0
“Web” is a fancy catch-all phrase for the Hypertext Transfer Protocol (HTTP, the protocol used for transferring information between a Web server and Web browser) and the Hypertext Markup Language (HTML, the markup language that tells your browser how to display whatever text, graphics, etc is coming through the HTTP). Over at the World Wide Web Consortium (W3C), there actually are versions of these protocols. HTTP for example is still on version 1.1 and has been since 1999. The most recent of HTML (version 4.01) is just as old. There is something over at the W3C in draft mode called XHTML which is now at version 2.0 and has relevance to the future Web. But a one-to-one mapping of it directly to Web 2.0, especially when you consider how many things have been dropped into the Web 2.0 bucket that don’t use XHTML, doesn’t work either.
If you looked at all the Web applications and sites that have been dropped into that Web 2.0 bucket, one of the more common ingredients would probably be use of the AJAX (Asynchronous Javascript and XML) programming technique — a technique that generally speaking adds an element of real-time interactivity to Web pages that might otherwise be very static. Google’s Gmail e-mail service, for example, uses AJAX to keep your view of the inbox updated as new mail arrives with out having to refresh the entire Web page. I’m fairly certain that AJAX is also the enabler of Gmail’s autosave feature (that automatically saves drafts to Gmail’s servers for you as you are writing your emails). But three problems that are common to many if not all AJAX-based pages is how they often interfere with the functionality of a Web browser’s back button (in most cases, it either doesn’t work, or it takes you back to a page that you don’t want to be taken back to). Another is that the forward button (when advancing to a page with AJAX code on it) yields unpredictable results as well. And finally, the same goes for bookmarking AJAX-driven pages.
So, when people ask me what Web 2.0 is, a lot of times, I say “It’s when the back button doesn’t work! (something that usually works with Web 1.0… but not always). The other thing I say is that I don’t think there’s a trade or servicemark on “Web 1.0.” That’s a big difference too.
How to connect database in ASP.Net
ADO Database Connection
Create a DSN-less Database Connection
The easiest way to connect to a database is to use a DSN-less connection. A DSN-less connection can be used against any Microsoft Access database on your web site. If you have a database called “northwind.mdb” located in a web directory like “c:/inetpub/wwwroot”, you can connect to the database with the following ASP code:
<%set conn=Server.CreateObject(”ADODB.Connection”)conn.Provider=”Microsoft.Jet.OLEDB.4.0″conn.Open “c:/inetpub/wwwroot/northwind.mdb”%>
Note, from the example above, that you have to specify the Microsoft Access database driver (Provider) and the physical path to the database on your computer.
Create an ODBC Database Connection
If you have an ODBC database called “northwind” you can connect to the database with the following ASP code:
<%set conn=Server.CreateObject(”ADODB.Connection”)conn.Open “northwind”%>
With an ODBC connection, you can connect to any database, on any computer in your network, as long as an ODBC connection is available.
An ODBC Connection to an MS Access Database
Here is how to create a connection to a MS Access Database:
1. Open the ODBC icon in your Control Panel.
2. Choose the System DSN tab.
3. Click on Add in the System DSN tab.
4. Select the Microsoft Access Driver. Click Finish.
5. In the next screen, click Select to locate the database.
6. Give the database a Data Source Name (DSN).
7. Click OK.
Note that this configuration has to be done on the computer where your web site is located. If you are running Personal Web Server (PWS) or Internet Information Server (IIS) on your own computer, the instructions above will work, but if your web site is located on a remote server, you have to have physical access to that server, or ask your web host to do this for you.
The ADO Connection Object
The ADO Connection object is used to create an open connection to a data source. Through this connection, you can access and manipulate a database.
ACE OLEDB 12.0 (Access 2007)
Standard security
Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\inetpub\wwwroot\myAccess2007file.accdb;Persist Security Info=False;
With database password
This is the connection string to use when you have an Access 2007 database protected with a password using the “Set Database Password” function in Access.
Provider=Microsoft.ACE.OLEDB.12.0;
Data Source=C:\inetpub\wwwroot\myAccess2007file.accdb;
Jet OLEDB:Database Password=MyDbPassword;
DataDirectory functionality
Provider=Microsoft.ACE.OLEDB.12.0;
Data Source=|DataDirectory|\myAccess2007file.accdb;
Persist Security Info=False;
ODBC(SQL Server 2000, 7.0)
Standard SecurityDriver={SQL Server};Server=myServerAddress;Database=myDataBase;Uid=myUsername;Pwd=myPassword;
Trusted connection
Driver={SQL Server};Server=myServerAddress;Database=myDataBase;Trusted_Connection=Yes;
Prompt for username and password
This one is a bit tricky. First you need to set the connection object’s Prompt property to adPromptAlways. Then use the connection string to connect to the database.
oConn.Properties(”Prompt”) = adPromptAlways
Driver={SQL Server};Server=myServerAddress;Database=myDataBase;
OLE DB, OleDbConnection (.NET)
Standard Security
Provider=sqloledb;Data Source=myServerAddress;Initial Catalog=myDataBase;User Id=myUsername;Password=myPassword;
Trusted connection
Provider=sqloledb;Data Source=myServerAddress;Initial Catalog=myDataBase;Integrated Security=SSPI;
Use serverName\instanceName as Data Source to use a specific SQL Server instance. Please note that the multiple SQL Server instances feature is available only from SQL Server version 2000 and not in any previous versions.
Connecting to an SQL Server instance
The syntax of specifying the server instance in the value of the server key is the same for all connection strings for SQL Server.
Provider=sqloledb;Data Source=myServerName\theInstanceName;Initial Catalog=myDataBase;Integrated Security=SSPI;
Prompt for username and password
This one is a bit tricky. First set the connection object’s Provider property to “sqloledb”. Thereafter set the connection object’s Prompt property to adPromptAlways. Then use the connection string to connect to the database.
oConn.Provider = “sqloledb”
oConn.Properties(”Prompt”) = adPromptAlways
Data Source=myServerAddress;Initial Catalog=myDataBase;
Connect via an IP address
Provider=sqloledb;Data Source=190.190.200.100,1433;Network Library=DBMSSOCN;Initial Catalog=myDataBase;User ID=myUsername;Password=myPassword;.
DBMSSOCN=TCP/IP. This is how to use TCP/IP instead of Named Pipes. At the end of the Data Source is the port to use. 1433 is the default port for SQL Server.
Disable connection pooling
This one is usefull when receving errors “sp_setapprole was not invoked correctly.” (7.0) or “General network error. Check your network documentation” (2000) when connecting using an application role enabled connection. Application pooling (or OLE DB resource pooling) is on by default. Disabling it can help on this error.
Provider=sqloledb;Data Source=myServerAddress;Initial Catalog=myDataBase;User ID=myUsername;Password=myPassword;OLE DB Services=-2;
SqlConnection (.NET)
Standard Security
Data Source=myServerAddress;Initial Catalog=myDataBase;User Id=myUsername;Password=myPassword;
Standard Security alternative syntax This connection string produces the same result as the previous one. The reason to include it is to point out that some connection string keywords have many equivalents.
Server=myServerAddress;Database=myDataBase;User ID=myUsername;Password=myPassword;Trusted_Connection=False;
Trusted Connection
Data Source=myServerAddress;Initial Catalog=myDataBase;Integrated Security=SSPI;
Trusted Connection alternative syntax
This connection string produce the same result as the previous one. The reason to include it is to point out that some connection string keywords have many equivalents.
Server=myServerAddress;Database=myDataBase;Trusted_Connection=True;
Use serverName\instanceName as Data Source to use a specific SQL Server instance. Please note that the multiple SQL Server instances feature is available only from SQL Server version 2000 and not in any previous versions.
Connecting to an SQL Server instance
The syntax of specifying the server instance in the value of the server key is the same for all connection strings for SQL Server.
Server=myServerName\theInstanceName;Database=myDataBase;Trusted_Connection=True;
Trusted Connection from a CE device
Often a Windows CE device is not authenticated and logged in to a domain. To use SSPI or trusted connection / authentication from a CE device, use this connection string.
Data Source=myServerAddress;Initial Catalog=myDataBase;Integrated Security=SSPI;User ID=myDomain\myUsername;Password=myPassword;
Connect via an IP address
Data Source=190.190.200.100,1433;Network Library=DBMSSOCN;Initial Catalog=myDataBase;User ID=myUsername;Password=myPassword;
DBMSSOCN=TCP/IP. This is how to use TCP/IP instead of Named Pipes. At the end of the Data Source is the port to use. 1433 is the default port for SQL Server.
Specifying packet size
Server=myServerAddress;Database=myDataBase;User ID=myUsername;Password=myPassword;Trusted_Connection=False;Packet Size=4096;
By default, the Microsoft .NET Framework Data Provider for SQL Server sets the network packet size to 8192 bytes. This might however not be optimal, try to set this value to 4096 instead.
SQLXMLOLEDB.
Using SQL Server Ole Db
The SQLXML version 3.0 restricts the data provider to SQLOLEDB only.
Provider=SQLXMLOLEDB.3.0;Data Provider=SQLOLEDB;Data Source=myServerAddress;Initial Catalog=myDataBase;User Id=myUsername;Password=myPassword;
Data Shape
MS Data Shape
Provider=MSDataShape;Data Provider=SQLOLEDB;Data Source=myServerAddress;Initial Catalog=myDataBase;User ID=myUsername;Password=myPassword;