All 3 would be valuable although I'd rather #2 use CKEditor so it is consistent with the admin site rather than expect content editors to be comfortable with two different WYSIWYG editors.
This also means any custom extensions to the WYSIWYG only need to be built once.
The new documentation pages about Writing automated tests is public: https://docs.kentico.com/display/K9/Writing+automated+tests
Maybe you will find there something you didn’t know. Right now we are working on the v10 version with some of the new options and enhancements.
Any feedback will be appreciated.
+1 on Gabor's comments.
Has there been any movement on this since originally posted?
Agree with Sean on this one. The use of static Context classes causes a lot of tight code-coupling which causes issues with unit tests. Ideally the Contexts would be injected using interfaces which we could then mock in our tests.
On the point of testing, there is still no ability to call a "SetInfo" method on an InfoProvider when writing a unit test. This also causes issues and requires a layer of abstraction on our side to avoid.
Please share your thoughts
In terms of OWIN:
We have needed to hook into the request pipeline in the past to make checks to redirect/rewrite requests based on business logic. Having the ability to do this as early as possible will remove some overhead on the initial request.
Using the OWIN pipeline also allows us to separate the webforms environment and multiple WebAPI environments with their own specific configurations. We have had scenarios before where changes to the WebAPI configuration have impacted the Kentico dashboard as this also uses WebAPI.
In terms of Identity:
The main scenario we have encountered is using WebAPI in conjunction with Forms Authentication.
There is a disconnect when doing this. However, if we could use the Identity framework then we could share the same authentication token between the two systems whilst maintaining a stateless API.
The Identity framework also supports using OAuth with only simple configuration which will make the authentication more extensible with 3rd party services or SSO.
Would Kentico be looking to implement this in the WebForms version also?
Waiting for more votes