After upgrading my Visual Studio to Update 2, I tried to do my first steps with Xamarin.However I am unable to connect my MacBook. Desktop mac powerful enough for studio one 3 pro.
Active2 years, 7 months ago
October 16 in Visual Studio Every time files change externally - for example when I pull changes from git or switch branches - VS Mac crashes. Running 7.6.2 (build 22).
This is my Setup:MacBook Pro with OSX 10.11.3Windows 10 Enterprise - newest updates installedVisual Studio Enterprise 2015 Update 2
Down below is the error I get when trying to connect my MacBook.
I did check, it created the folders and due to the permission denied error I did a chown for the user I use to login to the mac for the whole Xamarin directory- did not help..
If someone could help me solve my little problem I would be happy.
Thanks in advance.
After changing the Channel to Alpha I get this:
It is nowhere written that I have to have mono on my mac ..
After installing mono I received this error ..
Outlook 365 For Mac Keeps Crashing
mhenkel
mhenkelmhenkel
7 Answers
Xamarin for Visual Studio doesn't install some requirements on the Mac side like Xamarin.iOS, Xamarin.Mac and Mono. All of those are requirements that are installed by the Xamarin Studio installer on the Mac (from http://xamarin.com/download). You should hit that URL from the Mac itself to get the Mac download, otherwise you'll see the Windows download.
As mentioned before, you will also need to configure 'Remote Login' on the Mac. And additionally, you need an open session on the Mac with the same credentials you're using from Windows to connect. On other words, if you're using a 'User1' on the Mac, that User1 should be logged in on the Mac, and those Mac credentials will be the ones Visual Studio is asking for when it tries to connect.
For more help please take a look at the troubleshooting guide.
Finally, if you're still facing issues connecting to your Mac, please share the logs (Help - Xamarin - Zip Logs). That includes diagnostic information that can be very helpful.
Jose GallardoJose Gallardo
Try changing to the 'Alpha Channel' must be changed in Visual Studio and Xamarin study and update all
Aderson RangelAderson Rangel
Most of these issues usually go away if you install Xamarin Studio on the Mac you wish to use as your build/iPhone simulator host (from http://xamarin.com/download). It bundles 'all the things'.
That installer includes Mono, among other things. Also make sure you enable remote login on the mac (ssh) for the user you wish to connect with (which is in the 'Sharing' control panel for some interesting Apple-y reason).
HenningKHenningK
The problem that I discovered (thanks to the one who wrote about the logs) was that Xamarin Build Agent, while trying to connect to the Build Host, failed when reading the .bashrc file.
It came down to that I had the line 'source dnvm.sh' and that dnvm.sh no longer exists on my system. That made the program crash when the script was being executed.
So check the logs!
Robert SundströmRobert Sundström
To solve mono cannot be found you could download mono from here:
Updated: try to install xamarin on Mac, change update channel to alpha in xamarin studio and update xamarin.
![]()
1,94811 gold badge2020 silver badges2525 bronze badges
I run OSX on a local VM on my Windows 10 machine. This set up has worked well the past few months until this morning. Yesterday I updated Xamarin in Visual Studio 2015 and on my OSX instance. Then I continued working all day.
This morning I could not connect to my Mac Agent. So I started troubleshooting the problem.1.Connected to the MacMini I have on the network fine. So, The issue is on my VM version of OSX.2.Can SSH to the VM3.Check the logs and see the problem is a hung broker on my OSX instance.4.Deleted the XMA Folder on OSX and forced it to regenerate.
Issue fixed.
Robert CavanaughRobert Cavanaugh
Visual Studio For Mac Keeps Crashing On Mac Mini
I have found the problem. If your Visual studio has a open xamarin solution, then u are changing some proxy or network settings. the Mac agent doesn't get the latest settings. so answer is close VS 2013 or 2015, make the network / proxy changes in IE Open VS and open the Xamarin solution again. wao the mac agent works like a charm and auto connects to Mac
Sundara PrabuSundara Prabu
Not the answer you're looking for? Browse other questions tagged macosvisual-studioxamarin or ask your own question.
Since it was released a little more than a year ago, Visual Studio 2017 for Mac has grown from being an IDE primarily focused on mobile application development using Xamarin to one that includes support for all major .NET cross-platform workloads including Xamarin, Unity, and .NET Core. Our aspiration with Visual Studio for Mac is to bring the Visual Studio experiences that developers have come to know and love on Windows to the MacOS and to provide an excellent IDE experience for all .NET cross-platform developers.
Over the past year, we added several new capabilities to Visual Studio for Mac including .NET Core 2; richer language services for editing JavaScript, TypeScript, and Razor pages; Azure Functions; and the ability to deploy and debug .NET Core apps inside Docker containers. At the same time, we have continued to improve Xamarin mobile development inside Visual Studio for Mac by adding same-day support for the latest iOS and Android SDKs, improving the visual designers and streamlining the emulator and SDK acquisition experiences. And we have updated the Unity game development experience to reduce launch times of Visual Studio for Mac when working together with the Unity IDE. Finally, we have been investing heavily in fundamentals such as customer feedback via the Report-a-Problem tool, accessibility improvements, and more regular updates of components that we share with the broader .NET ecosystem such as the .NET compiler service (“Roslyn”), and the .NET Core SDKs. We believe that these changes will allow us to significantly accelerate delivery of new experiences in the near future.
While we will continue to make improvements to Visual Studio 2017 for Mac into early next year, we also want to start talking about what’s next: Visual Studio 2019 for Mac. Today, we are publishing a roadmap for Visual Studio for Mac, and in this blog post, I wanted to write about some of the major themes of feedback we are hearing and our plans to address them as described in our roadmap.
Aol Desktop For Mac Keeps CrashingImproving the performance and reliability of the code editor
Improving the typing performance and reliability is our single biggest focus area for Visual Studio 2019 for Mac. We plan to replace most of the internals of the Visual Studio for Mac editor with those from Visual Studio. Combined with the work to improve our integration of various language services, our aspiration is to bring similar levels of editor productivity from Visual Studio to Visual Studio for Mac. Finally, as a result of this work, we will also be able to address a top request from users to add Right-To-Left (RTL) support to our editor.
Adobe Acrobat For Mac Keeps CrashingSupporting Team Foundation Version Control
Including support for Team Foundation Server, with both Team Foundation Version Control (TFVC) and Git as the source control mechanisms, has been one of the top requested experiences on the Mac. While we currently have an extension available for Visual Studio 2017 for Mac that adds support for TFVC, we will integrate it into the core of the source control experience in Visual Studio 2019 for Mac.
Increased productivity when working with your projects
The C# editor in Visual Studio for Mac will be built on top of the same Roslyn backend used by Visual Studio on Windows and will see continuous improvements. In Visual Studio 2017 for Mac (version 7.7), we will enable the Roslyn-powered brace completion and indentation engine which helps improve your efficiency and productivity while writing C# code. We’re also making our quick fixes and code action more discoverable by introducing a light-bulb experience. With the light bulb, you’ll see recommendations highlighted inline in the editor as you code, with quick keyboard actions to preview and apply the recommendations. In the Visual Studio 2019 for Mac release, we’ll also dramatically reduce the time it takes you to connect to your source code and begin working with it in the product, by introducing a streamlined “open from version control” dialog with a brand-new Git-focused workflow.
.NET Core and ASP.NET Core support
In future updates to Visual Studio 2017 for Mac, we will add support for .NET Core 2.2. We will add the ability to publish ASP.NET Core projects to a folder. We will also add support for Azure Functions 2.0, as well as update the New Functions Project dialog to support updating to the latest version of Azure Functions tooling and templates. In Visual Studio 2019 for Mac, we will add support for .NET Core 3.0 when it becomes available in 2019. We will add more ASP.NET Core templates and template options to Visual Studio for Mac and improve the Azure publishing options. Finally, building upon the code editor changes described above, we will improve all our language services supporting ASP.NET Core development including Razor, JavaScript and TypeScript.
Xamarin support
In addition to continuing to make improvements to the Xamarin platform itself, we will focus on improving Android build performance and improving the reliability of deploying iOS and Android apps. We will make it easy to acquire the Android emulators from within the Visual Studio for Mac IDE. Finally, we aim to make further improvements in the Xamarin.Forms Previewer and the Xamarin.Android Designer as well as the XAML language service for Xamarin Forms.
Unity support
We continue to invest in improving the experience of game developers using Unity to write and debug cross platform games as well as 2D and 3D content using Visual Studio for Mac. Unity now supports a .NET 4.7 and .NET Standard 2.0 profile, and we’re making sure that Visual Studio for Mac works out of the box to support those scenarios. Unity 2018.3 ships with Roslyn, the same C# compiler that is used with Visual Studio for Mac, and we’re enabling this for your IDE. In addition to this, we’ll be bringing our fine-tuned Unity debugger from the Visual Studio Tools for Unity to Visual Studio for Mac for a more reliable and faster Unity debugging experience.
Help us shape Visual Studio 2019 for Mac!
By supporting installation of both versions of the product side-by-side, we’ll make it easy for you to try out the Visual Studio 2019 for Mac preview releases while we are still also working on the stable Visual Studio 2017 for Mac releases in parallel.
We don’t have preview bits to share with you just yet, but we wanted to share our plans early so you can help us shape the product with your feedback that you can share through our Developer Community website. We will update our roadmap for Visual Studio for Mac once a quarter to reflect any significant changes. We will also post an update to our roadmap for Visual Studio soon.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |