It was first released publicly in June 2015. In order to cooperate with the actual application of Tinyfox, after the release of Tinyfox, it has successively launched and two key application frameworks, forming a relatively complete and independent OWIN protocol -based Web -oriented service system.
Because the original Tinyfox is essentially an Owin basic engine with the Microsoft Owin protocol. Although it has the solidity and strength of the basic level, the Web application layer and its OWIN kernel layer need to perform relatively low -order data conversion data conversion. And packaging, this process not only has a certain impact on performance, but also puts forward higher requirements on Tinyfox users. It requires developers to have a deeper understanding of the OWIN protocol and their pipeline models to develop a stronger application to develop more powerful applications This has a small contrast with the reality, which is neither conducive to users' use, nor is it conducive to the development of Tinyfox.
In order to overcome the deficiencies of traditional Tinyfox, Mr. Yu Shi Yun Yun (also author of Jexus) of Tinyfox's original author, combined with the characteristics of the current mainstream Web system, the latest development results of .NET and summarized the demand rules of Tinyfox in the past 10 years. It began to design a new design in early December of the year, and released the first new Tinyfox version on January 18, 2025: Tinyfox V6.0.118.
The new version of Tinyfox has the following characteristics:
1. Remove the OWIN protocol.
The new version of Tinyfox's network transfer layer and the application layer is closely connected, and no longer uses the OWIN protocol for conversion and packaging, which not only further improves performance, but also greatly simplifies the operation process and reduces the threshold for learning and use.
2. Integrated Webapi and WebSocket to add "dynamic HTML" function.
The new version of Tinyfox no longer scattered the application layer function into the sub -framework, but is a whole with the HTTP kernel of Tinyfox. It is worth mentioning that while the new version of Tinyfox "pure data services" such as Webapi and WebSocket also added expansion support for HTML files, that is, "dynamic HTML". "Dynamic HTML" is "dynamic" by adding "labels" to the HTML file (labeling "(dynamic" (dynamic "in HTML (in HTML to interact with the variable value, value, and function directly with the host program). The addition of dynamic HTML characteristics makes Tinyfox has the ability to directly develop Web website programs with the UI interface without the support of other web frameworks or engines such as Core, Java Spring or PHP.
3. Ultra -light, strong independence, universality, and natural support for .NET AOT.
All functions of the new version of Tinyfox are concentrated in a .NET DLL with a size of only about 200k bytes. It is referenced by Nuget and does not rely on any third -party component.
Tinyfox comes with the HTTP service engine. Its communication components do not use anything about .NET SOCKET. It is completely based on the underlying function of the operating system and conducts native development of the characteristics of the HTTP service. Because of this, Tinyfox does not require the support of external Web servers such as IIIS, Jexus, Nginx, etc., and can independently provide high -performance network services based on the HTTP protocol.
The new version of Tinyfox both supports .NET Frameowrk 4.5.1 or above the traditional .NET framework, as well as .NET 6 or above .NET "New World", both supporting Windows and LINUX (including "domestic operating system"). It supports both X86/X86_64, ARM/AARCH64, and even a domestic Longxin CPU. It can be embedded in any .NET program, which is widely adaptable to the target environment. In order to support the .NET Nativeaot, the new version of Tinyfox itself has removed the relevant code that affects Nativeaot operations such as dynamic loading and dynamic reflection, which affects users based on Tinyfox with strong independence and source code security business program. Key support.
4. Easy -to -use, openness and complete development documents.
Simple and easy to use is one of the most obvious features of the new version of Tinyfox. It completely removes the Owin protocol used by the old version of Tinyfox. Users do not need to deal with any original protocol, only one sentence such as "["/"= _ => The simple code such as New TextResult ("Hello") can achieve data output. Friends who are familiar with C# need to take a serious look at the Tinyfox user manual. It only takes a few minutes to get started.
In order not to repeat the other framework, the larger the more, the more complicated, and the more inefficient the same mistake, the Tinyfox's own development and design strictly adhere to the word "boundary", that is, the use of all energy on the network layer, Webapi, WebSocket and and In terms of the optimization and improvement of several key functional modules such as dynamic HTML and the standardization of external interface standardization, we strive to seek the efficient and solidity of the core, and never easily add functions to break through the design "boundary". At the same time, in order to meet the specific needs of different users, the new version of Tinyfox is open in the base classes related to the user application layer whether it is Webapi or WebsokCet. Disposter and arbitrarily expand.
The most lacking of the old version of Tinyfox is the development document. When using the old Tinyfox, many old users either rely on the online scattered technology blog text to explore themselves, or contact the author to develop under the author's guidance. In order to overcome this deficiencies, the new version of Tinyfox has its own "home": official website. Now, Tinyfox users can obtain a complete TinyFox user manual on the Tinyfox official website. Without the author's separate guidance, you can master the relatively complete TinyFox usage and development skills without the need to guide themselves.
Whether the old version of Tinyfox continues to maintain, how to distinguish between the old and new Tinyfox?
The new version of Tinyfox and the old version of Tinyfox are two completely different frameworks. However, in order to ensure the sustainability of applications developed based on the old version of Tinyfox, we will continue to maintain the old version of Tinyfox (the newly discovered BUG, the continuous optimization of the key code of the kernel) Essence The dividing line of Tinyfox's TinyFox is their version number. The new version of the Tinyfox version number starts from 6.0. As long as Tinyfox, which is higher than 6.0, is the new version of Tinyfox. Tinyfox is Tinyfox V4.2.9), so the procedure developed based on the old version of Tinyfox does not need to worry about the sustainability of the old version of the old version due to the birth of the new version of Tinyfox.