This repository has been archived by the owner on Aug 9, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 18
WebForms Examples Explorer issues in Ext.NET 4.2.1 #15
Comments
The stock ticker example (item 408) was broken because a setting in the project file was preventing owin-related class Startup.cs from being compiled by any VS not matching versions 11, 12, or 14. |
fabriciomurta
added a commit
that referenced
this issue
May 21, 2017
Removed old rules that allowed it to work on very old versions of Visual Studio and that deterministicly broken the project to any new versions of Visual Studio. Notably Owin startup class that was limited only to VS versions explicitly specified. This addresses issue #15 item 408 (Stock ticker example not working).
This was referenced May 21, 2017
fabriciomurta
added a commit
that referenced
this issue
May 21, 2017
Now the example can safely be run with ScriptMode=Debug and SourceFormatting=True. Related github issue: #15 item 97.
fabriciomurta
added a commit
that referenced
this issue
May 21, 2017
KeyMap is broken as per extnet/Ext.NET#1466. And fixing this example requires fixing the KeyMap functionality. Related github issue: #15 item 354.
fabriciomurta
added a commit
that referenced
this issue
May 21, 2017
The example is using an alternative way (via listeners) to attain the same behavior, so it was not completely hidden from EE. When extnet/Ext.NET#1466 is fixed, the example can again use the KeyMap component/concept. This addresses #15 item 353.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Summary
Here we will enumerate all issues on Ext.NET 4.2.1 regarding the WebForms version of the Examples Explorer. MVC Examples explorer did not raise any error on this release.
This version includes ExtJS 6.2.1. The previous Examples Explorer Webforms release issue was #9 .
OPEN
Items here are identified as defects but not yet analysed nor fixed.
PENDING
Items here are pending further analysis, another fix or something else that prevents them to be actually fixed.
WON'T FIX or NOT BUG
FIXED
As items are fixed, they are moved to this section.
Items with the FIXED* tag (with an asterisk) means they were fixed merely by the ExtJS upgrade or already fixed as the examples explorer was tested.
The text was updated successfully, but these errors were encountered: