This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(156.8, 79%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPJ%3C/text%3E%3C/svg%3E)
I've been a Xamarin developer for over 6 years and used to contribute to and rely on the Xamarin Forums when they were active. Now that they've been replaced by this site, it seems like all the members have left. I see only two questions answered in the month of July and ironically, one of those is asking whether using Xamarin is a mistake.
It would be of huge benefit to the dev community if this site was truly usable, so can I ask you Microsoft/Xamarin guys to take the initiative and make this site as good or better than the forums were?
Thanks.
Hey there Phil, the Xamarin Forums have officially been retired as of July. There was a 8 month plan that was outlined on the forums before they moved here to Q&A. They have been archived -> https://aka.ms/xamarinforum-archives
@James Montemagno the OP was asking about the forum members, not the posts themselves.
I was an active member on the previous forums, but here I’m not sure why I should bother? After all the likes and answers I gave on the previous forums, it felt like a kick in the teeth when it was announced it was moving. Ok that wasn’t the reason for helping people, but Xamarin support was (and still is) so poor, I was happy to help. Why should I bother helping now, when the ‘answers’ occasionally come back from MS with a ‘yes we replicated can you post on github instead’. Um isn’t that what support is for? Why bother posting anything here at all?
And Xamarin Forms support, how absolutely shocking is that? Confirmed GitHub issues are ignored unless you have a support contract. We have a massive Azure subscription having just migrated from AWS, but we didn’t up the support level from basic. So fundamental issues are just ignored for MAUI dev.
To answer the OP, I don’t and won’t speak for all the previous members, but I know of several that have moved on to better, supported technologies. We definitely aren’t building anything new with Xamarin.
James, I know you host the Xamarin Show, I was thinking of creating another called The Xamarin Sh!t Show, coz that’s really what it is.
2yrs later, this follow-up post is still a huge reference win!
Having done KB migrations in the past, one thing I wish came migrated over is to include the previous (dead) URL's ID and/or full URL in the new location. This assists in searches when the previous link's title is unknown.
i.e. Deadlink with an unknown linkage to the new source. Still not sure if this is the correct linkage
Much of the support work is now available via both GitHub issues and discussions on the Xamarin Forms and Maui repos and there is a very active presence on Discord. I've been able to actively engage the Maui developers on Discord and have had a number of issues successfully addressed. The Visual Studio "Report A Problem" feature DOES actually get to the proper developers for attention and they DO follow up when an appropriate amount of information is available, so spending the time to provide a proper repro is time well spent. I was a Microsoft Escalation Engineer until I retired in 2012 and I can tell you that support from Microsoft has vastly improved since the move to Open Source for .NET.