shadowsocks-windows VS ASP.NET Core

So I have a SS proxy running (with this client) and the majority of applications use it when it's on global mode but for example the command line (cmd) doesn't seem to pick it up. (e.g. I can't ping a blocked website on cmd whereas I can do this with a VPN)

commented on 18 Aug 2015 at Github

Just tried it on https://github.com/shadowsocks/shadowsocks-windows

Microsoft PowerToys is a set of utilities for power users to tune and streamline their Windows 10 experience for greater productivity. For more info on PowerToys overviews and guides, or any other tools and resources for Windows development environments, head over to docs.microsoft.com!

https://github.com/shadowsocks/shadowsocks-windows/issues/293#issuecomment-132253168

Shadowsocks is a free and open-source encryption protocol project, widely used to circumvent Internet censorship. Why is it so popular, because it is used by a large population!

🌟.NET 9 Preview 2 ➡️.NET 9 Preview 2 Discussion ➡️ASP.NET Core updates in .NET 9 Preview 2 ➡️ASP.NET Core updates in .NET 9 Preview 2 Release Notes ➡️EF Core updates in .NET 9 Preview 2 ➡️.NET Aspire preview 4 - .NET Aspire

https://github.com/dotnet/aspnetcore/issues/50643

Even if you look at Microsoft’s by far most popular GitHub project, they’re still only half as big as SupaBase. If you believe “the SupaBase story”, SupaBase grew and became twice as large as Microsoft in 3 years. Below is their likes over time if you’re curious, together with a couple of additional “too good to be true” Silicon Valley projects.

https://github.com/dotnet/aspnetcore/issues/10117

To achieve these objectives, we will take inspiration from ASP.NET Core Identity's PasswordHasher class. It incorporates a concept of hash versioning, allowing only the number of iterations to be modified.

yes I watched several courses, may be aim not getting clearly. but i worked with asp.net which uses http call and firebase cloud function also which uses socket connection, for socket connection its makes sense to use observable bcoz there streams of data we can observe once the connection establish ,but for http it need to be call every time.

As I'm not utilizing ASP.NET, despite its resource-intensive nature and occasional unpredictability, I prefer the cost-free option. I'm hesitant to invest in EPPlus or engage in trials, and moreover, I am more proficient with Interop. Given the limited volume of records in my department, there's a preference for utilizing tools covered by our existing license. This avoids the need for navigating through layers of approval within the chain of command and ensures compliance with our contractual agreements and Microsoft's patch management, ultimately aligning with a cost-saving mindset.

Most of basic .NET itself is almost identical to .NET Framework, with few new methods here and there. You can just switch framework and start coding. New language features are not at all essential and required to use, so you can just read C# release notes on MSDN, and start using them at your own pace. ASP.NET changed a lot, but for competent Framework developer, just reading through MSDN docs on new ASP.NET + doing some WebApi project is enough to get the gist of it. Stop hesitating and just go for it.