paulwu0115

[ASP.NET]利用configSource將web.config的connectionStrings移到另一個config檔來維護

2018-12-27T03:23:00.002-08:00

最近剛好看到這樣的寫法,把它記錄一下

connectionStrings：

一般web.config的connectionStrings會這樣設定

web.config

也可以將connectionStrings移到另一個config檔來維護

web.config

connections.config

<?xml version="1.0" encoding="utf-8"?>
<connectionStrings>
<add name="MSSQL" connectionString="MSSQL" />
<add name="Oralce" connectionString="Oracle" />
</connectionStrings>

appSettings：

appSettings也可以使用configSource將設定值移到另一個config檔來維護

web.config

settings.config

<?xml version="1.0" encoding="utf-8"?>
<appSettings>
  <add key="Blog" value="F6 Team" />
  <add key="Name" value="puma" />
  <add key="skill" value="ASP.NET" />
</appSettings>

也可以使用file來增加外部config檔的設定值

web.config

settings.config

<?xml version="1.0" encoding="utf-8"?>
<appSettings>
<add key="skill" value="ASP.NET" />
</appSettings>

file與configSource的差別就是：

1.file:可以延伸外部檔案的setting
2.configSource:指定一個xxx.config(但web.cofing就不能設定了,不然會出錯)

以上每一種方式的執行結果都一樣,如下圖所示：

code：

using System;
using System.Web.Configuration;
using System.Configuration;

public partial class webconfig : System.Web.UI.Page
{
    protected void Page_Load(object sender, EventArgs e)
    {
        foreach (string set in WebConfigurationManager.AppSettings)
        {
            Response.Write(string.Format("key：{0}，value：{1}<br/>", set, WebConfigurationManager.AppSettings.Get(set)));
        }

        foreach (ConnectionStringSettings conn in WebConfigurationManager.ConnectionStrings)
        {
            Response.Write(string.Format("name：{0}，connectionString：{1}<br/>", conn.Name, conn.ConnectionString));
        }
    }
}

201207232016微軟教你免費用永久使用測試版的 Terminal Licensing

2018-11-22T07:32:00.003-08:00

微軟教你免費用永久使用測試版的 Terminal Licensing

還在為專案用的主機同時只能有二個使用者使用遠端桌面煩惱嗎?

建議您可以安裝 Microsoft 的 Terminal Services Licensing

(在新增移除 Windows 元件中可以找到，且可由安裝光碟中直接安裝測試版)

因為是測試版的，所以只能免費使用 90 天，

算法是 "用戶電腦" 第一次由遠端桌面登入主機時算起 (CAL DEVICE 授權)

可由下列步驟找到目前有授權使用的電腦(有使用遠端桌面登入過的電腦)

開始->所有程式->系統管理工具->終端機伺機器授權->連線到 LOCALHOST

在臨時的授權 Windows Server2003-終端機伺服器 CAL 權杖中

可以看到每一台有使用遠端桌面登入過的電腦及他們的授權時間(90天)

雖然購買 Microsoft 的 CAL(Client Access Licensing) DEVICE 授權還不太貴(1個大慨 $3,000 NTD)，

但是如果一整個專案，或部門要使用，加起來要買的 CAL 授權也是個不小的開支，

而且 DEVICE CAL 還是每一台伺服都要買一次，授權只是一年的。

永久免費使用授權的方法，其實是利用 Microsoft 在授權流程上的漏洞

只要在用戶端移除 MSLicensing 的註冊碼就可以了

執行一行指令

reg delete HKLM\SOFTWARE\Microsoft\MSLicensing /f

這行指令對你的系統完全沒有任何影響!

(在 Microsoft 網站其實已經有不小心洩漏出來破解的方法了 http://support.microsoft.com/?id=839878 原因 2)

用戶端可透過這行指令無限的延申使用 Terminal Licensing

針對如何無限的使用測試版的 Terminal Licensing 有幫各位歸納有以下二種情況：

1. Server 未安裝過 Licensing

2. Server 已經安裝 Licensing ，且已經開始有人使用了

針對以上二種情況可依下列步驟處理

1. Server 未安裝過 Licensing

a. 安裝 Licensing

b. 在每一作用戶的電腦中，移除 CAL TS 註冊值，

在每個用戶電腦上執行指令

reg delete HKLM\SOFTWARE\Microsoft\MSLicensing /f

c. 重開電腦

2. Server 已經安裝 Licensing ，且已經開始有人使用了

a. 中斷所有線上 Terminal 中的使用者

b. 如果自己本身也是 Terminal 進入Windlows 可以先中斷本身的連線

c. 停止 Termianl Licensing

d. 到目錄 %WINDIR%\system32\lserver 內將檔案 TSLIC.edb 修改為 tslic.old (為防萬一，備份用的)

e. 啟重 Termianl Licensing

e. 在每一作用戶的電腦中，移除 CAL TS 註冊值，

在每個用戶電腦上執行指令

reg delete HKLM\SOFTWARE\Microsoft\MSLicensing /f

f. 重開電腦

註：如果不想動 Server 也可以三個月只重新執行一次指令就可以重新開始使用 Licensing 了

Is it possible to autostart a VMware virtual machine in background as a Windows service, and shut it down elegantly when Windows shuts down?

2018-11-19T21:46:00.002-08:00

You can also use the vmrun command.

You can use a script to start a VM, for example:

vmrun -T ws start "F:\VMWare-VMs\S1.vmx"

and you add the script at Windows startup.

More info about vmrun: http://www.sysadmit.com/2016/11/vmware-workstation-vmrun.html

Change Remote Desktop RDP Port

2018-11-19T09:33:00.001-08:00

Follow these steps to change the Remote Desktop server port:

Open up Registry Editor by clicking on the Start Button, type in regedit and then hit Enter.
In Registry Editor, navigate to HKEY_LOCAL_MACHINE, SYSTEM, CurrentControlSet, Control, Terminal Server, WinStations and RDP-Tcp.
Right click on the PortNumber dword and select Modify.
Change the base to Decimal and enter a new port between 1025 and 65535 that is not already in use.
Click OK and reboot.

仕女按摩，外出到旅館服務全身推拿油壓／男按摩師 ( 新竹竹北中壢桃園台北地區)

2017-03-30T11:39:00.007-07:00

仕女按摩，外出到旅館服務全身推拿油壓／男按摩師

( 新竹竹北中壢桃園台北地區)

Ben老師，，173/70。

單純素質高，體型健壯，不抽煙，不喝酒，

不吃檳榔，無體味，斯文有禮，貼心服務，

且手法純熟，提供尊重，安全，專業，溫柔服務。

Ben老師針對全身經絡穴位精油推拿按摩的服務周到，

平價收費，為仕女們省荷包，

讓您體驗備感呵護的關心。

小資族仕女們也能享受彷佛渾然忘我，CP值超高的服務，

可外出到府及旅館服務按摩，卸除您的疲憊與壓力。

特色：

(1) 改善睡眠、按摩腦部、放鬆腦神經壓力。

(2) 改善長期睡眠品質不佳，放鬆肩頸、腰背及全身疲勞。

(3) 針對長期的過度疲勞，造成的疲勞痠痛。

(4) 改善身體左右失衡而造成的肩頸僵硬、腰酸背痛等。

(5) 超高品質放鬆舒暢的享受。

服務對象：限女性

聯絡方式

Line : paulwu0117

電話: 0965705598

每次一人　全身經絡穴道、淋巴按摩油壓服務

旅館：90分鐘　NTD：2000元 (不含車資,車資另計)

按摩事前準備：

1.可預先自行盥洗，泡腳或蒸汽浴，以達到全身按摩最佳效果。

2.請著寬鬆純棉內褲(全程只著紙內褲為佳）或包浴巾即可。

@按摩流程：

燈光會調暗，先用毛巾蓋著，首先做背部指油壓，舒鬆經絡，

再來是正面油壓淋巴周圍，並依客戶需求及想要加強的部位，重點式按摩。

經由指壓、油壓、重點式按摩之順序，如此身心舒暢，方達最佳調理效果。

注意事項：

1.需事先預約，現場請一律先以台幣現金或LINE PAY, 網路銀行轉帳支付按摩費用。

2.當日預約需在"4小時前"詢問。

3.已確認預約者，請勿任意取消。

4.按摩基本時數以90分鐘為限，按摩部位可配合客戶需求。

5.到旅館者，請顧客自行找喜歡的旅館訂房及並付房費用。

6.生理期或懷孕期間，扭挫傷者，急性期中，不宜推拿。

7.飯後1小時內不宜推拿，按摩推拿結束後請多喝溫熱水。

8.長期的經絡不暢、過勞痠痛者，建議每1、2周預約一次，以達最佳調理效果。

9.異性SPA推拿按摩會從心理上到生理上產生一種變化，會調節內分泌，使仕女們的皮膚得到很大的改善。

10.預約後，您已認同上述的注意事項。

2017-03-30T11:38:00.001-07:00

Body Essential Oil Hydraulic Massage Male Masseur (north of Hsinchu)

Male masseur, 173/75, simple high quality, do not smoke, do not drink, do not eat betel nut,
Gentle and polite, caring service, the whole time does not steal the guests time, customer first, experience the care of care.
Can go out or go to the studio press to remove your fatigue and stress.

Line: paulwu0114

Massage costs: go out the basic two hours 1800 yuan, to the studio by two hours 1300 yuan. (Outside the county and then subsidize transportation)
Other costs: scraping and heat does not increase the price

Massage clothing: the first kimono anti-wear, oil pressure can wear paper underwear, do the back first, the front to see the guests have no need.

Massage process: the light will be dimmed, placed soft music, first covered with a towel on the back, the first to do acupressure, Shu pressure meridian, and then around the hydraulic lymph

Note:
1. There are disposable bed paper. Essential oil. Emulsion. Towel was. Paper underwear. Electric blanket.
2. Out of service to 2 hours as the basic unit.
3. Outside the massage object is currently only accepted female, Mr. can accompany his wife to go, waiting in the next.

[IIS][ASP.NET] 拒絕訪問Temp目錄

2016-08-04T01:22:00.003-07:00

創建BlogConfigurationSettings 的配置節處理程序時出錯: 拒絕訪問臨時目錄。以其運行XmlSerializer 的身份“IIS APPPOOL\www.cnblogs.com”沒有足夠的權限訪問臨時目錄。CodeDom 將使用此進程用於進行編譯的用戶帳戶，因此如果用戶對系統臨時目錄沒有訪問權限，則將無法編譯。使用Path.GetTempPath() API 可找到臨時目錄位置。

Access to the temp directory is denied. Identity 'IIS APPPOOL\www.cnblogs.com' under which XmlSerializer is running does not have sufficient permission to access the temp directory. CodeDom will use the user account the process is using to do the compilation, so if the user doesnt have access to system temp directory, you will not be able to compile. Use Path.GetTempPath() API to find out the temp directory location.

CS0016: 未能寫入輸出文件“c:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\root\946055b8\92eead15\App_global.asax.qakaesxx.dll”--“拒絕訪問。 ”

開始以為是“C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files”文件夾權限的問題，但怎麼設置這個權限也解決不了問題。

後來在應用程序池設置中將“加載用戶配置文件”（Load User Profile）設置為true，問題就解決。

[IIS][ASP.NET] 拒絕訪問Temp目錄

2016-08-04T01:22:00.001-07:00

創建BlogConfigurationSettings 的配置節處理程序時出錯: 拒絕訪問臨時目錄。以其運行XmlSerializer 的身份“IIS APPPOOL\www.cnblogs.com”沒有足夠的權限訪問臨時目錄。CodeDom 將使用此進程用於進行編譯的用戶帳戶，因此如果用戶對系統臨時目錄沒有訪問權限，則將無法編譯。使用Path.GetTempPath() API 可找到臨時目錄位置。

Access to the temp directory is denied. Identity 'IIS APPPOOL\www.cnblogs.com' under which XmlSerializer is running does not have sufficient permission to access the temp directory. CodeDom will use the user account the process is using to do the compilation, so if the user doesnt have access to system temp directory, you will not be able to compile. Use Path.GetTempPath() API to find out the temp directory location.

CS0016: 未能寫入輸出文件“c:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\root\946055b8\92eead15\App_global.asax.qakaesxx.dll”--“拒絕訪問。 ”

開始以為是“C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files”文件夾權限的問題，但怎麼設置這個權限也解決不了問題。

後來在應用程序池設置中將“加載用戶配置文件”（Load User Profile）設置為true，問題就解決。

Includes Files Dynamically

2016-07-29T00:15:00.001-07:00

下面說明，因為include 為SEVER SIDE SSI語法，所以前後的if、select判斷式都不會執行

http://www.learnasp.com/freebook/asp/inc.aspx

Include Files

The include option is the heart of making efficient ASP files and re-usable chunks. It basically
has two forms and now we will present the forms and their differences:


would include any file on your site (in this example, whatever.asp is in the web server's root directory)
but you must fully qualify the filename with a path.


can include the whatever.asp file in the directory of the script that contains the statement.
It ASSUMES the current directory!

Example #1
could include a file from sally's directory, even if the page with this statement is (for example)
in the /fred/finance folder.

Example #2:
will fail from fred's directory.

Example #3:
will succed from fred's directory but if the script that contains it is moved to a different level in the tree structure
it will fail to locate the file. INCLUDE VIRTUAL is better if a script may be moved and is immune to relative path issues.

IMPORTANT: Include files are always processed and inserted before ASP scripts on the page are calculated. Thus a page with many IFs and SELECT CASEs that selectively include files in fact always include the file before the script begins executing.

請參考下面的動態載入方式

Includes Files Dynamically

The include files are gathered and processed BEFORE any ASP code. Soif your code looks like this:

<%SELECT CASE
     CASE 1 %>    
     CASE 2 %>         CASE 3 %>    
<%END SELECT%>

Three includes are performed before any ASP code is executed.

YOU CANNOT DO:

<%
     whichfile="1"%> 

Though this is a reasonable idea.



We however have coded a workaround that is FREE you may find useful. The workaround is:

   filename=/learn/test/includedynamic.asp

How to Use JavaScript to Change a Cascading Style Sheet (CSS) Dynamically

2016-07-28T19:20:00.000-07:00

It may be useful sometimes to provide your visitors with the option to change the appearance of your website. Perhaps you want to provide theme support for your site. Or you may simply want to provide a bigger font size version of your site for older users who may not be able to read the small-sized text you use by default. This article describes how you can use JavaScript to dynamically change the cascading style sheets, or CSS, of your website.

Prerequisites

One of the assumptions I will make in this tutorial is that you know how to write HTML and CSS. You do not have to be highly proficient in either of these, but you should have at least a basic working knowledge. Some JavaScript knowledge is also necessary.

If you have not already done so, you may want to read the following articles as well. This guide was written as the part of a series of articles on how to provide alternate style sheets for your website and change them.

How to Allow Your Visitors to Switch Between Alternate CSS Styles / Themes. It deals with the CSS aspect of switching style sheets.

How to Use Cookies in JavaScript. Although not strictly part of the CSS style switcher series, the cookie management code provided in that article is used to preserve the theme selection that your visitors make on your site. Without setting a cookie, their CSS setting will not be retained when they go to the other pages on your website.

Steps to Adding a Style Sheet Switcher in JavaScript

Let's assume that we have the following style sheets defined in our `HEAD` section. This is the same code described and explained in the first instalment of this tutorial.

<link rel="stylesheet" type="text/css" title="blue" href="http://example.com/css/blue.css">
<link rel="alternate stylesheet" type="text/css" title="pink" href="http://example.com/css/pink.css">

HTML Code to Provide a Way for Your Users to Choose the Style Sheet

You will need to provide some way for your visitors to select the theme or CSS they want. There are many ways to do this, including the use of radio buttons, drop down selection boxes, normal submit buttons, text links, and so on. For usability reasons, you should not use things like checkboxes which suggests to users that they can simultaneously select a few themes and have them work together.
Here's an example of HTML code using normal submit buttons.

<form>
<input type="submit" onclick="switch_style('blue');return false;" name="theme" value="Blue Theme" id="blue">
<input type="submit" onclick="switch_style('pink');return false;" name="theme" value="Pink Theme" id="pink">
</form>
When the visitor clicks any of the buttons, the JavaScript `onclick` handler, `switch_style()`, will run. The function will be passed either 'blue' or 'pink' as its parameters, depending on which button is clicked. The words "blue" and "pink" correspond to the title attributes for the `link` elements referencing the style sheets.

JavaScript Function to Change Style Sheets

The actual JavaScript code needed to implement CSS style switching can be found below.

Note that this script includes the `set_cookie()` and `get_cookie()` functions from the How to Use Cookies in JavaScript article. For your convenience, I have already included those functions in the block of code above, so you do not need to copy and paste from that article. However, you may still want to read that article to understand the default settings and assumptions I make in my cookie code.
The `switch_style()` function essentially iterates through all your `link` tags looking for a style sheet with the same title as the text specified in its argument (parameter). If it matches, it sets a special property, called `disabled`, to false, thus enabling that style sheet. In the meantime, all other relevant style sheets are disabled. The function ignores all persistent style sheets as well as any non-style-sheet `link` tags, such as those used for your site's favicon.
When it finishes, it sets a cookie with the necessary information about the style sheet setting. By default, the name of the cookie is "style" and it is retained for 30 days. You can change this by altering the values of the `style_cookie_name` and `style_cookie_duration` variables at the start of the script. You should also change the value of the `style_domain`variable to that of your own domain.
To ensure that the visitors' style sheet settings remain when they visit other pages of your site, as well as when they reload the page, you will also need to add an `onload` attribute to your web pages' `body` tag. For example, change `<body>` to the following:

<body onload="set_style_from_cookie()">
This causes the browser to run the `set_style_from_cookie()` function when the page is loaded. The function merely checks for the style-setting cookie, and if present, switches the style sheets accordingly. Otherwise, it does nothing.

Demo

You can check out how the script works using the test copy loaded with this page. To change between the current style sheet used on thesitewizard.com and the older version, simply select the appropriate button below.

Note that the code used for this demo sets a cookie called "demo_theme" in your browser that is valid for only 1 day. The cookie will contain either the word "blue" or "grey", depending on which button you click. Your setting will only affect this page, and no other page on this site, since none of the other pages includes the style switcher JavaScript code.

ASP.Net : 如何追蹤執行時所花費時間

2016-07-25T23:01:00.001-07:00

介紹如何使用 Stopwatch 類別來追蹤執行時間，以及使用時的小技巧

我們常常會需要去追蹤一段code執行所花費的時間，
一般的做法會像這樣


 ////示範一 
 DateTime dtstart = DateTime.Now;                
                                            //// code
 System.Threading.Thread.Sleep(100);         
 TimeSpan ts = DateTime.Now - dtstart;  
 Response.Write(ts.TotalSeconds.ToString());


                                            
                                                這邊分享另一個類別 【Stopwatch】
                                                
                                            
 
////示範二             
    System.Diagnostics.Stopwatch sw =
                                            new 
    System.Diagnostics.Stopwatch();              
    sw.Start();                
                                            
//// code              
System.Threading.Thread.Sleep(100);                
sw.Stop();              
Response.Write(sw.Elapsed.TotalSeconds.ToString());


                                            
                                                一樣可以達到相同效果。
                                            
                                            
                                                那兩者的差異在哪呢，

                                                【Stopwatch】提供較高精確度的計量，

                                                如果硬體和OS支援高解析度效能計數器，Stopwatch 類別會使用該計數器來測量已耗用時間。

                                                不然，Stopwatch 類別會使用系統計時器來測量已耗用時間，

                                                並且可重複呼叫Start及Stop方法，來累積更多執行區間所耗用時間，

                                                然後利用【Elapsed】屬性取得累積耗用時間。
                                            
                                            
                                                

                                            
                                            
                                                再分享一下，

                                                為了方便在線上環境追蹤執行狀況，有時可以利用 #if DEBUG 搭配 Stopwatch，埋一些追蹤的code，

                                                只要將 web.config 的 debug mode 設定為 true，就可以輸出執行時間，

                                                在將 debug mode 設定為 false，就可以隱藏執行時間，類似作法如下
                                            
 

////示範三 #if DEBUG 搭配 Stopwatch 
#if DEBUG
System.Diagnostics.Stopwatch sw = new System.Diagnostics.Stopwatch();
sw.Start();  
#endif
//// code         
 System.Threading.Thread.Sleep(100);    
#if DEBUG 
sw.Stop();          
Response.Write(sw.Elapsed.TotalSeconds.ToString());  
#endif



                                                此範例是將時間直接輸出，

                                                各位可以修改將時間輸出到檔案或是別的地方。


                                        
                                            

                                            程式碼工作室  吳 Sir

                                            Skype: wu_chung_pin
                                        
                                        
                                            Line: paulwu0114
                                        
                                        
                                            亞太:0977387198
                                        
                                        
                                            電話:03-5509853
                                        
                                        
                                            傳真:03-5509853
                                        
                                        
                                            
                                                官方網址: http://www.runcode.com.tw



資料指標(CURSOR)
2016-07-21T20:00:00.001-07:00

/*** 資料指標(CURSOR) ***/


/* 1. 基本用法 */
/***********************************************************/
DECLARE cur1 CURSOR FOR SELECT PRODUCTID,PRODUCTNAME 
  FROM PRODUCTS --(1.宣告Cursor)

DECLARE @ProdId int, @ProdName VARCHAR(40),
        @Count NUMERIC(10,0)

OPEN cur1      --(2.開啟Cursor)
SET @Count = 0
FETCH NEXT FROM cur1 
    INTO @ProdId,@ProdName  --(3.抓取Cursor中之記錄資料)
WHILE @@FETCH_STATUS=0   /*0: Fetch成功 -1: Fetch失敗 
                          -2: 要Fetch之記錄已不存在(一般發生
                              在KEYSET之CURSOR) */ 
BEGIN
  PRINT CONVERT(CHAR(5),@ProdId)+' '+@ProdName
  SET @Count = @Count + 1
  FETCH NEXT FROM cur1 INTO @ProdId,@ProdName
END
PRINT ''
PRINT '共 '+ CONVERT(VARCHAR(10),@Count)+' 筆'

CLOSE cur1                  --(4.關閉Cursor)
DEALLOCATE cur1             --(5.移除Cursor)


/* 2. CURSOR 深入探討 */
/***********************************************************/

/* 2.1 Cursor宣告 */
/***********************************************************/
  /* 2.1.1 用SQL-92標準語法宣告 */
    /*===========================================*/
  DECLARE cur_name [INSENSITIVE] [SCROLL] CURSOR
  FOR select_statement
  [FOR {READ ONLY| UPDATE [OF col_name [,...n] ] } ]

  (註1) INSENSITIVE: 1.SQL Server會在Tempdb資料庫,
                     建立暫存資料表存放Cursor內容
                     (當其他使用者在Cursor開啟之後
                      才異動之資料,並不會反映於Cursor內容上);
                     2.此類Cursor不可用來更改或刪除資料
                     3.可加快資料讀取速度 
  (註2) SCROLL: 唯有此設定之Cursor,才可跳躍式地被讀取資料
                例如Fetch Fisrt/Last/Prior/Relative/Absolute
                (預設只能由前往後循序被讀取)
  (註3) FOR UPDATE OF ... : 指定資料表可異動之欄位


  /* 2.1.2 用T-SQL擴充語法宣告 */
    /*===========================================*/
  DECLARE cur_name CURSOR
  [LOCAL|GLOBAL]      /* Cursor 有效範圍(cursor_scope) */
                      --LOCAL: 當相關批次結束時,該Cursor自動被
                               SQL Server移除(Close and Deallocate)
                      --GLOBAL(預設):該Cursor可於整個登入連線過程
                                     中被使用
  [FORWARD_ONLY|SCROLL] /* 資料可否跳躍式讀取(scrollable) */
                        --FORWARD_ONLY: 相當於SQL-92未設定SCROLL者
                        --SCROLL: 相當於SQL-92之SCROLL

  [STATIC|KEYSET|DYNAMIC] /* Cursor內容是否會自動更新(model) */
                          --STATIC: 相當於SQL-92之INSENSITIVE者
                          --KEYSET: 1.只有鍵值欄位之資料存入暫存資料表,
                                      其他欄位內容可動態更新反映;
                                    2.當來源資料表之鍵值欄位被異動時,
                                      讀取Cursor中之對應記錄會產生錯誤
                                      (@@FETCH_STATUS => -2)
                          --DYNAMIC: 相當於SQL-92未設訂INSENSITIVE者
                     
  [READ_ONLY|SCROLL_LOCKS|OPTIMISTIC]
                          /* Cursor可否被異動(concurrency) */
                          --READ_ONLY: 相當於SQL-92之 FOR READ ONLY
                          --SCROLL_LOCKS: 經由Cursor讀取到的記錄皆被
                                          SQL Server自動鎖住(Lock);
                                          以確定資料修改或刪除不會被他人
                                          妨礙
                          --OPTIMISTIC:  1.經由Cursor讀取到的記錄不會被
                                           鎖住,但允許由此Cursor去更改
                                           資料;
                                         2.原始資料中之記錄若已被異動,再
                                           由Cursor去異動該筆記錄時會導致
                                           失敗
  
  FOR select_statement
  [FOR UPDATE [OF col_name [,...n] ] ]  --相當於SQL-92之 FOR UPDATE 


  ◎最簡單範例:
  DECLARE cur1 CURSOR FOR SELECT * FROM PRODUCTID 

  --> 預設設定:GLOBAL + FORWARD_ONLY + DYNAMIC + OPTIMISTIC
                          
                             

/* 2.2 Cursor開啟(Open) */
/***********************************************************/
  ◎建立Cursor與來源資料表之連結

  (註1)開啟INSENSITIVE 或 STATIC CURSOR: 
       SQL Server會在Tempdb資料庫,建立暫存資料表
       存放Cursor內容(當其他使用者在Cursor開啟之後
       才異動之資料,並不會反映於Cursor內容上)
  (註2)開啟KEYSET CURSOR:
       SQL Server只會將鍵值欄位資料存入暫存資料表



/* 2.3 Cursor關閉(Close) */
/***********************************************************/
  ◎解除Cursor與來源資料表之連結 



/* 2.4 Cursor移除(Deallocate) */
/***********************************************************/
  ◎從記憶體中移除Cursor定義 



/* 2.5. FETCH用法深入探討 */
/***********************************************************/
FETCH [NEXT             --(1) 預設 
                              (註: Cursor被Open時,
                                   記錄位置是在第一筆之前)
       PRIOR  
       FIRST
       LAST
       ABSOLUTE n
       RELATIVE n ]
[FROM] cur1 
[INTO @Var1,@Var2,... ] --(2) 省略INTO項,則抓取之資料
                              將傳回給前端應用程式

  --2.5.1 巢狀Cursor應用
  /*===========================================*/
DECLARE @cust_id VARCHAR(5), @ord_id INT, @ord_date DATETIME

/*** 外層 ***/
DECLARE cust_cur INSENSITIVE CURSOR FOR 
  SELECT CUSTOMERID   FROM CUSTOMERS 
  ORDER BY CUSTOMERID
OPEN cust_cur
FETCH cust_cur INTO @cust_id

WHILE @@FETCH_STATUS=0
BEGIN
  PRINT '客戶' + @cust_id + ' 訂單:'

  /*** 內層 ***/
  DECLARE ord_cur CURSOR FOR 
    SELECT ORDERID,ORDERDATE 
    FROM ORDERS 
    WHERE CUSTOMERID=@cust_id 
      -- @cust_id變數在左式之Cursor宣告時會以實際值取代
  OPEN ord_cur
  FETCH ord_cur INTO @ord_id,@ord_date
  WHILE @@FETCH_STATUS=0
  BEGIN
    PRINT '      ' + convert(varchar,@ord_id)+ ' '+ 
          convert(varchar,@ord_date,111)
    FETCH ord_cur INTO @ord_id,@ord_date
  END
  CLOSE ord_cur
  DEALLOCATE ord_cur
  /************/

  FETCH cust_cur INTO @cust_id
END

CLOSE cust_cur
DEALLOCATE cust_cur
   


/* 3. 透過CURSOR修改或刪除資料 */
/***********************************************************/
(註1)此Cursor不可是READ_ONLY

USE NORTHWIND
DROP TABLE PRODUCTS2
SELECT * INTO PRODUCTS2 FROM PRODUCTS

DECLARE @unitprc numeric(10,4)
DECLARE cur1 CURSOR FOR SELECT UNITPRICE FROM PRODUCTS2
OPEN cur1
FETCH cur1 INTO @unitprc 
WHILE @@FETCH_STATUS=0
BEGIN
 UPDATE PRODUCTS2 SET UNITPRICE = @unitprc*1.1
   WHERE CURRENT OF cur1

 FETCH cur1 INTO @unitprc
END
CLOSE cur1
DEALLOCATE cur1


/* 4. 預存程序之OUTPUT 參數使用Cursor變數 */
/***********************************************************/
CREATE PROC sp_EmpCur @cur_var CURSOR VARYING OUTPUT
AS
  Set @cur_var = CURSOR FOR SELECT EMPLOYEEID,LASTNAME+' '+FIRSTNAME FROM EMPLOYEES
  /* 上敘述產生區域性CURSOR,即此CURSOR只限被呼叫之程式使用
     (其他批次之程式不可使用) */
  Open @cur_var
GO

/***** 呼叫上述預存程序 *****/
DECLARE @cur_var CURSOR
DECLARE @empid int,@name VARCHAR(80)

EXEC sp_EmpCur @cur_var OUTPUT

FETCH NEXT FROM @cur_var INTO @empid, @name
WHILE @@FETCH_STATUS=0
BEGIN
  PRINT convert(varchar,@empid)+' '+@name
  FETCH NEXT FROM @cur_var INTO @empid, @name
END
 
/* 本批次結束後,CURSOR自動被Close及Deallocate */
GO


/* 5. Local Cursor與Global Cursor之命名空間 */
/***********************************************************/
--5.1 Global Cursor與Local Cursor可有相同的名稱
      當有同名之Cursor存在時,欲存取Global Cursor必須加上Global關鍵字

--5.2 實例示範 
DECLARE cur1 CURSOR FOR SELECT * FROM PRODUCTS
DECLARE cur1 CURSOR LOCAL FOR SELECT * FROM CUSTOMERS

OPEN cur1           --Local Cursor
FETCH cur1

OPEN GLOBAL cur1
FETCH GLOBAL cur1
CLOSE GLOBAL cur1
DEALLOCATE GLOBAL cur1





































Using a cursor with dynamic SQL in a stored procedure
2016-07-20T20:25:00.001-07:00
 
I have a dynamic SQL statement I've created in a stored procedure. I need to iterate over the results using a cursor. I'm having a hard time figuring out the right syntax. Here's what I'm doing.
SELECT @SQLStatement = 'SELECT userId FROM users'    DECLARE @UserId    DECLARE users_cursor CURSOR FOR  EXECUTE @SQLStatment --Fails here. Doesn''t like this    OPEN users_cursor  FETCH NEXT FROM users_cursor  INTO @UserId    WHILE @@FETCH_STATUS = 0  BEGIN    EXEC asp_DoSomethingStoredProc @UserId    END  CLOSE users_cursor  DEALLOCATE users_cursor
What's the right way to do this?




A cursor will only accept a select statement, so if the SQL really needs to be dynamic make the declare cursor part of the statement you are executing. For the below to work your server will have to be using global cursors.
Declare @UserID varchar(100)  declare @sqlstatement nvarchar(4000)  --move declare cursor into sql to be executed  set @sqlstatement = 'Declare  users_cursor CURSOR FOR SELECT userId FROM users'    exec sp_executesql @sqlstatement      OPEN users_cursor  FETCH NEXT FROM users_cursor  INTO @UserId    WHILE @@FETCH_STATUS = 0  BEGIN  Print @UserID  EXEC asp_DoSomethingStoredProc @UserId    FETCH NEXT FROM users_cursor --have to fetch again within loop  INTO @UserId    END  CLOSE users_cursor  DEALLOCATE users_cursor



程式碼工作室  吳 Sir
Skype: wu_chung_pin
Line: paulwu0114
  亞太:0977387198
電話:03-5509853
  傳真:03-5509853
官方網址: http://www.runcode.com.tw
  


SQL Server: combining multiple rows into one row
2016-07-20T09:16:00.001-07:00

I have a SQL query like this;
SELECT *   FROM Jira.customfieldvalue  WHERE CUSTOMFIELD = 12534  AND ISSUE = 19602
And that's the results;
What I want is; showing in one row (cell) combined all STRINGVALUE's and they are separated with a comma. Like this;
SELECT --some process with STRINGVALUE--  FROM Jira.customfieldvalue  WHERE CUSTOMFIELD = 12534  AND ISSUE = 19602    Araç Listesi (C2, K1 vb.Belgeler; yoksa Ruhsat Fotokopileri), Min. 5  araç plakası için İnternet Sorgusu, Son 3 Yıla Ait Onaylı Yıl Sonu  Bilanço + Gelir Tablosu, Son Yıl (Yıl Sonuna ait) Detay Mizanı, İçinde  Bulunduğumuz Yıla ait Ara Dönem Geçici Vergi Beyannamesi, Bayi Yorum  E-Maili, Proforma Fatura


You can achieve this is to combine For XML Path and STUFF as follows:
SELECT (STUFF((          SELECT ', ' + StringValue          FROM Jira.customfieldvalue          WHERE CUSTOMFIELD = 12534          AND ISSUE = 19602          FOR XML PATH('')          ), 1, 2, '')      ) AS StringValue
 
  


How Can I Tell What is Listening on a TCP/IP Port in Windows?
2016-07-20T09:05:00.004-07:00

Open up a command prompt and type in the following—you may have to open in Administrator mode to see all processes:

netstat -ab | more
a
b
c  
  


This will immediately show you a list, although it’s maybe a little complicated. You’ll see the process name in the list, and you can search for it.

You can also use this other method, which takes an extra step, but makes it easier to locate the actual process:


netstat -aon | more





If you look on the right-hand side, you’ll see where I’ve highlighted the list of PIDs, or Process Identifiers. Find the one that’s bound to the port that you’re trying to troubleshoot—for this example, you’ll see that 0.0.0.0:80, or port 80, is in use by PID 4708.



Now you can simply open up Task Manager—you might have to use the option to Show Processes for All Users, and then you’ll be able to find the PID in the list. Once you’re there, you can use the End Process, Open File Location, or Go to Service(s) options to control the process or stop it.






You can also use CurrPorts to directly kill the process if you want.

Download CurrPorts from nirsoft.net


64/32 BIT ODBC 設定
2016-07-20T09:05:00.001-07:00

最近把手邊維護的系統做一個升級，從原本的 Windows Server 2003 32bit 升級到 Windows Server 2008 64bit，由於該系統中有很多的程式會透過 ODBC 連線資料庫，所以想說依照先前的設定方法設定就好，但是卻發生生程式可以跑但是卻無法正常連線資料庫的狀況，經過同事提點才知道 ODBC 設定是有分 32/64 bit 的。

通常設定 ODBC，就是開啟 控制台->系統管理工具-> ODBC 設定 -> 新增







如果你的系統是 『64位元的作業系統』但是程式是『32位元』，雖然設定的方法一樣，但是是要開啟 C:\Windows\SysWOW64\odbcad32.exe 來設定『32位元的ODBC』，由於 32/64 ODBC設定的路徑不一樣，預設的路徑是設定『64位元的ODBC』，所以要注意這一點，並且也要注意 ODBC Driver 的版本。

64 位元 ODBC 位置：C:\Windows\System32\odbcad32.exe
32 位元 ODBC 位置：C:\Windows\SysWOW64\odbcad32.exe 






009 在IIS7中顯示ASP偵錯訊息
2016-07-20T09:04:00.003-07:00

















在IIS7中顯示ASP偵錯訊息


最近接到一個案子，是學校的案子，所以因為學校的政策關係，沒辦法使用我比較熱悉的ASP.net，只能硬著頭皮，用高職學的ASP來寫程式，而我的作業系統上WINDOWS 7內建的是IIS 7 。但是發現了一個問題，當我程式發生錯誤的時候他出現很不討喜的錯誤訊息

An error occurred on the server when processing the URL. Please contact the system administrator.

If you are the system administrator please click here to find out more about this error.

 

我本人之前還笨笨的把他移到IIS 5上去執行，這樣來來回回浪費了不少時間！




原來，在IIS 7中 ASP的偵錯訊息是預設關閉的




只要在IIS 7 中你需要改的站台中



看到ASP這個按鈕點下去



有一個「將錯誤傳送到瀏覽器」

把他改成True

之後套用！




你在開啟一次你錯誤的網頁






















IIS 8.0 Using ASP.NET 3.5 and ASP.NET 4.5
2016-07-20T09:03:00.001-07:00

Problem

Windows Server 2012 includes .NET Framework 4.5 by default, as well as optional installation of the .NET 3.5 Framework. Developers frequently need to run mixed web applications across multiple .NET Framework versions.

Solution

IIS 8.0 on Windows Server 2012 runs ASP.NET applications on all .NET Framework versions supported on Windows Server 2012. This means ASP.NET applications can run on IIS 8.0 using either .NET Framework 3.5, or .NET Framework 4.5. IIS 8.0 hosts versions of the .NET Framework in different application pools, thus allowing multiple ASP.NET applications with different .NET Framework versions to run simultaneously on Windows Server 2012.

IIS 8.0 also supports managing both ASP.NET 3.5 and ASP.NET 4.5 applications using both the graphical IIS Manager tool as well as IIS' command-line management tools. Refer to this article for more information.

Step by Step Instructions

Prerequisites:

IIS is installed on Windows Server 2012. To learn more about installing IIS 8, see Installing IIS 8 on Windows Server 2012.


SETTING UP IIS 8.0 WITH SUPPORT FOR ASP.NET 3.5 AND ASP.NET 4.5

In Windows Server 2012, both the .NET Framework 3.5 and .NET Framework 4.5 are natively recognized by the operating system. This means both UI-based and command-line driven setup can be used to turn on both versions of the .NET Framework, as well as enabling integration of both versions of ASP.NET with IIS 8.0.

For this walkthrough we will use the new Server Manager UI in Windows Server 2012 Server to demonstrate enabling both ASP.NET 3.5 and ASP.NET 4.5 on IIS 8.0.

When you first login to a new Windows Server 2012 machine, the new Server Manager UI will display. Click add roles as shown below:

On the first screen of Add Roles and Features Wizard, click Next. This display a page where you select the desired installation type. Choose either Role-based or Feature-based installation as shown below:

Click Next. The next screen of the wizard asks you to choose the server that you are configuring.
On the next wizard step you will be asked to select one or more server roles. Scroll down in the Roles list, and make sure to check the Web Server (IIS) checkbox as shown below:

Click Next to proceed to the next step, which enables you to select additional specific features to install on the server. Click Next again and proceed to the next step.
The next wizard step displays some introductory information about the Web Server (IIS)role. Click Next again and proceed to the next step. Now you should be at a wizard step that looks like the following:

Note that a number of default sub-features for IIS have already been turned on because you selected the Web Server (IIS) server role earlier. However we want to enable both ASP.NET 3.5 and ASP.NET 4.5 to run on IIS 8.0, so we need to enable some additional IIS related features. Scroll down in the Role services list until the Application Development node is showing. This node is collapsed initially, click on the node and expand it so that its children are showing:

The Application Development node is where we enable ASP.NET integration with IIS. Note that there are a few checkboxes in the feature list with similar names. The pair of checkboxes that are of interest for this walkthrough are:
ASP.NET 3.5 - This option enables ASP.NET 3.5 to run on IIS 8.0. Note that with Windows Server 2012, .NET Framework 3.5 is not available as a part of the base OS image. Instead, the payload is downloaded from the Internet and you need to connect to the Internet.
ASP.NET 4.5 - This option enables ASP.NET 4.5 to run on IIS 8.0.


First click the ASP.NET 3.5 check box. When you do so an additional dialog box will popup as shown below:

Since ASP.NET 3.5 is integrated into the Windows Server 2012 setup, Windows Server 2012 knows all of the related dependencies necessary to enable ASP.NET 3.5 on IIS 8.0. This popup dialog is just showing you what will be automatically pulled in and installed. Since we do want ASP.NET 3.5 enabled, click Add Required Features.
Next, click the ASP.NET 4.5 check box in the Role services feature list. The end result of clicking both ASP.NET related checkboxes is shown below:

Even though you only directly selected the ASP.NET 3.5 and ASP.NET 4.5 features, the wizard automatically turned on a number of other items. This is done automatically so that developers do not have to explicitly choose the various component pieces needed to "assembly" of ASP.NET on Windows Server 2012. At this point click Next to accept the changes.
The Confirm installation selections step displays a list of all of features that are installed if you accept the changes.

At this point, click Install to accept the changes and install full ASP.NET support on Windows Server 2012.
Since the installation will take a small amount of time to complete, the wizard displays a progress dialog while the installation progresses:

After a few minutes the wizard shows that the installation has completed:

At this point, you can click Close and exit the wizard.


EXPLORING THE IIS 8.0 INSTALLATION

With both IIS 8.0 and ASP.NET integration installed we can take a look at the basic ASP.NET footprint for IIS 8.0.

From the Windows Start menu select All Programs and then expand the Administrative Tools menu. In the resulting list, find Internet Information Services (IIS) Manager and select it to launch the graphical IIS management tool:

Once the IIS Manager starts up, expand the server node in the left-hand window so that both the Application Pools node and Sites node are showing. When you do this the IIS Manager will popup a dialog asking if you want to stay connected with the latest Web Platform Components. For this walkthrough, you can click No. However on real-world installations you will probably want to click Yes so that the Web Platform Installer is available for your use to download various IIS extensions such as the URL Rewrite Module. At this point the IIS Manager looks like the following picture:

Click the Application Pools node to display the application pools that have now been installed for use by IIS 8.0:

You can see that six different application pools are created by default when both ASP.NET 3.5 and ASP.NET 4.5 are enabled for IIS 8.0. Four of the applications are new for IIS 8.0, while two other application pools have been carried forward from previous Windows releases.
Note that although the .NET Framework Version column shows "v2.0" and "v4.0" for .NET Framework versions, these equate to ASP.NET 3.5 and ASP.NET 4.5. Due to the internals of how application pools bind to .NET Framework versions, the actual version name written to configuration (and thus displayed in the tool) corresponds to the original .NET Framework file version.
Classic .NET AppPool and DefaultAppPool existed in previous versions of Windows, and thus continue to be created for IIS 8.0. Note however that since .NET 4.5 is the default .NET Framework for use by Windows Server 2012, the "DefaultAppPool" on IIS 8.0 also defaults to using the newer version of the .NET Framework.
The other four application pools are new in Windows Server 2012. There are two application pools for running .NET Framework 3.5 (.NET v2.0 and .NET v2.0 Classic), and two application pools for running .NET Framework 4.5 (.NET 4.5 and .NET 4.5 Classic).
The difference between "classic" and "not classic" application pools is the managed pipeline mode supported in each application pool type. The two application pools ending in "Classic" support the older Windows Server 2003-era classic pipeline mode for ASP.NET, while the other two application pools use the newer integrated pipeline mode for ASP.NET introduced in Vista/IIS7.0.


Exploring a little bit further, expand the Sites node in the left-hand side of the screen so that the Default Web Site node is visible:

Default installations of IIS always have a "Default Web Site" configured to listen for HTTP requests on port 80. Drill into the "Default Web Site" to see what version of ASP.NET it supports by default. Right-click Default Web Site, then select Manage Website, and select Advanced Settings as shown below:

The Advanced Settings dialog pops up, showing (amongst other things) the application pool used to run the "Default Web Site". As shown in the picture below, the "Default Web Site" runs in the application pool called "DefaultAppPool":

If you click the small ellipsis-button on the right-hand side of the application pool , an additional dialog pops up displaying more information about the "DefaultAppPool". As noted earlier the "DefaultAppPool" defaults to ASP.NET 4.5 for IIS 8.0, so ASP.NET 4.5 applications deployed in the "Default Web Site" will work without any further configuration.

At this point, click Cancel to cancel both the Select Application Pool dialog, and theAdvanced Settings dialog.


RUNNING BOTH ASP.NET 3.5 AND ASP.NET 4.5 APPLICATIONS

Now that you have explored the setup state of IIS 8.0, try running some sample ASP.NET code to confirm that both ASP.NET 3.5 and ASP.NET 4.5 applications can run simultaneously on a single IIS 8.0 installation.

Sample code for both ASP.NET 3.5 and ASP.NET 4.5 is contained in the following .zip:





First, set up a simple ASP.NET 3.5 application on IIS 8.0:

Open the "examples.zip" file.
In Windows Explorer on your Windows Server 2012 machine, navigate to the "wwwroot" directory for your IIS installation. For example if you installed IIS on the "C:\" drive, the "wwwroot" directory will be at "c:\inetpub\wwwroot".
Copy the folder "example35" from "examples.zip", and paste it into the directory "c:\inetpub\wwwroot". When you are done the directory structure should look like the following:

The newly created "example35" folder needs to be configured as an ASP.NET 3.5 application in the IIS Manager. Go back to the IIS Manager window, click on the Default Web Site node, and select Refresh. The treeview of child nodes under the Default Web Site now shows the "example35" folder:

Right-click the example35 folder and select Convert to Application:

The Add Application dialog will pop up. By default all directories within Default Web Siteare part of the application pool called DefaultAppPool. This means that newly created folders containing ASP.NET run as ASP.NET 4.5 applications by default.

Since we want to run the example35 folder as an ASP.NET 3.5 application, the application pool needs to be changed. Click Select, and the Select Application Pool dialog that pops up. Change the application pool to .NET v2.0 as shown below:

Click OK button to accept the application pool change, and then click OK again to commit the changes to IIS. The IIS Manager window appears again. In the treeview showing "Default Web Site", the icon for "example35" is changed to indicate it is now a separate ASP.NET application.

At this point start an instance of Internet Explorer and navigate to the following Url:
http://localhost/example35
After a short pause the application displays a list of .NET Framework features supported in this application.
in Windows Explorer, if you navigate to the "c:\inetpub\wwwroot\example35" directory, you can use notepad to look at the code for "default.aspx" and the information in "web.config". For example, the contents of web.config include directives that configure the .NET Framework compilers to run in "3.5" mode. The .NET Framework code in "default.aspx" demonstrates some C# constructs that were introduced in .NET 3.5 - specifically LINQ-to-Object queries.


Now that there is an ASP.NET 3.5 application running, you can create a second ASP.NET application, but this time configure it to use .NET 4.5.

Go back to the Windows Explorer window that has the .zip file "examples.zip" open.
Open up the contents of the "example45" folder.
In the second Windows Explorer window that you have open, navigate to "c:\inetpub\wwwroot".
Copy the "default.aspx" file from the .zip file and paste it directly into "c:\inetpub\wwwroot". The folder contents for "c:\inetpub\wwwroot" should now look like:

Now go back to Internet Explorer and navigate to the following Url:
http://localhost/default.aspx
After a short pause a second application pool will start running an ASP.NET 4.5 application for the "Default Web Site". The browser once again displays a list of .NET Framework features supported in this application with a new entry at the end of the list for dynamically typed variables (i.e. the dynamic keyword introduced in .NET 4.0/4.5). Notice that unlike the "example35" application that required special web.config entries, no web.config file was required to configure and run the "default.aspx" page in the "Default Web Site". This is because .NET Framework 4.5 is the default .NET Framework used by ASP.NET applications in IIS 8.0, and as a result no extra configuration is required.
If you use Notepad to open the "default.aspx" page that you just copied, you will also see a few changes compared to the version in the "example35" directory. There are no namespace directives at the top of the page since the .NET Framework 4.5 is the default on IIS 8.0. The code on the page demonstrates using a dynamic variable, which is a compiler concept introduced in .NET 4.0/4.5.



偵測出ASP.NET設定沒有套用到整合式Managed管線模式
2016-07-20T09:02:00.004-07:00

執行ASP.NET應用程式時，發生【HTTP錯誤500.21-Internal Server Error，處理常式 "PageHandlerFactory-Integrated" 的模組清單中有錯誤的模組 "ManagedPipelineHandler"】錯誤的故障排除

33343
 0
IIS
 檢舉文章




本文將介紹在執行ASP.NET應用程式時，發生【HTTP錯誤500.21-Internal Server Error，處理常式 "PageHandlerFactory-Integrated" 的模組清單中有錯誤的模組 "ManagedPipelineHandler"】錯誤的故障排除


當您嘗試在IIS 7.5上執行ASP.NET應用程式（以.NET Framework 4.0為例）時，遇到處理常式 "PageHandlerFactory-Integrated" 的模組清單中有錯誤的模組 "ManagedPipelineHandler"的錯誤時該如何排除，本文將提供可能的解決方案。



若您是先安裝.NET Framework 4.0獨立安裝程式再啟用IIS角色就可能遇到上述的錯誤訊息，原因在於IIS角色在啟用時並未更新現有的應用程式以使用ASP.NET 4 版本的應用程式集區 ，以及在 IIS Metabase 中未更新傳統模式及 IIS 整合模式下ASP.NET 4的處理常式與指令對應，以至於出現上述的錯誤訊息。

解決步驟如下：

Win + R開啟執行視窗後輸入cmd按確定，開啟命令提示字元。
依據作業系統的位元數切換至相對應的目錄。
32位元的作業系統請切換至【%systemroot%\Microsoft.NET\Framework】。
64位元的作業系統請切換至【%systemroot%\Microsoft.NET\Framework64】。


輸入【aspnet_regiis -i】後按ENTER，下圖的為在64位元的作業系統下所做的範例。






依照上述步驟即可於IIS 7.5上執行ASP.NET 4.0應用程式。以本文所舉的情境為例，建議要讓ASP.NET順利在IIS 7.5上執行的設定步驟如下：

啟用IIS角色，並選取ASP.NET角色服務。
安裝.Net Framework 4.0獨立安裝程式。


【參考資料】

ASP.NET IIS 註冊工具 (Aspnet_regiis.exe)








error


在本機電腦上安裝及解除安裝 ASP.NET 的管理公用程式。

Copyright (C) Microsoft Corporation.  著作權所有，並保留一切權利。

開始安裝 ASP.NET (4.0.30319.0)。

這個作業系統版本不支援這個選項。系統管理員應該改用 [開啟或關閉 Windows 功能] 對

話方塊、[伺服器管理員] 管理工具或 dism.exe 命令列工具，隨著 IIS8 一起安裝/解除安

裝 ASP.NET 4.5。如需詳細資訊，請參閱 http://go.microsoft.com/fwlink/?LinkID=2167

71。

完成安裝 ASP.NET (4.0.30319.0)。




C:\Windows\Microsoft.NET\Framework\v4.0.30319>aspnet_regiis -i

Microsoft (R) ASP.NET RegIIS 版本 4.0.30319.0

在本機電腦上安裝及解除安裝 ASP.NET 的管理公用程式。

Copyright (C) Microsoft Corporation.  著作權所有，並保留一切權利。

開始安裝 ASP.NET (4.0.30319.0)。

這個作業系統版本不支援這個選項。系統管理員應該改用 [開啟或關閉 Windows 功能] 對

話方塊、[伺服器管理員] 管理工具或 dism.exe 命令列工具，隨著 IIS8 一起安裝/解除安

裝 ASP.NET 4.5。如需詳細資訊，請參閱 http://go.microsoft.com/fwlink/?LinkID=2167

71。

完成安裝 ASP.NET (4.0.30319.0)。




How do I enable upload of large files in classic ASP on IIS 7?
2016-07-20T09:02:00.001-07:00

Recently I had to get an old ASP application working in IIS 7.5 on a W2K8 server. Almost everything works fine, except that I can't seem to get it to accept uploads larger than ~200kB. I did find a setting, that from what I can understand should to the trick, in the applicationHost.config, I set the max request size to 100 MB like this:
<location path="TheNameOfMySite">
    <system.webServer>
        <security>
            <requestFiltering>
                <requestLimits maxAllowedContentLength="104857600" />
            </requestFiltering>
        </security>
    </system.webServer>
</location>

Unfortunately, this seems to do nothing at all, it still refuses to accept any files larger than about 200 kB, and in the log file it gives this error message:

ASP_0104_:_80004005|Operation_not_Allowed

Googling that points to increasing the maxAllowedContentLength as I have done above. So I'm fresh out of ideas, but confident that the clever stackoverflow crowd can solve this in less time than it took for me to write this question.




The maxAllowedContentLength controls how much data is allowed to be sent in a response. However you want to control how much can be accepted in a request. This is handled by themaxRequestEntityAllowed attribute of the limits element in the asp section of the config file. An example might look like:-
<system.webServer>
  <asp>
     <cache diskTemplateCacheDirectory="%SystemDrive%\inetpub\temp\ASP Compiled Templates" />
     <limits scriptTimeout="00:02:00"
        queueConnectionTestTime="00:00:05"
        requestQueueMax="1000"
        maxRequestEntityAllowed="104857600"
        />
  </asp>

You can configure this in the IIS7 manager under the "Limit Properties" category in the property grid for the ASP feature. Alternatively you can use a command line:-
appcmd set config /section:asp /limits.maxRequestEntityAllowed:104857600

Note that extending this value increase the window for DOS attack where the attacker sends large content to the server so don't be tempted to extend this beyond what you really need.


IIS 7.0 設定顯示詳細錯誤訊息 (HTTP 500 - 內部伺服器錯誤)
2016-07-20T09:01:00.001-07:00
IIS 的 站台
- 錯誤網頁(要點兩下進去)
- 編輯功能設定(在右邊動作區塊)
- 請選擇"詳細錯誤"(無論本機遠端都顯示錯誤, 預設是是本機顯示錯誤,遠端不顯示錯誤)





設定錯誤 無法讀取設定檔案，因為權限不足
2016-07-20T09:00:00.004-07:00
1  檢查看看檔案夾是否是唯讀, 不可以是唯讀
    我在IIS 管理員 console內, 將wwwroot及我站台的目錄
    權限都取消唯讀.
2. 然後在"安全性"內, 新增一個Users的使用者.


IIS7.0 ASP 啟用上層路徑
2016-07-20T09:00:00.000-07:00

http://itgroup.blueshop.com.tw/inmarkblue/markshu?n=convew&i=6684





開啟IIS管理員



ASP/ 開啟功能



將啟用上層路徑 及 將錯誤傳送到瀏覽器 選取








部署傳統 ASP 伺服器
2016-07-20T08:58:00.001-07:00

若要部署傳統 ASP 伺服器


使用 Web Platform Installer (Web PI) 可以讓您輕鬆安裝 IIS 以及在 IIS 上執行的應用程式。 因為 Web PI 會安裝最新版本的可用 Web Platform 提供項目，所以只需要幾個簡單的按選動作，您就可以下載並安裝任何新工具或更新。 如需深入了解 Web PI，請參閱深入了解並安裝 Web PI (英文)。

您也可以藉由使用 Windows 使用者介面 (UI) 或是從命令列來執行這個程序。

若要在 Windows Server 2008 或 Server 2008 R2 中使用 UI



按一下 [開始]，指向 [系統管理工具]，然後按一下 [伺服器管理員]。


在 [角色摘要] 中，按一下 [新增角色]。


使用 [新增角色精靈] 新增 [網頁伺服器 (IIS)] 角色。

如需如何安裝預設 IIS 7 網頁伺服器的詳細資訊，請參閱部署靜態內容伺服器 (IIS 7)。


在 [選取角色服務] 頁面上，注意預設安裝之預先選擇的角色服務，然後選取下列其他角色服務：

ASP

要求篩選

ISAPI 擴充程式




在 [要安裝的功能摘要] 頁面上，確認您所做的選擇，然後按一下 [安裝]。


在 [安裝結果] 頁面上，確認成功完成要安裝的網頁伺服器 (IIS) 角色以及所需的角色服務，然後按一下 [關閉]。


若要確認 IIS 安裝成功，請將下列網址輸入網頁瀏覽器：

http://localhost

您應該會看見預設的 IIS 7 歡迎使用畫面。




若要在 Windows Vista 或 Windows 7 中使用 UI



按一下 [開始]，然後按一下 [控制台]。


在 [控制台] 中，按一下 [程式集]，再按一下 [開啟或關閉 Windows 功能]。


在 [Windows 功能] 對話方塊中，按一下 [Internet Information Services] 以安裝預設功能，然後選取下列其他功能：

ASP

要求篩選

ISAPI 擴充程式




按一下 [確定]，關閉 [Windows 功能] 對話方塊。


若要確認 IIS 安裝成功，請將下列網址輸入網頁瀏覽器：

http://localhost

您應該會看見預設的 IIS 歡迎使用畫面。




若要使用命令列



將下列命令輸入成一個指令碼：

Start /w pkgmgr /iu:IIS-WebServerRole;IIS-WebServer;IIS-CommonHttpFeatures;IIS-StaticContent;IIS-DefaultDocument;IIS-DirectoryBrowsing;IIS-HttpErrors;IIS-ApplicationDevelopment;IIS-ASP;IIS-ISAPIExtensions;IIS-HealthAndDiagnostics;IIS-HttpLogging;IIS-LoggingLibraries;IIS-RequestMonitor;IIS-Security;IIS-RequestFiltering;IIS-HttpCompressionStatic;IIS-WebServerManagementTools;IIS-ManagementConsole; WAS-WindowsActivationService;WAS-ProcessModel;WAS-NetFxEnvironment;WAS-ConfigurationAPI






An error occurred on the server when processing the URL. Please contact the system administrato
2016-07-20T08:57:00.002-07:00

在WINDOWS7或SERVER2008上安裝了IIS7.5，調試ASP程序時出現以下錯誤：



    An error occurred on the server when processing the URL. Please contact the system administrator



    解决方法如下：



    設置方法一:



    以管理員身份運行CMD，將目錄定位到%windir%\system32\inetsrv\，然後執行appcmd set config -section:asp -scriptErrorSentToBrowser:true。

    %windir%\system32\inetsrv\appcmd set config -section:asp -scriptErrorSentToBrowser:true



    設置方法二:



    打開IIS7的asp設置，展開“調試屬性”選項，“將錯誤發送到瀏覽器”這項默認的是False，改为True，然後點右側的應用！如圖所示：







    通過以上設置後，再從瀏覽時打開出錯ASP頁面時就能看到頁面出錯的詳細信息，方使調試。如果是公開的Web服務器建議不要打開此選項，以防出錯信息被他人利用。

paulwu0115

[ASP.NET]利用configSource將web.config的connectionStrings移到另一個config檔來維護

201207232016微軟教你免費用永久使用測試版的 Terminal Licensing

Is it possible to autostart a VMware virtual machine in background as a Windows service, and shut it down elegantly when Windows shuts down?

Change Remote Desktop RDP Port

仕女按摩，外出到旅館服務 全身推拿油壓／男按摩師 ( 新竹 竹北 中壢 桃園 台北地區)

[IIS][ASP.NET] 拒絕訪問Temp目錄

[IIS][ASP.NET] 拒絕訪問Temp目錄

Includes Files Dynamically

How to Use JavaScript to Change a Cascading Style Sheet (CSS) Dynamically

Prerequisites

Steps to Adding a Style Sheet Switcher in JavaScript

HTML Code to Provide a Way for Your Users to Choose the Style Sheet

JavaScript Function to Change Style Sheets

Demo

ASP.Net : 如何追蹤執行時所花費時間

資料指標(CURSOR)

Using a cursor with dynamic SQL in a stored procedure

SQL Server: combining multiple rows into one row

How Can I Tell What is Listening on a TCP/IP Port in Windows?

64/32 BIT ODBC 設定

009 在IIS7中顯示ASP偵錯訊息

IIS 8.0 Using ASP.NET 3.5 and ASP.NET 4.5

Problem

Solution

Step by Step Instructions

Prerequisites:

SETTING UP IIS 8.0 WITH SUPPORT FOR ASP.NET 3.5 AND ASP.NET 4.5

EXPLORING THE IIS 8.0 INSTALLATION

RUNNING BOTH ASP.NET 3.5 AND ASP.NET 4.5 APPLICATIONS

偵測出ASP.NET設定沒有套用到整合式Managed管線模式

執行ASP.NET應用程式時，發生【HTTP錯誤500.21-Internal Server Error，處理常式 "PageHandlerFactory-Integrated" 的模組清單中有錯誤的模組 "ManagedPipelineHandler"】錯誤的故障排除

How do I enable upload of large files in classic ASP on IIS 7?

IIS 7.0 設定顯示詳細錯誤訊息 (HTTP 500 - 內部伺服器錯誤)

設定錯誤 無法讀取設定檔案，因為權限不足

IIS7.0 ASP 啟用上層路徑

部署傳統 ASP 伺服器

若要部署傳統 ASP 伺服器

若要在 Windows Server 2008 或 Server 2008 R2 中使用 UI

若要在 Windows Vista 或 Windows 7 中使用 UI

若要使用命令列

An error occurred on the server when processing the URL. Please contact the system administrato

仕女按摩，外出到旅館服務全身推拿油壓／男按摩師 ( 新竹竹北中壢桃園台北地區)

設定錯誤無法讀取設定檔案，因為權限不足