No definitive timeline, but I want to get this done for the 2.4 release. I don't usually bother with releasing stuff for unfinished products (VS for Mac/MD 7), but it might be easy to support it since it doesn't appear to be many api breakages between 6 and 7. If you'd like to help out, I can really use it. All the source is. They need to be loaded up in the newer versions of VS and XS with the appropriate extension/addin authoring plugins installed, and tested. There are some other outstanding items regarding the addins that need looking at too: • - conditionally support MonoMac, or possibly remove it altogether since Xamarin.Mac is now open source. • - conditionally support Xamarin.Mac, so it only loads the appropriate stuff when it is installed. • - add templates for xaml-based form and dialog to XS. • - Fix crashing with VS preview window, which has to do with how the appdomain is setup. I have a local branch with an attempt at fixing it, but I have yet to figure out why it does not kill the appdomain properly when reloading the preview. Thanks, but I required it for the classic Visual Studio 2017 desktop application on Windows. Actually, I could build the.vsix for it now (using assemblies in my VSSDK directory rather than NuGet packages, don't really understand what's the difference but eh), but it can't really create projects, not being able to find the Eto.Forms NuGet packages somehow (including the available 2.3.0 one instead of the 2.4.0-alpha package when changing it to that). But at least the templates and designer work, the latter quite slow but good enough. I'm trying to use the new addin with VS for Mac but I'm a bit confused: I can build Eto dll(s) from Visual Studio for Mac Eto src Eto.sln, and it works (updated the develop branch to commit (1st Feb 2018, 20:19) I can build the add-in from Eto build build-addin.sh, a Eto.Addin.XamarinStudio_2.3.0.6.mpack gets created but the overall build fails. Only the Eto.Forms.Templates.2.4.0-alpha.nupkg gets created in the Eto artifacts nuget Release. However the newly created addin installs successfully and I can create a new Eto project, but when I build it nuget complains with the message 'Restore failed for 'Eto.Platform.Mac64 (>= 2.4.0-alpha)'. Should I expect to have it in Eto artifacts nuget Release? If instead of using nuget I directly add to my solution Eto src Eto.csproj and Eto src Eto.Mac Eto.Mac.csproj (or Eto src Eto.Mac Eto.Mac64.csproj) and reference them where needed I can compile fine but when I run my application it crashes with the exception 'Platform type Eto.MacPlatform, Eto.Mac64 was loaded but is not valid in the current context. ![]() Extension for Visual Studio - Multilingual App Toolkit helps you localize your Windows and Xamarin Apps by providing file management, translation services, translation editor, and build integration. Build rich, enterprise-class, line of business Windows desktop applications using WPF,. Converting avi to mp4 for mac. NET and Visual Studio. Download Visual Studio IDE for free today. Visual Studio Community 2017. Free, fully-featured IDE for students, open-source and individual developers. Visual Studio Enterprise for Mac. Mac platforms require to be in an.app bundle to run.' What am I doing wrong? Hey, to build the nuget packages you need to use the./build.sh (on mac), and build.cmd (on windows). I usually do this via a share to a windows VM so they are both run on the same copy of the source files. This ensures the XamMac and Wpf nupkg files are created, which are mandatory for the addin templates. You need the nuget packages to run the Mac/Mac64 platform as it sets up the proper.app bundle build, and tells VS on Mac to run the.app bundle instead of the.exe directly. This stuff is all in build/MacTemplate. ![]() Thanks Curtis, running./build.sh I can now successfully build all the nuget packages and the initial Eto project created by the addin runs fine:) However I'm not yet able to debug the Eto code, if I reference the Eto projects instead of using the nuget packages I still get the exception: 'Platform type Eto.MacPlatform, Eto.Mac64 was loaded but is not valid in the current context. Mac platforms require to be in an.app bundle to run.' The only difference that I found from the Eto test application (that I thought relevant) is a: True but even adding it nothing changes:( I think I did not understand what you meant when you told me that everything is in the build/MacTemplate. How do I use it? Thanks for your patience;).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |