今天發現當 System.Net.Mail.MailMessage  有附件時，SendMail 後附檔會被Lock住
原來使用完之後要釋放資源，不然要等一段時間才會被系統釋放

另外 .Net 4.0 的 SmtpClient 物件也要 Dispose()
他的做法也類似 SqlCoonection 有 pooling 的機制
因此用完也必須要 Dispose()

UW.Mail 我有調整過了 要SVN更新一下 再build

最近看到一些 javascript 範例 覺得這樣不錯的
就是用 array push, join 方式來拼字串

    var Data = [{"key": "key5", "value": "value5"}, {"key": "key4", "value": "value4"}, {"key": "key3", "value": "value3"}];

    var html = [];

    html.push('<select name="test">');

    for (var i = 0; i < Data.length; i++) {

        html.push('<option value="' + Data[i]["key"] + '">',

            Data[i]["value"],

            "</option>");

    }

    html.push('</select>');

    return html.join('');

同樣的方式 .net 也可以這樣做

        List<string> listOfString = new List<string>();

        for (int i = 0; i < 10; i++)

        {

            listOfString.Add(i.ToString());

        }

        string strResult = string.Join(", ", listOfString.ToArray());

用這種方式也省的判別最後一筆要不要加上分隔符號

參考：Microsoft® SQL Server® 2008 Express安裝步驟指南

※Microsoft® SQL Server® 2008 Express with Tools此版本才有管理工具。

必備元件

Microsoft .NET Framework 3.5 Service pack 1(不裝連安裝畫面都無法開啟)
http://www.microsoft.com/downloads/details.aspx?FamilyId=AB99342F-5D1A-413D-8319-81DA479AB0D7&displaylang=zh-tw

Windows Installer 4.5 Redistributable - 繁體中文(不安裝就無法安裝SQL Server 2008)
http://www.microsoft.com/downloads/details.aspx?displaylang=zh-tw&FamilyID=5a58b56f-60b6-4412-95b9-54d056d6f9f4

PowerShell 1.0(不裝在檢查元件步驟就無法通過)
926139：Windows PowerShell 1.0 英文語言安裝封裝適用於 Windows Server 2003 及 Windows XP
926140：Windows Server 2003 Service Pack 1 與 Windows XP Service Pack 2 的 Windows PowerShell 1.0 當地語系化安裝套件
926141：Windows 1.0 PowerShell 多語系使用者語言介面 (MUI) Pack 適用於 Windows Server 2003 或適用於 Windows XP
928439：適用於 Windows Vista 的 Windows PowerShell 1.0 安裝封裝

※MSXML 6 SP2 會造成 SQL Server 2008 安裝失敗
解：先移除掉 MSXML 6 SP2，安裝完 SQL Server  2008 後，再更新 HotFix 一次
http://byronhu.wordpress.com/2008/12/25/msxml-6-sp2-%E6%9C%83%E9%80%A0%E6%88%90-sql-server-2008-%E5%AE%89%E8%A3%9D%E5%A4%B1%E6%95%97/

我今天將這個物件做了調整 主要是針對
ssl (https) 判斷以及 Url-Rewrite 狀況做處理
而之前孟哲有調整加入port number的狀況

理論上目前運作的程式應該是不會有影響，
但如果舊NET 4.0專案更新dll有狀況，也許跟這個更新有關
這個大家注意一下

 ASP.NET 在處理 HTTP POST 要求時最多只能接受 1,000 個參數，一般來說不會有人透過 POST 傳遞表單資料超過 1,000 個欄位 ( 以筆者的經驗來說，傳過最多的一次是 700 個欄位，當時是個問卷系統 )，如果傳數參數超過 1,000 筆的話，就會出現 Operation is not valid due to the current state of the object. (英文) 或 由於該物件目前的狀態，導致作業無效。 (中文) 例外狀況，細部的例外訊息會有 HttpException (0x80004005): The URL-encoded form data is not valid. (英文) 或 HttpException (0x80004005): URL 編碼型式資料無效。
參考：http://blog.miniasp.com/post/2012/01/01/Efficient-Denial-of-Service-Attacks-on-Web-Application-Platforms.aspx

解：
web.config加下面這個設定

<appSettings>

     <add key="aspnet:MaxHttpCollectionKeys" value="5000" />

</appSettings>

 

使用 APPCMD

所在位置: cd %windir%\system32\inetsrv

匯出整個網站設定: appcmd list site "SiteName" /config /xml > D:\IISSetting\SiteName.xml

匯入整個網站設定: appcmd.exe add site /in < D:\IISSetting\SiteName.xml

在執行匯入的動作之前，要先檢查一下 .XML 裡面的 ID, 是否和現有的網站衝突，一般會有兩個地方。 

有時在 XML 裡面會多一個 ftpServer 的區塊，要記得刪掉，另外 Application Pool 要記得，建立可以使用以下指令。

export
appcmd list apppool 116foto /config /xml >D:\IISSetting\app_116foto.xml
import
appcmd add apppool /name:116foto /in <D:\IISSetting\app_116foto.xml

各瀏覽器中cookie個數和大小限制

當使用 WebRequest 來 Get 網址時，出現"已經嘗試太多次自動重新導向"。

通常為對方網站有進行某種判斷。以下為試過的項目。

上次是將 CookieContainer 設定一個 New Net.CookieContainer 即可。

            Dim http As Net.HttpWebRequest = Net.WebRequest.Create(Url)

            http.Method = "GET"

            http.ContentType = "application/x-www-form-urlencoded;"



            http.UserAgent = "Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.0; Win64; x64; Trident/5.0)"

            http.CookieContainer = New Net.CookieContainer

            http.Referer = Url

從 http://blog.ie-soft.de/post/2007/12/globalasax-events.aspx  抄來的. 留作參考

HttpApplication Events:

Application_AcquireRequestState
Occurs when ASP.NET acquires the current state (for example, session state) that is associated with the current request. 

Application_AuthenticateRequest
Occurs when a security module has established the identity of the user. 

Application_AuthorizeRequest
Occurs when a security module has verified user authorization. 

Application_BeginRequest
Occurs as the first event in the HTTP pipeline chain of execution when ASP.NET responds to a request. 

Application_Disposed
Adds an event handler to listen to the Disposed event on the application. 

Application_EndRequest
Occurs as the last event in the HTTP pipeline chain of execution when ASP.NET responds to a request. 

Application_Error
Occurs when an unhandled exception is thrown. 

Application_PostAcquireRequestState
Occurs when the request state (for example, session state) that is associated with the current request has been obtained. 

Application_PostAuthenticateRequest
Occurs when a security module has established the identity of the user. 

Application_PostAuthorizeRequest
Occurs when the user for the current request has been authorized. 

Application_PostMapRequestHandler
Occurs when ASP.NET has mapped the current request to the appropriate event handler. 

Application_PostReleaseRequestState
Occurs when ASP.NET has completed executing all request event handlers and the request state data has been stored. 

Application_PostRequestHandlerExecute
Occurs when the ASP.NET event handler (for example, a page or an XML Web service) finishes execution. 

Application_PostResolveRequestCache
Occurs when ASP.NET bypasses execution of the current event handler and allows a caching module to serve a request from the cache. 

Application_PostUpdateRequestCache
Occurs when ASP.NET completes updating caching modules and storing responses that are used to serve subsequent requests from the cache. 

Application_PreRequestHandlerExecute
Occurs just before ASP.NET begins executing an event handler (for example, a page or an XML Web service). 

Application_PreSendRequestContent
Occurs just before ASP.NET sends content to the client. 

Application_PreSendRequestHeaders
Occurs just before ASP.NET sends HTTP headers to the client. 

Application_ReleaseRequestState
Occurs after ASP.NET finishes executing all request event handlers. This event causes state modules to save the current state data. 

Application_ResolveRequestCache
Occurs when ASP.NET completes an authorization event to let the caching modules serve requests from the cache, bypassing execution of the event handler (for example, a page or an XML Web service). 

Application_UpdateRequestCache
Occurs when ASP.NET finishes executing an event handler in order to let caching modules store responses that will be used to serve subsequent requests from the cache. 

Application_Init
This method occurs after _start and is used for initializing code. 

Application_Start
As with traditional ASP, used to set up an application environment and only called when the application first starts.

Application_End
Again, like classic ASP, used to clean up variables and memory when an application ends.

Session Events:

Session_Start
As with classic ASP, this event is triggered when any new user accesses the web site.

Session_End
As with classic ASP, this event is triggered when a user's session times out or ends. Note this can be 20 mins (the default session timeout value) after the user actually leaves the site.

Profile Events:

Profile_MigrateAnonymous
Occurs when the anonymous user for a profile logs in.

Passport Events:

PassportAuthentication_OnAuthenticate
Raised during authentication. This is a Global.asax event that must be named PassportAuthentication_OnAuthenticate.
 

Possibly more events defined in other HttpModules like:

System.Web.Caching.OutputCacheModule
System.Web.SessionState.SessionStateModule
System.Web.Security.WindowsAuthentication
System.Web.Security.FormsAuthenticationModule
System.Web.Security.PassportAuthenticationModule
System.Web.Security.UrlAuthorizationModule
System.Web.Security.FileAuthorizationModule
System.Web.Profile.ProfileModule