ASP.NET 2.0 Guide by RidDick for VS2005 and .Net Framework SDK 2.0 (Start Time 18/01/2008 23:59)
ถึงวันนี้แล้วก็คงไม่มีใครปฏิเสธได้ว่าเทคโนโลยีก้าวไปอย่างรวดเร็วจนอยู่แทบทุกที่ที่เราอยู่ คงจะมีน้อยคนมากที่ไม่ได้ยุ่งเกี่ยวกับเทคโนโลยีเลย คนเราก็ช่างมีความมหัศจรรย์เหลือหลาย อะไรที่ไม่เคยมีคนคิดคนทำก็ช่างสรรค์หามาทำจนได้ เช่นกันกับตัวเราเองนี่แหละน๊า ที่อยู่ดี ๆ ก็ต้องมาศึกษาเทคโนโลยี .Net กับเขาเสียที
พอเริ่มปุ๊บก็เจอแล้วนะเรา ไม่ใช่ว่าเจอทางสว่างนะ แต่เจอตอที่เขาเรียกว่าปัญหาต่างหาก นี่ลแหละคือที่มาของการทำหัวข้อนี้ เพื่อว่าวันต่อไปจะได้นำกลับมาใช้อีก ถ้าจะมีใครสักคนจะเข้ามาดูและนำไปใช้ก็ไม่ว่ากัน แต่ต้องขอบอกไว้ก่อนว่าข้อมูลเหล่านี้ได้มาจากส่วนตัวเท่านั้น อาจจะถูกหรือผิดก็อย่าว่ากันนะ เอาเป็นว่าเริ่มเลยละกัน
……………………………………………………………………………………………………………….
ขั้นตอนการติดตั้ง ASP.NET
1. Install IIS (XP,2000 or Higher)
2. Install VS2005 (Don’t install .Net Framework because VS have them)
3. Set IIS in TAB ASP.NET use ver. 2.0.xxxx
–> VS2003 use ver. 1.0.xxxx
–> VS2005 use ver. 2.0.xxxx
4. Start VS2005
–> Select Web Developer
–> Create new Project Website
–> Select ASP.Net Website
–> Location Select HTTP = http://localhost/Project name
–> Language Select Visual Basic
–> Click Ok to start develope
–> Right click http://localhost/Project name to Create New Page and type name for your page
–> Coding your application.
……………………………………………………………………………………………………………….
Exception for <connectionStrings/>
แก้โดย เลือกเวอร์ชั่นของ .Net Framwork ให้ถูกต้อง
–> VS2003 use ver. 1.0.xxxx
–> VS2005 use ver. 2.0.xxxx
……………………………………………………………………………………………………………….
Exception = Failed to access IIS metabase.
แก้โดย
RUN –> cmd
–> cd C:\WINDOWS\Microsoft.NET\Framework\v2.
0.50727
Execute Command –> aspnet_regiis -i
–> C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>aspnet_regiis -i
Start installing ASP.NET (2.0.50727).
……………………
Finished installing ASP.NET (2.0.50727).
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>
……………………………………………………………………………………………………………….
Exception = Mutex could not be created.
แก้โดย
ลบไฟล์ที่เกี่ยวกับโปรเจกที่อยู่ใน C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files ออกให้หมด
Restart IIS+VS2005+IE
……………………………………………………………………………………………………………….
วันนี้ต้องพอแค่นี้ก่อนแล้วเรา ง่วงแล้ว ไว้ต่อคราวหน้า
แซมริด 
January 19, 2008 at 5:22 pm |
ลงตอนไหนว่ะ เมื่อเช้ายังไม่มีเลย
ต้องไปหาเว้บนอกอ่าน ทำได้แล้วเหมือนกันคับท่าน
แต่ขอบคุณคับที่อะไรดีๆ มให้อ่าน
January 20, 2008 at 9:23 pm |
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.
Using MARS with SQL Native Client, by Chris Lee >>
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:\asd\qwe\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.
Download the SQL Native Client here. The package contains booth the ODBC driver and the OLE DB provider >>
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.
Read more about database mirroring in this Microsoft TechNet article “Database Mirroring in SQL Server 2005″ >>
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.
Using MARS with SQL Native Client, by Chris Lee >>
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:\asd\qwe\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.
Download the SQL Native Client here. The package contains booth the ODBC driver and the OLE DB provider >>
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.
Read more about database mirroring in this Microsoft TechNet article “Database Mirroring in SQL Server 2005″ >>
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;
Note that this will only work on a CE device.
Read more about connecting to SQL Server from CE devices here >>
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.
How to define which network protocol to use >>
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.
Streamline your Data Connections by Moving to MARS, by Laurence Moroney, DevX.com >>
Attach a database file on connect to a local SQL Server Express instance
Server=.\SQLExpress;AttachDbFilename=c:\asd\qwe\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.
Read more about database mirroring in this Microsoft TechNet article “Database Mirroring in SQL Server 2005″ >>
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;
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
August 13, 2008 at 2:51 pm |
แว้บ เข้ามาดูหลายครั้งแล้วค่ะ เป็นประโยชน์มากๆเลย
วันหลังเอาความรู้ดี ๆ มาลงอีกเยอะ ๆนะคะ