WxUtile 1.0.0
dotnet add package WxUtile --version 1.0.0
NuGet\Install-Package WxUtile -Version 1.0.0
<PackageReference Include="WxUtile" Version="1.0.0" />
paket add WxUtile --version 1.0.0
#r "nuget: WxUtile, 1.0.0"
// Install WxUtile as a Cake Addin #addin nuget:?package=WxUtile&version=1.0.0 // Install WxUtile as a Cake Tool #tool nuget:?package=WxUtile&version=1.0.0
Package Description
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net5.0 is compatible. net5.0-windows was computed. net6.0 was computed. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 was computed. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. |
.NET Core | netcoreapp3.1 is compatible. |
.NET Framework | net461 is compatible. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
-
.NETCoreApp 3.1
- BouncyCastle.NetCore (>= 1.8.10)
- Microsoft.AspNetCore (>= 2.2.0)
- Microsoft.AspNetCore.Http (>= 2.2.2)
- Microsoft.AspNetCore.Mvc (>= 2.2.0)
- Newtonsoft.Json (>= 13.0.1)
-
.NETFramework 4.6.1
- BouncyCastle.NetCore (>= 1.8.10)
- Microsoft.AspNetCore (>= 2.2.0)
- Microsoft.AspNetCore.Http (>= 2.2.2)
- Microsoft.AspNetCore.Mvc (>= 2.2.0)
- Newtonsoft.Json (>= 13.0.1)
-
net5.0
- BouncyCastle.NetCore (>= 1.8.10)
- Microsoft.AspNetCore (>= 2.2.0)
- Microsoft.AspNetCore.Http (>= 2.2.2)
- Microsoft.AspNetCore.Mvc (>= 2.2.0)
- Newtonsoft.Json (>= 13.0.1)
NuGet packages (1)
Showing the top 1 NuGet packages that depend on WxUtile:
Package | Downloads |
---|---|
WxMicro
目前大多的业务平台、办公OA、以及相关的数据管理后台,Api接口等的开发在环境搭载方面均比较复杂。每套程序都需要自行去构建复杂的权限、开发繁琐的权限分配计算。设想如果有一个框架可以实现简单的数据配置就能 实现复杂高效的权限功能,只需要简短的代码就能构建出复杂的鉴权,那么在构建开发时是否可以减轻程序员构建复杂权限的时间?可直接进行业务接口的开发,无需去考虑权限以及分配问题。开发好直接通过简单的权限配置即可得到想要的结果。 微服务架构的维护是很让程序员头疼的事情,可不可以简化微服务的架构?通过鉴权的方式让程序自动去完成日志、记录、接口、发现、网关等一系列的繁琐品配置。让程序员快速构建对应的业务程序即可发布出相应的微服务,其他的挂载的微服务程序可检测到新的服务程序,并提供相应的程序使用场景。可通过实现新开发出的微服务程序接口,使用或调用对应微服务的相关接口进行业务处理来实现微服务开发的繁琐性质。 通过以往经验了解以往的MVC(Model View Controller)框架是将M和V实现代码分离,从而使同一个程序可以使用不同的表现形,而这种设计模式是比较单一而且复杂的。程序员在开发不同的功能时通过书写多个Controller以及多个View实现不同的业务和功能,设想一下如果将MVC设计理念+上微服务理念,实现出来的新架构会是什么样子的?单独的模块是MVC处理模式。可单独布置或者单独的发表,而MVC模式中Controller其实是可以跨服务器限制实现远程访问的。那么我们可以不可以通过一些特殊的程序完成MVC的服务继承?实现接口和业务的模块化,实现权限统一的校验标准,让我们构建项目时,不需要过多的区书写相同的功能或者界面,然后构建对应的功能模块仓库或者商城实现模块的复用。完成微服务能做到而MVC做不到的一些功能呢?如果可以那将如何去实现,由此构建了一下的响应项目,并完成由MVC框架保留以往的设计模式以及理念,加上一些新的微服务理念,完成MVC设计的模块编程。 根据上述需求以及构想进行相应资料的查阅以及通过以往开发经验的整理,建设该MVC微服务项目。项目命名为“WxMicro” 名字大概的意思就是“微小工程”。 |
GitHub repositories
This package is not used by any popular GitHub repositories.
Version | Downloads | Last updated |
---|---|---|
1.0.0 | 286 | 7/15/2022 |