Skip to content
This repository has been archived by the owner on Nov 1, 2020. It is now read-only.

Speculative changes to high-level plan #7997

Merged
merged 2 commits into from
Feb 21, 2020
Merged

Speculative changes to high-level plan #7997

merged 2 commits into from
Feb 21, 2020

Conversation

kant2002
Copy link
Contributor

This is to gather feedback from core team,
and maybe improve documentation slightly

This is to gather feedback from core team,
and maybe improve documentation slightly
@@ -41,13 +41,13 @@

## Interop
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
## Interop
## COM Interop

@jkotas
Copy link
Member

jkotas commented Feb 21, 2020

80% of the items in this list are done, and the rest is unclear or abandoned. Maybe it would be best to delete this file, and just use github issues for tracking?

@kant2002
Copy link
Contributor Author

if it 80% or something just not applicable it would be more damaging to the reader to actually read. it give impression of abandon-ware. From my point of view, tech is more or less mature, but need investing and polishing. At least I hope so. Better that somebody come up with another document which explain more modern goals.

I personally see (can do probably) something like evaluation of well-known libraries, and how well they are behave under CoreRT. Example of what I thought can be helpful to read

  • ASP.NET Core
  • EF Core
  • System.Net.Http
  • Windows Forms
  • WPF
  • COM Interop
  • PInvoke
  • Blazor
  • IdentityServer

All that is well-known MS technologies. For sure list can contains not only MS tech. This is document from consumer perspective, but for sure I personally would like to read overview of what's left from core dev perspective.

@jkotas
Copy link
Member

jkotas commented Feb 21, 2020

Agree. We are not planning to do that in isolation for just CoreRT.

Number of the technologies on your list do not work well for single file or IL linker, without any full AOT or CoreRT in the picture. Both single file and IL linker issues are being worked on for .NET 5.

@jkotas jkotas merged commit d97bf3b into dotnet:master Feb 21, 2020
@kant2002 kant2002 deleted the kant/plan-questions branch February 21, 2020 19:03
@kant2002
Copy link
Contributor Author

I'm not shy try some tech on .NET 5 if that improve CoreRT story. If you think it can somehow help me create smaller files. I personally do not care about SingleFile as long as it is 200Mb. That's my main reason for looking at CoreRT, plus Blazor

Regarding some tech which may not working under CoreRT - I believe it is better know what's not (hopefully) yet working. If large parts of BCL is mostly working, it will be very interesting to know (read in docs). File system + Http can go you relatively far. If SqlClient/NgSql is working it moves you even further etc.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants