Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@deltragon
Copy link

@deltragon deltragon commented Oct 11, 2021

Hello!
I am administrating a legacy ASP.NET project that is built on telerik web ui which makes heavy use of System.Web.Extensions.
These patches make it possible to run the project on mono/linux, which is what I would prefer to do with this project in the long term.
(I have not tested the project extensively yet, but it appears to load all pages/data so far. The only issue seems to be that the encoding is not properly sent in the Content-Type header, so the browser interprets UTF-8 as some legacy encoding).

I would like to contribute these patches to upstream mono.
They mostly consist of switching to/adding files from the referencesource, or (specifically for System.Web.UI.ScriptManager) copy-pasting needed methods from the referencesource.

I have some questions however:

  • Is it even still desirable to use the referencesource? According to this, which I had not found when I started this, corefx should be used instead - however, it does not seem complete enough at the moment (especially the mono/corefx afaict), and the referencesource gets the job done.
  • There are two commits modifying corefx, which reintroduce System.Data.LinqDataView and extend System.ComponentModel.DateTimeConverter, both based on the referencesource. Is it correct to just modify the mono/corefx repo?
  • Should I keep this in one big PR, or split it out into smaller ones? Eg. the System.Data.LinqDataView changes might make sense as a separate PR.

Other notes:

  • There is one commit switching from corefx back to the referencesource (System.ComponentModel.DateTimeConverter), as the referencesource version has methods corefx is missing. I will add the missing functionality to corefx instead. Functionality has been added to corefx.
  • This does not pass the test suite for System.Web. I am currently working on that.
  • This does not add any tests for the new functionality. I will add these as well.

@dnfadmin
Copy link

dnfadmin commented Oct 11, 2021

CLA assistant check
All CLA requirements met.

@deltragon deltragon force-pushed the scriptmanager-extensions branch 2 times, most recently from 267945a to 0ad7b0c Compare October 12, 2021 17:17
@deltragon deltragon marked this pull request as ready for review October 12, 2021 17:20
@deltragon deltragon changed the title [Draft] System.Web.Extensions additions [WIP] System.Web.Extensions additions Oct 12, 2021
@steveisok
Copy link
Contributor

@deltragon Thanks for opening this up! If you want, take a look at #12619 . I believe it'll have the tests that go along w/ your PR.

@deltragon deltragon force-pushed the scriptmanager-extensions branch from 2055f17 to 1f4f897 Compare October 21, 2021 15:25
@deltragon
Copy link
Author

@steveisok Thank you for the pointer! I also tried the approach of porting the whole thing to referencesource, but quickly gave up on it. Good to see that someone already put in that work :)
I did unfortunately not find any added tests, only some changes to existing tests. Were those removed at some point, or were the tests added separately at a later point?

@deltragon deltragon force-pushed the scriptmanager-extensions branch from 1f4f897 to b0a70dc Compare November 14, 2021 21:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants