Disclaimer: this is an automatic aggregator which pulls feeds and comments from many blogs of contributors that have contributed to the Mono project. The contents of these blog entries do not necessarily reflect Xamarin's position.

March 18

3 Ways to make more money with Unity IAP Promo.

Take your monetization to the next level by promoting in-app purchases (IAPs) throughout the player lifecycle. New from Unity, IAP Promo gives you this functionality for FREE, by serving existing product offers to players as a new type of ad unit. Surfacing these promotions helps players discover your offers organically, rather than having to search […]

March 16

Add Cloud Storage to Xamarin Apps with Azure Blob Storage

Cloud Storage has become a must-have feature for mobile apps. It gives developers the ability to store large files in the cloud and securely distribute them to all mobile app users. Moving these large files to the cloud also helps reduce the size of the APKs and IPAs significantly. Azure Blob Storage makes it extremely easy for Xamarin developers to implement Cloud Storage code in your cross-platform apps, allowing us to share 100% code across iOS, Android, and Windows.

What is Azure Blob Storage?

Azure Blob Storage is basically a giant folder in the Cloud. Just like a folder in the cloud, we can add anything inside that we need such as PDFs, photos, Word documents, etc. Each of these files are assigned a unique URL to access the folder, along with the added benefits of cloud storage, like GeoReplication and User Authentication.

In this post, you’ll learn how to create an Azure Storage Resource and retrieve the images stored in the cloud using the Azure Storage .NET Client libraries from a Xamarin.Forms project.

Getting Started with Cloud Storage

Before writing the code for our Xamarin app, let’s first use the Azure Portal to create an Azure Storage account for Blob Storage, then upload an image.

Free Azure Credits

If you are new to Azure, click here to get a free $200 credit!

Create New Azure Storage Resource

1. In the Azure Portal, create a new Storage Account.
Create Azure Blob Storage Container

Create New Blob Container

Now, let’s navigate to the newly created Azure Storage resource and upload some photos!
2. In the Azure Notification Menu (the bell icon at the top of the Azure Portal), select Go to Resource.
Navigate to Azure Blob Storage Resource
3. Click on Browse Blobs.
Click On Browse Blobs
4. Click on + Container.
  • Note: A container is like a folder in the cloud. In it, we will store Blobs which is just another name for a file
5. Name the new container “photos”.
6. Set the Public access level to Blob.
  • Note: For this example, we are creating a public blob storage container. For future projects that you do not want to be publicly accessible, set the Public access level to Private
7. Click Ok.
 Click On Add New Container
8. Click on the newly created container, “photos”.
Select Photos Container
9. Select Upload.
10. Select an image to upload from your computer.
11. Select Upload.
Select Upload Images
12. On the Azure Storage menu, select Access Keys.
13. Copy the Connection string for Key1. (We’ll need this for our Xamarin app!)
Copy Connection String
Our Azure Storage resource is complete. Let’s start working on our app!

Create a Simple Xamarin.Forms App

Let’s make a simple Xamarin.Forms app that uses our image from Azure Blob Storage. It will be a single-page app that communicates directly with our Azure Blob Storage Container using the Azure Storage SDK for .NET.


Add the following code to a Xamarin.Forms project, making sure to replace "Your Connection String" with the Connection String created in Step 13.
Simple Xamarin Forms App Using Azure Blob Storage


App.cs  is the starting point for every Xamarin.Forms app! In App.cs, we will set the MainPage to be our ImagePage  which will be wrapped in a NavigationPage  to provide a title bar.
public class App : Application
        MainPage = new NavigationPage(new ImagePage());


This file will display our image. In its OnAppearing  method, which runs every time the page appears in our app, we include the logic to retrieve the image from Azure Blob Storage.
public class ImagePage : ContentPage
    readonly Label _title = new Label{ HorizontalTextAlignment = TextAlignment.Center };
    readonly Image _image = new Image();
    readonly ActivityIndicator _activityIndicator = new ActivityIndicator();

    public ImagePage()
        Content = new StackLayout
            Spacing = 15,
            HorizontalOptions = LayoutOptions.Center,
            VerticalOptions = LayoutOptions.Center,
            Children = {

        Title = "Image Page";

    protected override async void OnAppearing()

        _activityIndicator.IsRunning = true;

        var blobList = await BlobStorageService.GetBlobs<CloudBlockBlob>("photos");

        var firstBlob = blobList?.FirstOrDefault();
        var photo =  new PhotoModel { Title = firstBlob?.Name, Uri = firstBlob?.Uri };

        _title.Text = photo?.Title;
        _image.Source = ImageSource.FromUri(photo?.Uri);

        _activityIndicator.IsRunning = false;
        _activityIndicator.IsVisible = false;


This is a generic static class that can be used in any project. It contains two public methods: GetBlobs  and SaveBlockBlob which can be called from anywhere in our app to retrieve and upload blobs from/to Blob Storage accordingly.
readonly static CloudStorageAccount _cloudStorageAccount = CloudStorageAccount.Parse("Your Connection String");
readonly static CloudBlobClient _blobClient = new CloudBlobClient _cloudStorageAccount.CreateCloudBlobClient();

public static async Task<List<T>> GetBlobs<T>(string containerName, string prefix = "", int? maxresultsPerQuery = null, BlobListingDetails blobListingDetails = BlobListingDetails.None) where T : ICloudBlob
    var blobContainer = _blobClient.GetContainerReference(containerName);

    var blobList = new List<T>();
    BlobContinuationToken continuationToken = null;

            var response = await BlobContainer.ListBlobsSegmentedAsync(prefix, true, blobListingDetails, maxresultsPerQuery, continuationToken, null, null);

            continuationToken = response?.ContinuationToken;

            foreach (var blob in response?.Results?.OfType<T>())

        } while (continuationToken != null);
    catch (Exception e)

    return blobList;

public static async Task<CloudBlockBlob> SaveBlockBlob(string containerName, byte[] blob, string blobTitle)
    var blobContainer = _blobClient.GetContainerReference(containerName);

    var blockBlob = blobContainer.GetBlockBlobReference(blobTitle);
    await blockBlob.UploadFromByteArrayAsync(blob, 0, blob.Length);

    return blockBlob;


PhotoModel  is the model class for our photo metadata. It is used to store the photo’s Uri and Title.
public class PhotoModel
    public System.Uri Uri { get; set; }
    public string Title { get; set; }
That’s it! Now launch the app and enjoy!

Going Serverless with Azure Functions + Azure Storage

Azure Functions are a great compliment to Azure Blob Storage because they allow us to offload any metadata processing from the Xamarin app to the cloud, and they can help ensure our metadata doesn’t get corrupted. You can download an advanced example that incorporates Azure Functions from my GitHub repo.
Azure Blob Storage Sample App Diagram
This Xamarin app uses a SQLite Database to store the metadata of the Photos (e.g. Url, Title) locally on our Xamarin device. The local database syncs, via an Azure Function, with an Azure SQL Database that contains the metadata of the Photos stored in Azure Blob Storage. It also allows the user to take photos and save them to Azure Blob Storage. To do this, the Xamarin app uploads the image to an Azure Function, and the Azure Function saves the image in Azure Blob Storage, then adds the image metadata to the Azure SQL Database.

Learn More

Dive deeper into these topics and more on the Microsoft Docs:

About The Author

Brandon Minnick is a Xamarin + Azure Developer Advocate at Microsoft. As a Developer Advocate, Brandon loves helping developers build cloud-connected mobile apps! Brandon loves talking about mobile and invites you to start up a conversation @BrandonXamarin!


The post Add Cloud Storage to Xamarin Apps with Azure Blob Storage appeared first on Xamarin Blog.

The High Definition Render Pipeline: Focused on visual quality

In a recent blog post, we introduced the concept of Scriptable Render Pipelines. In short, SRP allows developers to control how Unity renders a frame in C#. We will release two built-in render pipelines with Unity 2018.1: the Lightweight Pipeline and High Definition Render Pipeline. In this article, we’re going to focus on the High […]

March 15

Ooui.Wasm - .NET in the browser

I’ve been obsessing over my little .NET web framework Ooui and am excited to announce that it is now capable of running fully in the browser as a web assembly. This means that Xamarin.Forms apps can run completely in the browser - without a smart server - giving .NET developers even more reach and options for distributing their apps. Try the Xamarin.Forms XAML editor demo online or read the getting started guide if you want to try it yourself.



This simple XAML Editor running as a web assembly demonstrates the power of web assembly nicely. It demos Xamarin.Forms running in the browser and shows that all logic is working by enabling you to edit the displayed XAML.

I’m hosting it on S3 to drive home the point that this app is distributed as just a bunch of static files - all execution is done in the client browser. Once the app is loaded, you can turn off your network and everything will keep working. You can also inspect the HTML source to see that it’s just a shell of an app.

You may be asking how this works. Web assembly is the latest browser tech to enable non-JavaScript languages to execute in the browser. In the past, the only way to create HTML5 web apps was to write JavaScript or to compile your app down to JavaScript (like Netjs and Fable do). This obviously works but has limitations because JS wasn’t designed to be a low-level target language. Fortunately, the browser cabal that runs the internet has recognized this shortcoming and have created web assembly - a proper low-level target for programming languages to compile down to.

Web developers are no longer forced to work with JavaScript and thanks to the amazing work of the mono team, we can run full .NET code (.NET Standard 2.0) in the browser! This even works on mobile browsers. Wild!

Easy as 1-2-3

You can now create a .NET web assembly app with just 3 commands:

dotnet new console
dotnet add package Ooui.Wasm
dotnet build

This will create web assembly build of your app ready to be run in any modern browser. The build is tucked away in a dist subdirectory of your bin directory.

Now that app is quite boring and will just print “Hello World!” to the console instead of displaying the words. To fix this, we can edit the program:

UI.Publish("/", new Span("Hello World!"));

That one line of code will add a span to the HTML document to display the greeting. Every Ooui.Wasm app declares its initial UI by publishing that root element. Of course, the app is free to change things afterward. Check out the getting started guide for a longer example.

Xamarin.Forms in Web Assembly

Since Ooui.Forms already implements a backend for Xamarin.Forms, Xamarin.Forms works out of the box in web assembly!

I wrote a getting started guide for Xamarin.Forms that walks you through a complete example.

Pros and Cons of Web Assembly

Let’s compare writing an app with web assembly to writing a more traditional web app with Ooui.


  • Pro: Uses billion-year-old HTML that works everywhere in the known universe. Google can read it, bots can read it, and it probably might work in Internet Explorer.
  • Con: You need to run a web server that can execute code and that server will have to scale as your users increase.
  • Pro/Con: Data is shared by default between users (since it’s all coming from the server)

Web Assembly

  • Pro: No smart server needed - you can host your app on a static web server such as Amazon S3, Azure Blob, another CDN, or a low-power device.
  • Pro: Apps can be cached to be able to run in disconnected scenarios.
  • Con: Relies on fancy new support in modern browsers. Fortunately support is ubiquitous today, but this won’t be working on Windows XP.
  • Pro/Con: Data is private by default between users (since everything is running locally)

The last items were marked pro/con because it really depends on your app whether data between users should be easily shared. If you’re making a social network, then yes you want easy sharing. If you’re making a private journaling app, maybe local is right.

Comparison with Blazor

Blazor is an amazing product experiment from Microsoft that also uses mono’s web assembly support. Instead of exposing the DOM and classes and objects as Ooui does, it uses Razor templates composed through “components” to build your UI.

You can think of Ooui.Wasm and Blazor as application frameworks running atop a common runtime (mono wasm). Ooui was designed to feel like classical native object oriented UI development which enables it to run even higher-level app frameworks like Xamarin.Forms. Blazor was designed to feel like modern React-style web development where you’re writing HTML templates. Pick your poison.

Big Thanks

It’s surprising how little of Ooui had to change in order to work as a web assembly. This is thanks to the amazing effort of the mono team. I want to especially thank Rodrigo Kumpera for helping me get everything working.

ML-Agents v0.3 Beta released: Imitation Learning, feedback-driven features, and more

We are happy to announce that the ML-Agents team is releasing the latest version of our toolkit, v0.3. This is our biggest release yet, and many of the major features we have included are the direct results of community feedback. The new features focus on expanding what is possible with ML-Agents with the introduction of […]

March 14

Xamarin Joins docs.microsoft.com

Today we’re beginning a new chapter in mobile developer documentation: Xamarin docs are now live on docs.microsoft.com/xamarin! Here are a few highlights of the new documentation experience:

Xamarin Docs Hub

All our documentation options are a click or two away from docs.microsoft.com/xamarin. Click Xamarin in the header to return there from any page. Use the platform links to see our mobile developer docs, and switch to the Graphics & Games or Tools tabs to learn more about related topics such as SkiaSharp, Workbooks, and the Xamarin Live Player.

New Navigation

docs.microsoft.com/xamarin offers some new options for navigating Xamarin documentation:

  1. Platform home pages: Overview and quick reference for the docs available on each platform. Use the links in the blue header bar to visit each platform page:
  2. Search: Click the magnifying glass at the right of the header to search Xamarin content.
  3. Breadcrumbs: Tucked under the header, breadcrumbs help find your way to related docs.
  4. Navigation tree: Quickly drill down using the tree-view.
  5. Navigation filter: Filter the navigation tree to find a topic heading.
  6. In this article: Each article has a table of contents generated, including a handy indicator for your scroll location in the doc.
  7. Image zoom: Images with a magnifying glass icon in the bottom-right corner can be clicked to show more detail.


Presentations and lessons from evangelists and Xamarin University are now available inline, such as this Xamarin.Forms Layouts topic:

Open Source

Each page contains an Edit link so that the community can contribute fixes and updates. Comments on the docs become GitHub issues so you track the progress of your docs feedback. Read the contribution guidelines for instructions on submitting changes.

In Your Language

Using a combination of translation techniques, Xamarin developer documentation is now available in 13 languages besides English: Chinese (Simplified), Chinese (Traditional), Czech, French, Italian, Korean, German, Japanese, Polish, Portuguese (Brazil), Russian, Spanish, and Turkish. Visit the docs blog for more information on international features.

Editor Switcher

Sometimes you need instructions specific to either Visual Studio 2017 or Visual Studio for Mac. These are now located in tabs within each page:

Beautiful Code

Code snippets are syntax-highlighted, and there’s a Copy button that makes it easy to grab snippets for your apps:

API Browser

The Xamarin BCL API docs are already available in the .NET API Browser, and our platform-specific APIs are coming soon.

Responsive Design

Whether you’re reading on your phone, your tablet, or your desktop, the docs.microsoft.com site scales to ensure the content is clear and easy to read, while keeping the navigation accessible:

Dark Theme

There’s also an option to read the docs with a Dark Theme!

What’s Next?

Some content is still being hosted on our old site, including API docs, Workbooks, and Samples. The team is working hard to migrate these over to create a unified experience. Don’t worry if you have bookmarked or blogged links to the old developer site; they’ll automatically redirect to the equivalent page on the new site.

We’re so excited by all the new features available on docs.microsoft.com/xamarin and look forward to building an even bigger, better documentation experience for Xamarin developers everywhere!

Let us know what you think by discussing this post in the forums.

The post Xamarin Joins docs.microsoft.com appeared first on Xamarin Blog.

Neon Challenge: Community Creations and Winners

The Neon Challenge has wrapped up, challenging our community to create a real-time environment with the help of the Asset Store. Here are your winners. On Dec 1, 2017 we launched Unity Connect’s first contest, the Neon Challenge, a real-time environment contest based on Neon with over $30,000 in prizes. Armed with our powerful new […]

March 13

Next week: How to join us online for Unity at GDC

Staying home for GDC this year? Here’s how you can join us online. Soon, thousands of game developers will storm San Francisco for GDC, to spend a jam-packed week learning, exchanging ideas, getting inspired and making connections. It’s always one of my favorite industry events of the year, and luckily, because GDC happens in my […]

March 12

Podcast: Visual Studio 2017 version 15.6, AR with UrhoSharp, and ML with CoreML

In this episode of the Xamarin Podcast, James Montemagno and I discuss the fun new features in the Visual Studio 2017 version 15.6 stable release, including macOS environment setup and iOS WiFi deployment. We also discuss building AR and ML into your mobile apps, and take a look at how you can add Tizen as a deployment target for your Xamarin.Forms apps.

Be sure to download today’s episode from your favorite podcast app.

Subscribe or Download Today

Keeping up with the latest in .NET, C#, and Xamarin is easier than ever with the Xamarin Podcast! Cohosts Pierce Boggan and James Montemagno cover topics relevant to Xamarin developers, from designing mobile apps to identity management. Be sure to subscribe to the Xamarin Podcast on iTunes, Google Play Music, Stitcher, or your favorite podcast app you use to ensure you don’t miss an episode.

The post Podcast: Visual Studio 2017 version 15.6, AR with UrhoSharp, and ML with CoreML appeared first on Xamarin Blog.

Photogrammetry in Unity: Making Real-World Objects into Digital Assets

Photogrammetry is the process of using multiple photos of the real-world objects to author game-ready assets. It’s best suited to objects that are time-consuming to produce in 3D sculpting software. This post explains how new Unity features assist you in working with photogrammetry. We’re also sharing our Fontainebleau photogrammetry demo project, including all meshes, textures […]

March 9

Spotlight Team Best Practices: Making believable visuals in Unity

Being part of the Spotlight Team, I am fortunate to be involved in some very interesting projects. The Spotlight Team at Unity works on games together with our customers and a significant part of my role is to help developers achieve the desired look and quality for their projects. I get to hear many stories […]

March 8

Contributing to Xamarin.iOS and Xamarin.Mac

Two years ago this month, we made some exciting announcements about the future of Xamarin. One of those announcements detailed the open sourcing of the Xamarin.iOS and Xamarin.Mac SDK. Open source is fantastic for developers, but it can be a little overwhelming to know where to start on a project as large as the Xamarin SDKs themselves. If you’re curious about how you can contribute, we want to share some tips to help get you started.

Ways to Contribute

Report Issues

There are many ways to contribute to an open source community; writing code isn’t the only opportunity to be helpful. Writing good bug reports is a perfect example of an opportunity to contribute to the Xamarin SDK, while also detailing an issue you are having so it can be fixed.

Use Visual Studio Preview

Another way to contribute to these SDKs is to download and use the Visual Studio Preview. If you’re working in Visual Studio for Mac, use the Channel Updater and update using the Alpha channel. Installing previews and working with them as early as possible is vital to giving us your feedback on the next version of Visual Studio. You’ll also get to experience the very latest in bug fixes, performance improvements, and any new features we may be working on.

Stay on the Bleeding Edge

Things change quickly in the mobile world. When a new version of Xcode is in beta, we make support for that available as quickly as possible and publish a download link on our release blog. You can always find the latest packages on Jenkins as part of our Continous Builds too. This is a great way to experience the latest versions available when you’re working in Visual Studio for Mac.

Join the Community

The Xamarin SDK teams work in the open and you can join the conversation on Gitter. While not for support, Gitter is a great place to talk with the team about the development of these SDKs. If you’re not working on the development of an SDK and need support for a problem, the best option is to file an Issue.

Submit a Pull Request

Writing code is an obvious way to contribute and pull requests are welcome! If you’re looking for the best place to get started, we recommend checking for issues that are labeled help wanted or bug. Be sure to also check out the wiki for additional tips on where to contribute and coding guidelines. Merged pull requests will eternalize your name in the release notes as a contributor, and also gain our deepest appreciation!

We look forward to seeing you in the community and becoming part of the family. Thank you for helping make Xamarin and Visual Studio better!

Discuss this post on the Xamarin Forums

The post Contributing to Xamarin.iOS and Xamarin.Mac appeared first on Xamarin Blog.

International Women’s Day 2018: Celebrating women in technology

Today, March 8th is International Women’s Day. It’s a global day celebrating women’s equality, and the political, economic, and social achievements of women. To honor this day, we’re asking a few of our inspiring Unity women what this day means to them. We encourage you to take a moment to read their responses and celebrate […]

March 7

Jupyter lab with an Octave kernel

Octave is a good choice for getting some serious computing done (it’s largely an open-source Matlab). But for interactive exploration, it feels a bit awkward. If you’ve done any data science work lately, you’ll undoubtedly have used the fantastic Jupyter.

There’s a way to combine both and have the great UI of Jupyter with the processing core of Octave:

Jupyter lab with an Octave kernel

I’ve built a variant of the standard Jupyter Docker images that uses Octave as a kernel, to make it trivial to run this combination. You can find it here.

Comments | More on rocketeer.be | @rubenv on Twitter

How ARCore enables you to create brand new types of user interaction

AR frameworks unlock new types of gameplay and user interaction. Here are some practical ideas to inspire you to start building. We encourage you to share your own creations with the community – we’ll be actively looking for great examples! Back in 2003, Konami released the Game Boy Advance title, Boktai: The sun is in […]

DevOps with Bamboo and Plastic

DevOps is all about breaking silos and making production and development cooperate to deploy a continuous flow of stable changes to production.

In the previous blogpost, DevOps Primer, I explained the basics of what DevOps is and our vision on how to implement it with Plastic SCM.

This blogpost will start where the last one ended and will cover how to implement a full DevOps cycle using both Atlassian's Bamboo and Plastic SCM.


I will delve into the details of how to handle task branches with Plastic and then run tests, merge and deploy using Bamboo with the Plastic Plugin. The entire cycle is based on the Bamboo Gatekeeper feature using Plastic attributes that are set to branches to decide when a branch is ready to be merged.

March 6

Visual Studio 2017 Version 15.6 Now Available!

Our last release, Visual Studio 2017 version 15.5, featured awesome new updates, such as the iOS Remoted Simulator becoming available to all developers, live XAML previewing in Android emulators with the Xamarin Live Player, new Xamarin.Forms project templates for .NET Standard, and improvements to the Mac pairing mechanism.

In our latest release, Visual Studio 2017 version 15.6, we’re excited to build on that progress with features, including automatic macOS environment setup, iOS WiFi deployment, live XAML previewing in the Remoted iOS Simulator, and more! Update today by using the Visual Studio Installer, and check out the post below for more details on the new features.

Machine Learning with CoreML

CoreML was introduced in iOS 11. With Visual Studio 2017 version 15.6, iOS apps can now take advantage of this new framework to use trained machine learning models to perform tasks.

Check out our Introduction to CoreML tutorial and sample project to get started today.

iOS WiFi Deployment

The Remoted iOS Simulator allows developers to test and debug iOS apps entirely in Visual Studio on Windows. It was made available to all editions of Visual Studio, including the free Community Edition, in the last release. The simulator supports functionality such as location simulation, rotation, gestures, and even includes functionality that the iOS simulator on Mac does not, like multi-touch. This provides a great simulator experience for developers building iOS apps on Windows, but what about the experience for devices?

With Visual Studio 2017 version 15.6, you can now deploy your iOS apps to devices over the network with WiFi deployment, no cables required! After setting up a wireless device in Xcode, it will show up in Visual Studio just like a normal deploy target.

Automatic macOS Environment Setup

Building iOS apps with Visual Studio 2017 just got even easier. With the new automatic macOS setup feature, instead of manually maintaining your Mac build machine, all you need to do now is connect to the Mac and we’ll handle the heavy lifting of installing and configuring your build machine with the correct Xamarin.iOS and Mono bits, all from Visual Studio on Windows!

Android Oreo 8.1 Support

Visual Studio 2017 version 15.6 adds support for Android Oreo 8.1, so you can take advantage of new features like Android Go, Neural Networks API, Autofill framework enhancements, and SharedMemory API in your Android apps. For more detailed information on how to get started with Android Oreo, please see our documentation.

Live XAML Previewing with the iOS Simulator

The Xamarin Live Player enables developers to continuously deploy, test, and debug their apps using just Visual Studio and an iOS or Android device. We previously added support to preview real-time XAML changes directly in the Android emulator without requiring a recompile or redeploy, and this release brings that same functionality to the Remoted iOS Simulator for Windows.

To get started, select an iOS simulator from the deployment targets dropdown, and choose Live Run Current View using the context menu, keyboard shortcut, or the banner at the top of each XAML file.

So much more!

This release also includes Xamarin.iOS 11.8 and Xamarin.Android 8.2, improvements to design-time build performance for Android developers (which affects solution load and provides metadata for IntelliSense, among other things), and static analysis for Xamarin.iOS projects.

Let Us Know Your Feedback

We need you to help shape the future of Visual Studio Tools for Xamarin! Tell us what you think of Visual Studio 2017 version 15.6 by sharing with us on Twitter via @xamarinhq or @pierceboggan. If you encounter any bugs, performance issues, or other strange behavior, let us know by using the Report a Problem tool in Visual Studio. For more information on everything that’s new in Visual Studio 2017 version 15.5, check out the complete release notes.

The post Visual Studio 2017 Version 15.6 Now Available! appeared first on Xamarin Blog.

Unity Partners with PiXYZ Software to unlock CAD data for real-time development

Together, Unity and PiXYZ deliver a solution that makes creating real-time interactive and virtual experiences based on CAD data faster and easier than ever before. Unity today is used across many industries beyond gaming, including aerospace, architecture, automotive, construction, gambling, transportation, manufacturing, medical, and more. The benefits of using real-time in these industries include accelerating […]


Monologue is a window into the world, work, and lives of the community members and developers that make up the Mono Project, which is a free cross-platform development environment used primarily on Linux.

If you would rather follow Monologue using a newsreader, we provide the following feed:

RSS 2.0 Feed

Monologue is powered by Mono and the Monologue software.