Release Notes v3.4.0

January 25th 2018

Introduction

This is a summary of the changes introduced in v3.4.0 of MFractor for Visual Studio Mac.

This release adds an MFractor powered XAML IntelliSense engine!

The MFractor XAML editor is a dramatic improvement on Visual Studio for Macs default IntelliSense. MFractors IntelliSense has feature parity and injects a lot of MFractors smarts into the XAML editing experience.

Initially we've added obvious auto-completions to take the friction out of what you're currently working on; for example, we suggest available properties when creating a style setter based on the styles TargetType, suggest available images when editing an image source or even suggest available properties for databinding when MFractor can infer the view model.

We've also revamped our free licensing model; previously we had several feature groups as free and allowed up to 5 pro features per day; this licensing model was confusing, hard to communicate and didn't let you fully evaluate what you'd get by upgrading to MFractor Professional.

To simplify our free tier, we now allow unlimited use of all of MFractor's features in 2 XAML files per day. After you've used your 2 documents per day, Visual Studio for Mac will revert back to it's original behaviour. Additionally, all C# refactorings and inspections are still available in only MFractor Professional.

Features

XAML IntelliSense:

Feature parity with Visual Studio Macs XAML IntelliSense.

The ability to generate property bindings from XAML when MFractor can resolve the ViewModel. This is intentionally deactivated in DataTemplates, ResourceDictionaries and the App.xaml.

Suggest all available properties when the view model for a XAML view can be resolved.

Suggest FontSizes such as Micro, Small, Large etc

When in a GridUnit element, suggest Auto and *.

Suggest the .Behaviors property for VisualElements and suggest available behaviors.

Suggest the .Effects property for VisualElements and suggest available effects.

Suggest the .Triggers property for VisualElements and suggest available triggers.

Suggest the .GestureRecognizers property for Views and suggest available gesture recognisers.