尊重友善包容

1 129810 2 86534 3 69567 4 68592 5 67887 6 63032 7 63322 8 61738 9 65949 10 78690 自已整左個program仔去試concurreny send xps job..上面係不同concurrency的結果.. class XPSPrintTest     {         static Stopwatch completeStopWatch = new Stopwatch();         static bool Done = false;         static object jj = new object();         static object intLock = new object();         const int targetCounter = 100;         static int _completeCounter = 0;         static int CompleteCounter { get             {                 lock(intLock)                 {           ...

https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/web/applicationpool-element-web-settings C:\Windows\Microsoft.NET\ Framework64 \ v4.0.30319 \aspnet.config ^自已執生 The 64-bit runtime uses a different machine.config. The basic rules are this: ASP.NET 1.x uses  %WINDIR%\Microsoft.NET\Framework\v1.1.4322 ASP.NET 2.0 / 3.5 x86 uses  %WINDIR%\Microsoft.NET\Framework\v2.0.50727 ASP.NET 2.0 / 3.5 x64 uses  %WINDIR%\Microsoft.NET\Framework64\v2.0.50727 ASP.NET 4.0 / 4.5.x x86 uses  %WINDIR%\Microsoft.NET\Framework\v4.0.30319 ASP.NET 4.0 / 4.5.x x64 uses  %WINDIR%\Microsoft.NET\Framework64\v4.0.30319 For ASP.NET 5.0 using the Full CLR, this will be the same as the ASP.NET 4.0 locations since the .NET Framework 4.6 is a drop in replacement for 4.5. If ASP.NET 5.0 is running on the CoreCLR, there is no concept of a machine.config file. Which version of ASP.NET you use depends on your ASP.NET Tab (IIS 6) or AppPool (IIS 7+) x64 ...