.net

Winforms Could not load file or assembly 'Microsoft.ReportDesigner, Version=10.0.0.0' in VS2012

假如想象 提交于 2021-02-18 20:15:10
问题 This is driving me nuts. I have a winforms app build in VS2012 targeting .NET 4.5. On a few forms I have to use a ReportViewer. At first I worked with ReportViewer for 2012 (version 11.0.0.0). All working fine. However, my client doesn't want to install this version on their workstations yet because this version uses the CLR Types SQL 2012. Don't ask me why, but I have to accept this for now. So I decided to use the previous reportviewer version 10.0.0.0. I downloaded the redistributional

Detecting/Diagnosing Thread Starvation

荒凉一梦 提交于 2021-02-18 20:13:39
问题 I am doing some performance/scalability testing of an IIS application that occasionally seems to slow down to a crawl in production. I'm able to reproduce the slowness consistently using NUnit. CPU and Memory do not spike during the testing, or when the slowness occurs in production. My strong suspicion is that the application is suffering from thread starvation, since it does not appear to be CPU, Memory, I/O, or database access that is causing the bottleneck. I do see signs of what appear

Detecting/Diagnosing Thread Starvation

假如想象 提交于 2021-02-18 20:13:34
问题 I am doing some performance/scalability testing of an IIS application that occasionally seems to slow down to a crawl in production. I'm able to reproduce the slowness consistently using NUnit. CPU and Memory do not spike during the testing, or when the slowness occurs in production. My strong suspicion is that the application is suffering from thread starvation, since it does not appear to be CPU, Memory, I/O, or database access that is causing the bottleneck. I do see signs of what appear

Detecting/Diagnosing Thread Starvation

点点圈 提交于 2021-02-18 20:13:03
问题 I am doing some performance/scalability testing of an IIS application that occasionally seems to slow down to a crawl in production. I'm able to reproduce the slowness consistently using NUnit. CPU and Memory do not spike during the testing, or when the slowness occurs in production. My strong suspicion is that the application is suffering from thread starvation, since it does not appear to be CPU, Memory, I/O, or database access that is causing the bottleneck. I do see signs of what appear

Parallel.For partitioning

会有一股神秘感。 提交于 2021-02-18 19:42:56
问题 How is partitioning done for something like Parallel.For(0, buffer.Length, (i)=> buffer[i] = 0); My assumption was that for an n core machine, work would be partitioned n way and n threads will carry out the work payload. Which means for example buffer.Length = 100 and n = 4, each thread will get 0-24, 25-49, 50-74, 75-99 blocks. (100 element array is an example to illustrate partitioning, but please consider an array of millions of items.) Is this a fair assumption? Please discuss. I noticed

SChannel issue with Windows 10

杀马特。学长 韩版系。学妹 提交于 2021-02-18 18:55:56
问题 I have an application that uses the System.Net.Security.SslStream class to make a secure connection to a server. On Windows 7 and Windows 8/8.1, this works fine. On Windows 10, the call to SslStream.AuthenticateAsClient throws an exception - "AuthenticationException: A call to SSPI failed, see inner exception". The inner exception is "Win32Exception: The Local Security Authority cannot be contacted". This is not specific to one Windows 10 machine. I thought that it might have something to do

SChannel issue with Windows 10

一笑奈何 提交于 2021-02-18 18:55:25
问题 I have an application that uses the System.Net.Security.SslStream class to make a secure connection to a server. On Windows 7 and Windows 8/8.1, this works fine. On Windows 10, the call to SslStream.AuthenticateAsClient throws an exception - "AuthenticationException: A call to SSPI failed, see inner exception". The inner exception is "Win32Exception: The Local Security Authority cannot be contacted". This is not specific to one Windows 10 machine. I thought that it might have something to do

My app quits serving static files after the Windows April Update

这一生的挚爱 提交于 2021-02-18 18:43:06
问题 I have an app where the Content folder is filled by another process that builds a frontend app, and the Visual Studio project itself doesn't know what's in the folder. I set up the web.config with a standard <staticContent> node and <modules runAllManagedModulesForAllRequests="true"> . I have my RouteConfig set up with routes.IgnoreRoute("content/*"); The app typically runs with IIS Express, but I have also run it with IIS proper. This has all worked fine to load js, css, and other static

My app quits serving static files after the Windows April Update

大兔子大兔子 提交于 2021-02-18 18:42:15
问题 I have an app where the Content folder is filled by another process that builds a frontend app, and the Visual Studio project itself doesn't know what's in the folder. I set up the web.config with a standard <staticContent> node and <modules runAllManagedModulesForAllRequests="true"> . I have my RouteConfig set up with routes.IgnoreRoute("content/*"); The app typically runs with IIS Express, but I have also run it with IIS proper. This has all worked fine to load js, css, and other static

Enhanced Strong Naming

随声附和 提交于 2021-02-18 17:59:42
问题 I am testing Enhanced Strong Naming (http://msdn.microsoft.com/en-us/library/hh415055.aspx) and having some problems getting it into a build process. According to the article you have to delay-sign assemblies first and then re-sign them to get proper Enhanced String Name. That does not work well with the build process. Usually we delay-sign assemblies while developing, and fully sign them on build servers. Does anyone have any experience with Enhanced Strong Naming? Also posted on http:/