-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.NET Projections should not have WinRT types in them #36
Comments
Many thumbs up for System.IO ! |
@jtorjo note that this ask was more around creating a projection layer that properly "hides" the Windows Storage APIs behind a subset of the This would have to be elegantly done for the file system APIs, since UWP doesn't allow arbitrary file system operations. But I think for things like Streams and collections, this should be relatively straightforward |
@stevenbrix That could probably work. As longs as it's fast, I'll put up with it. Right now, StorageFolder query speeds are beyond horrible. |
@stevenbrix - now that we're getting into the type mapping work, can you provide an explicit list of WinRT -> .NET mappings (wrappings) you'd like to see implemented? |
dupe of #77 |
the winrt to .net projections were never implemented fully properly and is really confusing. sometimes you use the regular .NET types, and in other places you use the WinRT version. I think that .net developers should use the APIs they are comfortable and used to using. On top of that, I've heard from customers that it makes code re-use and sharing more difficult.
Any API that uses xLang to project into .NET should use the .NET APIs that already exist, especially those in the
System.ComponentModel
,System.Collections
, andSystem.IO
namespaces.The text was updated successfully, but these errors were encountered: