Creating a game requires many different skill sets, from programmers who write the code dealing with movement, animation, collisions, and scoring, to designers who draw the artwork and build the levels to play. Our CoinTime sample demonstrates both aspects of game development: you can browse the CocosSharp C# code to learn how cross-platform 2D game development […]
Indie game developers have chosen C# and Xamarin to release some truly amazing mobile games, including Skulls of the Shogun, The Incredible Baron, Draw a Stickman, and Infinite Flight. Many of these indies have even gone on to become powerhouse studios, like Supergiant Games, which appeared onstage with Apple to demo Transistor during the Apple TV launch. C#: The […]
Early Bird ticket prices (more than 20% off!) for Xamarin Evolve 2016 in Orlando, Florida end on December 31, 2015. Buy your tickets now so you don’t miss out! Evolve your Xamarin.Forms Apps Since launching last year, developers have been using Xamarin.Forms to create native UIs for iOS, Android, and Windows from a single shared […]
The post Learn Xamarin.Forms from the Experts at Xamarin Evolve 2016 appeared first on Xamarin Blog.
Some time ago, Scott Hanselman posted on Abandonware and
used my original Schematron.NET, which made it even to an
MSDN article by the (back then)
.NET XML PM Dare Obasanjo, as an example of abandonware:
Conclusion: The Schematron .NET implementation is total abandonware and I’m going to use it anyway.
As it happens, I got contacted by Pedro Frederico who had already done
the heavy lifting of polishing up the original source a bit, bringing it to GitHub, and contacting me about how
to proceed. That prompted me to contribute back a few minor changes, set up a
new repo for it, configure AppVeyor and voila: now we even have a CI-pushed
nuget package for Schematron.
So, dear Scott: I think that’s what we should all do with “abandoneware”. Bring it back to life, into modern life,
as we happen to come across it and find good uses for it.
Moral: What you care about, often ain’t what the other guy cares about.
As long as you make it stupidly easy for the original author to be on board (as Pedro did!), abandoneware doesn’t
mean more than “up for grabs”. The original author might not be too interested anymore in the project, but that
doesn’t mean it can’t still provide value to others, and continue flourishing on its own.
True Abandonware is closed-source software the original authors don’t care about anymore.
I for one are very happy to see Schematron alive again. Thanks Pedro!
PS: you can contribute PRs, report issues, etc. via GitHub, I’ll be happy to merge away, as well as support any documentation efforts ;).
The past few weeks I have been busy creating a new app based on the haveibeenpwned.com API. And it is ready!
The website haveibeenpwned.com is a website by security MVP Troy Hunt which focuses on data leaks, hacks and website breaches in all forms and shapes. While entering my usernames and passwords in there, I noticed there was also an API available.
Because I’m a big supporter of creating secure software ánd needed a new app project to try out push notifications, I took up this project to create a multi-platform app which leverages this API.
I does almost everything you can do on the website. It shows you which sites are indexed, read background information about the hacks, search through breaches and pastes for your own data and enable push notifications to be notified on new breaches.
The techniques I have used include, but are not limited to:
- Azure Mobile Services
- PortableRest NuGet
- Xamarin.Forms 2.0 with some CustomRenderers
Over the coming time I will describe some new things I have learned while creating this app. Probably starting with push notifications, which is going to be a big one divided into more posts.
You can check it out yourself for iPhone (Universal iPhone and iPad) and Android. Taking advantage of all that Xamarin has to offer there is of course also a Windows Phone version but this is giving me some troubles right now, so it will come soon.
Let me know if you like it, want to know how I did specific things or you can think of any more features I could add!
Xamarin 4 was designed to empower mobile developers by providing everything necessary to build and create great apps. The release included major enhancements and new features to the Xamarin Platform, such as Xamarin.Forms 2.0, as well as Xamarin.UITest 1.0, the Xamarin Test Recorder Preview, and general availability of our real-time app monitoring service, Xamarin.Insights, which enables […]
Continuous Coding with Xamarin iOS Frank A. Krueger wrote a new Xamarin Studio plugin that all Xamarin.Forms developers need. Handling Events in the Xamarin MessagingCenter Wallace McClure makes everything simpler with the Xamarin Messaging Center. Optimizing Xamarin.Forms Apps for Maximum Performance Pierce Boggan, from Xamarin Inc., shows us some tips for faster apps in the […]
As explained in XML vs XAML intellisense section of my blog post, Xamarin 4 ships with an XML-based intellisense for Xamarin.Forms we wrote from scratch. We have worked with Microsoft to make it possible to use the excelent built-in XAML language service instead, which knows about XAML’s specifics, and is driven by metadata provided by the Xamarin.Forms library.
In Visual Studio Update 1, a number of key issues were resolved that make the XAML language service quite usable for Xamarin.Forms XAML editing, so we’re releasing a Visual Studio extension to enable experimental support for it so that we can gather early feedback on what works and what doesn’t. Please file bug reports at our Xamarin Bugzilla tracker, for the
Visual Studio Extensions product, under the
You need to be using the latest stable version of the Xamarin.Forms nuget package, which contains the XAML language metadata required to provide intellisense.
We are providing this extension as an early preview and to gather feedback about things that should be improved or don’t work as expected. So please give it a shot and let us know how it works!
How do you tell if XAML language service is editing your file and not the XML language service?
If your XAML document contains an XML declaration, it will be in blue collor, rather than red:
(you can play “spot the other difference too ;))
Will this break anything on my stable dev environment?
Luckily, this is a minimally disruptive extension that just provides a bit of registry information to Visual Studio to know that it’s safe to open Xamarin.Forms XAML files with the XAML language service, that’s all. For additional reassurance, I’ve just put the extension source in GitHub if you rather see for yourself ;).
Given that, if anything breaks badly, recovery steps are:
- File a bug report!
- Uninstall the
Enable XAML Language for Xamarin.Formsextension from Visual Studio’s Extension Manager (or Extensions and Updates dialog nowadays).
And you’ll be back to normal.
Thanks and please let us know how it works!