Nurhak Kaya's Software Development Blog

It could be beneficial to run multiple threads to perform operations on different segments concurrently, so that certain tasks can be completed quicker (like some data updates using some services), and Data Parallelism   could help you, and in this scenario you can benefit from a powerful processor by writing a code as follows; ParallelOptions options = new ParallelOptions() { MaxDegreeOfParallelism = System.Environment.ProcessorCount }; Parallel.ForEach(mdList.AsEnumerable(), options, async row => {    result = await ProcessATask(param); }); For debugging purposes; you can replace the ParallelForEach with this following line to your checks for certain items; Parallel.ForEach(mdList.Select(“numbertocheck”).AsEnumerable(), options, async row => {    result = await ProcessATask(param); });

It is possible that after some big code changes(i.e. a big upgrade), you might have some issues with some old dlls, and in order to prevent some unexpected problems, you might want to remove everything under your Web App's wwwroot(or any other folder), and if this is the case, then you can Kudu for Azure Web Apps; Login to Azure Portal with your project's Azure credentials. Find your Azure Web App and copy its url and write the following command to remove all items from wwwroot. Get-ChildItem 'D:\home\site\wwwroot' | Remove-Item -Recurse -Force After doing this, you shouldn't see anything under wwwroot and you can then start your clean deployment(swap for my case).

Kudu is the engine behind git deployments in Azure Web Site and it can also run outside of Azure. Please click here for more details. Kudu can be used to find out an Azure App Service's OS version and all of other details like other environmental details etc. and here are the steps to check the OS system of you App Service; Login to Azure Portal with you credentials, and find your App Service. Find the publishUrl of your App Service, it should be something like this; your-app-name.scm.azurewebsites.net:443 Now simply go to this url; https://your-app-name.scm.azurewebsites.net In the Environment page, under System info, you will find the details for your system, including your Azure App Service's OS version. Hope it helps.

If you have got a Windows Web Server, it is possible that IIS is enabled to generate the IIS Log files and over the years this could cause some disk space problems. In order to clear up the disk space; one good option is cleaning up the old IIS log files automatically by using a Windows Scheduler Task and a Powershell script. For this solution; all credit goes to Bob McCoy , this has helped me and my Client, hope it will help you, too. Step 1: Copy/Create Script Copy the following script to a place where your privileged user can get to it. Since it's going to be run by the task scheduler, you don't want it somewhere where users can modify it to accomplish their nefarious purposes. # Script to be run weekly by task scheduler to cleanup IIS log files # greater than 30 days old. $start = (get-date).AddDays(-30) cd c:\inetpub\logs\logfiles\w3svc1 Get-ChildItem | where {$PSItem.LastWriteTime -lt $start} | Remove-Item If you are running PowerShell v2, replace $PSItem