Dealing with Application Base URLs and Razor link generation while hosting ASP.NET web apps behind Reverse Proxies
I'm quietly moving my Websitefrom a physical machine to a number of Cloud Services hosted in Azure. This is an attempt to not just modernize the system - no reason to change things just to change them - but to take advantage of a number of benefits that a straight web host sometimes doesn't have. I ...
Razor Page already includes a wide range of constraints that can be used to help disambiguate routes. It is also possible for you to create your own custom constraint and then register that with the routing system.
This is a part of a series of blog posts on data access with Dapper. To see the full list of posts, visit the Dapper Series Index Page. After my recent misadventures attempting to use Noda Time with Entity Framework Core, I decided to see what it would take to use Dapper in a the same scenario.
Do you need to build a REST API with ASP.NET Web API? If you’re creating a new API, you should probably create it with .NET Core. But it’s not always possible to use the latest and greatest technologies. If you’re working in an existing ASP.NET 4.x app, or the organization you work for hasn’t approved the use of .NET Core yet, you may need to build an API in .NET Framework 4.x. That is what you will learn here. You’ll also learn how to access your API from another application (for machine-to-machine communication) and prevent unauthorized access to your API. As you go, I’ll show you how to implement standard design patterns so it will be easy for other developers to understand and work with your API.
This article describes how to containerize an ASP.NET WebApi solution with Visual Studio, how to pass data via environment variables and also how to run the images in docker without Visual Studio. The tricky part when running a web solution with a web API in docker containers is to map the URLs and ports so that the code running inside the docker container can be accessed from outside. This is a question of docker configuration and minor code changes.
I'll make no secret of it: I LOVE asynchronous programming in ASP.NET! I love it so much that I submitted a talk for CodeMash 2019 called "Hold Up, Wait a Minute, Let Me Put Some Async In It," which I actually got to present despite that ridiculous title. This post is a direct result of that talk, in which I took an existing synchronous ASP.NET web application and slowly refactored it to use asynchronous programming. I figure that more than just CodeMash's attendees might find this useful.
本框架旨在为.NET开发人员提供一个Web后台快速开发框架，采用本框架，能够极大的提高项目开发效率。 整个框架包括三个版本： .NET新版，采用.NET452,GitHub地址为：https://github.com/Coldairarrow/Coldairarrow.Fx.Net.Easyui.GitHub .NET40版，采用.NET40,GitHub地址为：https://github.com/Coldairarrow/Coldairarrow.Fx.Net40.Easyui.GitHub .NET Core版，采用.NET Core2.1,正在移植中，敬请期待。。。 以上三个版本中，.NET新版，主要支持最新的技术方案，作为主要生产版本；.NET40版是为了兼容Windows 2003服务器而降级的版本，功能正常。.NET Core 版本是未来的发展方向，能够跨平台，并且涉及Linux、Docker、Nginx、微服务等概念，我会尽快完成移植。
一. 说在前面的话本节主要在前面章节的基础上补充了几个简单的知识点，比如：第三方调用通过 GlobalHost.ConnectionManager.GetHubContext();来获取Hub对象，那么能不能封装一下不必每次都这么获取呢？再比如SignalR传输是否有大小限制，一下传输10w个字能否传输成功？最后着重整理一下跨域的各种使用情况，结合C/S程序充当客户端和...