Xamarin Studio 5.2
- PDF for offline use:
Xamarin Studio 5.2.1 is a hotfix release based off of Xamarin Studio 5.2.0.
- Fixed random hangs of Xamarin Studio.
- Fixed code completion in .xaml files.
Side-by-side editing support
This release add support for placing text editors side-by-side and for detached floating editors.
2-column mode can be enabled by using the "2 columns" command (Command+Option+2 on Mac, Control+Shift+2 on Windows) or by dragging an editor tab to one of the edges of the editor area.
Once the IDE is in 2-column mode, you can move editors between columns as you wish.
Editor tabs can be dragged out of the document area to create floating editor windows. A floating window can contain several editors.
Added framework retargeting support
When the project’s target framework or PCL Profile is changed in the Project Options, Xamarin Studio will check whether that new project target framework / profile requires a different assembly from the NuGet package to be installed or if the NuGet package is incompatible with the new project framework. The results of this compatibility check are displayed in the Package Console and affected packages are highlighted with warning icon in the Solutions window.
To retarget the NuGet package, right click the package or Packages folder and select Retarget. This will reinstall the NuGet package so the correct assembly is referenced by the project.
Automatic Package Update Check
Xamarin Studio will check in the background for updated packages when a solution is opened. This can be disabled in Preferences via the Check for package updates when opening a solution option.
Updated package information is shown in the Solution window on the Packages folder and on each Package inside the Packages.
Support custom package repository path in NuGet.Config
In the NuGet.config file, the standard directory used to install packages can now be overriden. This can be useful if you have multiple solutions in different locations which you would like to share the same packages directory. By default directory is "packages” inside the solution directory.
<configuration> <config> <add key="repositoryPath" value="../../MyPackages"></add> </config> </configuration>
Other NuGet improvements and fixes
- Fixed Visual Studio compatibility for MSBuild imports added to a project with NuGet by adding a condition to the import that checks the imported file exists. This allows a project created by Xamarin Studio to be opened in Visual Studio when packages are missing.
- Fixed repositories.config file not being properly restored.
- All checked packages in Add Packages dialog are now installed even if they are not currently displayed.
- Improved status bar message when updating packages. Previously Xamarin Studio would show a message indicating that the packages were updated successfully even when no updates occurred. Now when no updates are available the status bar message will display "Packages are up to date".
- Fixed incorrect Add Packages button label when a single package checked in Add Packages dialog.
- Package dependencies are now resolved from all enabled package sources and not just the currently selected package source in the Add Packages dialog.
- Before updating NuGet packages Xamarin Studio will now check to see if any NuGet packages are missing for the project and restore them before attempting the update. Updating a package when packages are not restored can fail since the older NuGet package will need to exist so it can be uninstalled. Restoring missing packages before attempting to update the packages fixes this problem.
New unified exception, function and location breakpoints dialog
All kinds of breakpoints (based on location, function or exception) can now be created with the single command "New Breakpoint" in the Run menu. Also, all breakpoints can be managed in the Breakpoints pad.
As a result of this unification, some features which were previously only available for location breakpoints, are now also available for exception and function breakpoints, such as Hit count conditions, or the option to log a message when the breakpoint is hit.
Other debugger improvements and bug fixes
- Fixed a bug in resolving some variables in the debugger tooltips when "Allow implicit property evaluation and method invocation” is disabled. Fixed a bug caused by the use of UseShellExecute when running an application under a custom SDB debugger command. Fixed the completion-list logic to hide compiler-generated fields. Fixed the bug that sometimes caused the exception popup from going away in the editor.
- Fixed the completion-list logic to hide compiler-generated fields.
- Fixed the bug that sometimes caused the exception popup from going away in the editor.
Xamarin Designer for iOS
- Views can now be rearranged using the new SendBackward, SendToBack, BringForward and BringToFront commands.
- A project load error is no longer triggered if the designer cannot be initialized when opening a solution containing an iOS project.
- Improved the alignment marker logic so that mid/baseline drop areas are preferred over top/bottom/left/right alignment markers
- Improved handling of UIViewController.LoadView/UIViewController.ViewDidLoad when rendering custom controls.
- UIButton frames are now updated as expected when changing the type back to 'System'
- Fixed an issue where some tristate properties would not change out of the 'indeterminate' state.
- Duplicate files are no longer added to the solution if a UIView or UIViewController is made a custom class and a file of that name already exists.
- We now support generating [Action] methods with no sender parameter
- Improved support for Xcode6 and Yosemite. Some crashes caused by Xcode 6 / iOS8 support have been resolved.
- An exception triggered by selecting a constraint which references a Top or Bottom layout guide has been fixed.
- Fixed a case where we could generate invalid storyboard files when working with UITextView.
- Fixed a crash triggered by disabling autolayout under certain circumstances.
- The iOS Designer was misgenerating partial methods associated with Actions. The bug caused them to semi-randomly appear/disappear from the .designer file.
- ASP.NET MVC project templates have all been updated to ASP.NET 5.1.2.
- ASP.NET MVC project templates now use NuGet references.
- ASP.NET MVC projects are now compatible with VS2013.
- ASPX CodeBehind is now only updated on saving the ASPX file. It is not longer updated when building the project.
- HTML5 doctype is now used for new files.
Other Improvements and Bug Fixes
- Simplified the options panel for choosing the IDE fonts.
- F#: fixed bugs in Android fragment templates, which were producing invalid code. Tooltips now display in F# scripts that are not part of the current project
- Xamarin.Mac: fixed a bug preventing custom "Document Types” in the Advanced section of the Info.plist editor from loading the CFBundleTypeIconFile icons that the user had previously specified.
- Version control: fixed an interface corruption caused by the Commit Dialog.
- Fixed memory leak when reloading solutions
- Fixed context menu positioning issue on Macs with retina display (bug 20938)
- Fixed exceptions thrown by Windows Native File dialogs when working with encodings.