.NET (Core and Framework)

Reported issue. They suggested running from console with DOTNET_TC_QuickJitForLoops=0 env var defined. That speeds it up slightly, although 6.0 is still a bit faster. I read somewhere that in 6.0, setting that to 0 speeds things up but that in .NET 7 there's no difference. Though to me it looks like it might be the other way round! So for 6.0 I get 0.53/0.54s (two successive runs). For 7.0 it is 0.57/0.58s. Still, nothing worth bothering about. Kevin

Thank you for the explanation. Actually, I guessed but wasn't sure. Many thanks @RichardDeeming @Richard-MacCutchan

Yes thanks alot I got the help from . Full Stack User

You need to change the requestTimeout property on the aspNetCore element instead: <?xml version="1.0" encoding="utf-8"?> <configuration> <system.webServer> <aspNetCore requestTimeout="00:02:00" .../> </system.webServer> </configuration> "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

OpenSilver[^]: OpenSilver is a modern, plugin-free, open-source reimplementation of Silverlight. It uses WebAssembly to bring back the power of C#, XAML, and .NET to client-side Web development. Having never jumped on the Silverlight bandwagon, I haven't tried this, so I can't tell you whether it will work with your current code. But it's probably the simplest place to start. :) "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

See [OS/360 and successors \- Wikipedia](https://en.wikipedia.org/wiki/OS/360\_and\_successors#MVT). There were processors and operating systems half a century ago that supported multiple tasks (threads). The idea was that many things, especially I/O, took time and if only one task executes then the processor is idle for a long period of time. Back then disk drives and tape drives were very slow.

Hi there, Is there any solutions, as I have come across the same question. Wish for you reply, thanks.

Well, go ahead; you have our permission to do that. Feel free to come back if you have an actual question. "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

dataminers wrote: the two code blocks below are the same No they're not. The first one starts a new task to execute CalculateSomething(5), and then suspends the current thread until that task completes. It then starts another task to execute CalculateSomething(8). The second one starts two tasks to execute CalculateSomething(5) and CalculateSomething(8), and then freezes the current thread until both have completed. If you time both approaches, the AsParallel code will be roughly twice as fast as the two await Task.Run(...) calls. The closest equivalent using Task.Run would be: // Start both tasks in parallel: Task t1 = Task.Run(() => CalculateSomething(5)); Task t2 = Task.Run(() => CalculateSomething(8)); // Wait for both tasks to complete: await Task.WhenAll(t1, t2); // Or: await t1; await t2; "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

Good call Richard it does actually work but I don't like red squigglies - I've noticed the same with the using statements, same thing intellisense works in all views except _layout where I'm prompted to add the full namespace.class Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP

i am looking for c# related call.

Thanks for guide line.

I belive internet is the best source.

Thanks Richard I updated the nuget packages and the problem disappeared - NuGet does bite me every now and then. Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP

That's actually a very good point now that you mentioned it. I didn't consider that and assumed that an ASP.Net app would be large enough to see some optimizations but I guess the libraries used are already optimized and my code doesn't have much stuff to optimize.

I'm not sure whether this question is still relevant but it misses the most crucial piece: how does your project reference your library. Anyways, the most convenient way of attaching external dependencies is Nuget package manager. You can learn more in official docs What is NuGet and what does it do? | Microsoft Docs[^]

I'd start by looking at what your SQL is trying to do and simplify it. From what I can see, your WHERE clause can be reduced to vYear = 2022 AND EmpCode = 5229 AND NOT VacType IN (10, 15, 16, 17, 18, 19, 20, 21, 23, 24) AND Result <> 1 AND ('12/07/2022' BETWEEN vStart AND vEnd OR CONVERT(DATETIME, '2022-07-13 00:00:00', 102) BETWEEN vStart AND vEnd ) I do not understand what the date ranges are for and why there are two different ways of representing dates unless your data has two sets of texts neither as real dates, in which case the comparisons are meaningless.