ASP. Aries 2.0 released (the original source SVN has been turned off and the stream code has been migrated to GitHub)

Major updates:

1: Added support for sub-directory deployment.

2: Increase TAURUS.MVC support.

3: Optimization and bug fix.

1: Added support for sub-directory deployment:

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

However, the latest user feedback, need to be deployed in sub-directory, so on the homeopathic directory deployment of this feature to increase.

2: Add TAURUS.MVC Support:

Aries 2.0 of the directory structure is this: the original aries.logic under the handler change to Aries.controllers, other changes are not big.

In my entire design process is this:

1: Transform Aries into MVC:

In the beginning only: Ajaxbase and Logicbase and IBase, changed to become:

Ajaxcontroller,ajaxlogicbase,iajaxbase

Viewcontroller,viewlogicbase,iviewbase.

After the transformation, I constantly think about the user experience and the user's learning costs:

Thinking long, feeling easy to confuse users, a little damage to the purity of the Aries.

So, think of the MVC alone.

2:TAURUS.MVC Released:

Because the MVC function has been completed, just rewrite the renaming, independent release, so after a few days of effort, continuous simplification, optimize the process after:

Finally released and open source taurus.mvc:http://www.cnblogs.com/cyq1162/p/5739048.html

The core of the entire framework, ostensibly taurus.core, is actually cyq.data (at that time the emphasis on transforming the class under the CYQ.Data.Xml namespace)

The whole framework of innovation: Taurus.core simply simplifies routing and looking for controllers (reducing the cost of learning), innovation or the template engine, including template page references also create new thinking.

Therefore, there will be individuals who do not understand the truth, easy to narcissism.

After publishing Taurus.mvc, looking at Aries, preserving MVC? Or?

Remember to maintain at the same time two copies of almost the same but the name of different code, the heart is tired, must move, but how to move?

3:aries Remove the TAURUS.MVC part and change the compatibility mode:

and want to preserve MVC, but also to maintain the purity of Aries, thinking for a long time, and finally found a way to both worlds:

In Urlrewrite and invokelogic pre-process TAURUS.MVC Routing and find Controller.

Then just refer to Taurus.Core.dll and you can.

3: Optimization and Bug:1:cyq.data Upgrade:

The latest cyq.data version of the upgrade frequency is a bit high, mainly: automatic cache +xhtmlaction changes a bit large, has now stabilized.

But as long as the framework is still maintaining the upgrade update, stability is relative.

Related script upgrade for 2:aries.js:

Do some small optimizations, and add the search function to the searching box.

SVN Source Address Migration:

1: The original Aries in Code.taobao.org's SVN has been closed and is now moving to GitHub.

The address on the 2:github is: https://github.com/cyq1162/Aries.git

3: Here's the place to spit up a little bit of GitHub:

1: Speed (a few k upload rate, pit me too much time)

2: Can not pass empty directory (accidentally encountered empty directory, you have to re-upload, didn't notice, was pit a lot of back)

3: One-time upload can not be too much (the network is easy to break or unresponsive, and have to start again)

So, can only be divided into batches, a few small directories to upload.

In fact, the earliest is released on GitHub, because the speed of the upload too pit, change to code.taobao.org, did not expect to toss back (for you, endure).

A few simple related configurations:

1: Deploy subdirectories:

Change the configuration of the UI.

2: Cancel or increase the permission directory to log in:

Change the checktokenpath corresponding configuration, multiple directories with "," number separated.

PS: The code uses the path detection is: contains contains, so regardless of the hierarchy, this should be noted.

3: Auto-Cached settings:

If your system, in addition to the cyq.data, there are other ways to manipulate the database, you should turn off automatic Caching: Isaotucache is configured to False, the default is true.

Aries 2.0 steps to use TAURUS.MVC: Add a Taurus.Core.dll reference to the 1:aries.controllers project:

How to quote:

A: Download Taurus.mvc source code, find Taurus.Core.dll, add Reference.

B:nuget search Taurus.mvc, add Reference.

2: Suggested Views folder under the Web.ui project

If you want to run the demo, you can copy the views directory under TAURUS.MVC.

3: Add controller to the Aires.controllers project

If you want to run the demo, you can copy the directory under the Controllers project under TAURUS.MVC.

PS Note: When using TAURUS.MVC, note the namespace:

The inherited base class is Taurus.Core.Controller.

In short, it is how ordinary projects use Taurus.mvc,aries.

End:

As a lot of personal open source works, to maintain the upgrade, but also to conceive new features, it takes a lot of energy.

So if you encounter problems, please use the source code debugging, positioning to the problem, and then feedback to the group, so that can save me a little time.

Finally, thank you guys for your long-standing support!

ASP. Aries 2.0 released (the original source SVN has been turned off and the stream code has been migrated to GitHub)