ASP. NET Aries 2.0 (the original source code SVN has been closed and the source code has been migrated to GitHub), svngithub

ASP. NET Aries 2.0 (the original source code SVN has been closed and the source code has been migrated to GitHub), svngithub
Major updates:

1: added support for subdirectory deployment.

2: added support for Taurus. MVC.

3: optimization and Bug fixing.

1: added support for subdirectory deployment:

In fact, when rewriting the Aries framework, I removed the directory deployment function, mainly to speed up Aries development.

However, the latest user feedback needs to be deployed in sub-directories, so we can add the Sub-directory deployment function.

 

2: added support for Taurus. MVC:

The directory structure of Aries 2.0 is as follows: the Handler under the original Aries. Logic is changed to Aries. Controllers, and the other changes are not great.

The entire design process is as follows:

1: Transform Aries into MVC:

At the beginning, only AjaxBase, LogicBase, and IBase are available:

AjaxController, AjaxLogicBase, IAjaxBase

ViewController, ViewLogicBase, and IViewBase.

After the transformation, I repeatedly thought about the user experience and user learning costs:

Thinking for a long time makes it easy to confuse users and undermines the purity of Aries.

Therefore, let's think about how to separate MVC.

2: Taurus. MVC released:

Since the MVC function has been completed, it is only renamed and released independently, so after a few days of effort, it is constantly simplified and the process is optimized:

Taurus. MVC: http://www.cnblogs.com/cyq1162/p/5739048.html is finally released and open-source

The Core of the entire framework is Taurus. Core, which is actually CYQ. Data (classes in the CYQ. Data. Xml namespace were the most time-consuming)

Throughout the framework Innovation: Taurus. Core only simplifies routing and search for controllers (reducing learning costs). Innovation is still on the template engine, and the reference of template pages also creates new ideas.

Therefore, some people who do not know the truth may be self-satisfied.

After Taurus. MVC is released, watch Aries and retain MVC? Or?

When we remember that we had to maintain two identical copies of code with different names at the same time, we were so tired and had to change. But how did we change it?

3: Aries removed the Taurus. MVC part and transformed it into a compatible mode:

I want to retain MVC and keep Aries pure. After thinking for a long time, I finally found a perfect method:

In UrlRewrite and InvokeLogic, pre-process the routing of Taurus. MVC and find the Controller.

Then, you only need to reference Taurus. Core. dll.

3: optimization and Bug: 1: CYQ. Data upgrade:

The upgrade frequency of the latest CYQ. Data version is a bit high, mainly because the automatic cache + XHtmlAction changes a bit large and has stabilized.

However, as long as the framework is still being maintained and updated, stability is relative.

2: Upgrade related scripts of Aries. js:

We made some minor optimizations and added the search box search function.

SVN Source Code address migration:

1: The SVN of Aries at code.taobao.org has been closed and has been moved to GitHub.

2: GitHub address: https://github.com/cyq1162/Aries.git

3: Let's talk about github:

1: network speed (several K upload speed, so it takes me too much time)

2)

3: one-time upload cannot be too many (the network is easy to break or don't respond, and you have to start over again)

Therefore, only a few small directories can be uploaded in batches.

In fact, it was first released on Github. Due to the poor upload speed, I switched to code.taobao.org and did not expect to go back (for your sake, I have to endure ).

Several simple configurations:

1: Deployment subdirectory:

Modify the configuration of the UI.

2: cancel or add the permission directory to be logged on:

Modify the configuration corresponding to the CheckTokenPath. Separate multiple directories with.

PS: path detection is used in the Code: Contains, so no matter the level, this should be noted.

3: Automatic cache settings:

If your system uses other methods to operate the database besides CYQ. Data, you should disable automatic cache: Set IsAotuCache to false, and the default value is true.

Steps for using Taurus. MVC in Aries 2.0: 1: Add reference of Taurus. Core. dll to the Aries. Controllers project:

Reference Method:

A: Download the source code of Taurus. MVC, find Taurus. Core. dll, and add reference.

B: Search for Taurus. MVC on Nuget and add references.

2: The Views folder is recommended under the Web. UI project.

If you want to run the Demo, you can Copy the Views directory under Taurus. MVC.

3: add the Controller in the Controllers. Controllers Project

If you want to run the Demo, you can Copy the directory under the Controllers project under Taurus. MVC.

Note: When using Taurus. MVC, note the namespace:

The inherited base class is Taurus. Core. Controller.

In short, it is how to use Taurus. MVC in common projects and how to use Aries.

End:

As many open-source works are made by individuals, it takes a lot of effort to maintain and upgrade, and to design new functions.

Therefore, if you encounter any problem, first debug it with the source code, locate the problem, and then report it to the group, saving me some time.

Finally, thank you for your long-term support!