Proposal: It is hoped that the ```CastExtensions.As<T>()``` extension method can be consistent with the ```.NET as``` keyword behavior

[Gaoyifei1011]

Summary

It is hoped that the CastExtensions.As<T>() extension method can be consistent with the .NET as keyword behavior

--------------------------------------------

希望能把 CastExtensions.As<T>() 扩展方法与 .NET as 关键字行为保持一致

Rationale

As shown in the figure, if the as keyword in .NET encounters a type that cannot be converted, it returns null, while the CastExtension.As<T> extension method in WinRT throws an exception. Can the behavior of the as keyword in .NET be consistent in the future? Or provide an extension method similar to TryAs, with a Boolean return value, and return the relevant object through the out parameter?

--------------------------------------------

如图所示，.NET 的 as 关键字，如果遇到转换不过去的类型，返回 null，而 WinRT 的 CastExtension.As<T> 扩展方法抛出异常，未来能与 .NET as 关键字行为保持一致吗？或者提供一个类似 TryAs 的扩展方法，返回值为布尔值，通过 out 参数返回相关对象？

---

Important Notes

None

Open Questions

None

[manodasanW]

One of the goals with CsWinRT 3.0 by using the new .NET type map functionality is to avoid the scenarios that need the CastExtensions.As<T> and just have the .NET as operator work in our scenarios (that don't always work today due to trimming). So, I think your ask will be addressed by that.