Xamarin Dev Team Garners Community Improvements, Asks for Suggestion Input -- Visual Studio Magazine

Xamarin Dev Team Garners Community Improvements, Asks for Suggestion Input

By David Ramel
11/18/2019

The Xamarin dev team highlighted awards for its recent Hacktoberfest 2019 contest held to garner community improvements to the mobile development platform for coding Android and iOS apps in .NET and C#.

Hacktoberfest 2019 – Xamarin Edition was held to solicit "quality pull requests," defined as "anything that substantially improves the quality of the product," as opposed to simply fixing typos.

This year's contest generated 178 pull requests from 72 contributors, which Samantha Houts said was almost double the respone of last year. Winning participants received stickers, t-shirts and glass trophies.

Houts also highlighted some community suggestions.

"We are always excited to receive contributions resolving bugs or adding small enhancements because those contributions are guaranteed to improve the products for you" she said. "We are equally excited to receive pull requests that contain significant, game-changing suggestions. Suggestion PRs are guaranteed to improve the community by opening discussion." She specifically asked for input on the following "interesting suggestions":

[Spec] CSharpForMarkup #8342: "The goal is to make Xamarin Forms more attractive for additional developer audiences that don't have XAML skills / preference. Developers with XAML skills can also benefit; declarative C# can be very similar to XAML and can offer increased productivity (due to excellent IDE support for C# and no need for language bridging mechanisms)."
Fluent API for initialization of Xamarin.Forms #8220: "What if we were to add a 'Fluent API' for initialization of Xamarin.Forms? Instead of calling several Init methods that are not very intuitive or discoverable, we can use a fluent mechanism.
Based on @jamesmontemagno post
https://montemagno.com/add-asp-net-cores-dependency-injection-into-xamarin-apps-with-hostbuilder/"
Updating DependencyResolver to use TypedParameter #8343: "Updates the Dependency Resolver to take a new TypedParameter. This helps with providing a proper Dependency Injection tie in as containers prefer to know the type a specified instance is for."

"We'd like to hear your opinion on these! Would you use them? Comment now by hitting those links above!" Houts said.

About the Author

David Ramel is an editor and writer at Converge 360.

Printable Format

comments powered by Disqus

Featured

Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.
Diving Deep into .NET MAUI

Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.
Copilot AI Boosts Abound in New VS Code v1.96

Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.
AdaBoost Regression Using C#

Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.
Versioning and Documenting ASP.NET Core Services

Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.