Is there any chance Visual D will be ported to Visual Studio for mac?

Is the extension API for the mac version even remotely similar to what's on the windows side?

Visual Studio for mac is basically a renamed copy of Xamarin Studio, but massive breaking changes were made to XS's extension API recently (which is why Mono-D no longer works) and I'm wondering.. were those changes meant to align the API with whatever is done for windows?

Thanks

On 05.08.2017 18:28, bitwise wrote:
> Is there any chance Visual D will be ported to Visual Studio for mac?
> 
> Is the extension API for the mac version even remotely similar to what's on the windows side?
> 
> Visual Studio for mac is basically a renamed copy of Xamarin Studio, but massive breaking changes were made to XS's extension API recently (which is why Mono-D no longer works) and I'm wondering.. were those changes meant to align the API with whatever is done for windows?
> 
> Thanks

As you noticed, Visual Studio for mac is basically Xamarin Studio, so the API is very different to VS for Windows.

I tried VS for mac once, and AFAIR it even installed Mono-D, but some referenced assemblies have changed. I suspect it wouldn't be too much work to adapt Mono-D, but that would be unlikely me doing it ;-)

On Sunday, 6 August 2017 at 11:37:00 UTC, Rainer Schuetze wrote:
>
[...]
> I tried VS for mac once, and AFAIR it even installed Mono-D, but some referenced assemblies have changed. I suspect it wouldn't be too much work to adapt Mono-D, but that would be unlikely me doing it ;-)

Unfortunately, it's worse than just updating the assemblies. I tried to get Mono-D working, but they've changed the way parsers work, and I think there were changes in the way a document is abstracted as well - meaning entire classes seem to have been added and removed. I didn't have much time for it, so that's about as far as I got.

Thanks anyways though - Nothing but positive experiences with Visual D so far =D

On 2017-08-06 23:39, bitwise wrote:

> Unfortunately, it's worse than just updating the assemblies. I tried to
> get Mono-D working, but they've changed the way parsers work, and I
> think there were changes in the way a document is abstracted as well -
> meaning entire classes seem to have been added and removed. I didn't
> have much time for it, so that's about as far as I got.

In a video from the build conference they mentioned that the editor component is now the same as on Windows.

-- 
/Jacob Carlborg

On Monday, 7 August 2017 at 10:39:23 UTC, Jacob Carlborg wrote:
> On 2017-08-06 23:39, bitwise wrote:
>
>> Unfortunately, it's worse than just updating the assemblies. I tried to
>> get Mono-D working, but they've changed the way parsers work, and I
>> think there were changes in the way a document is abstracted as well -
>> meaning entire classes seem to have been added and removed. I didn't
>> have much time for it, so that's about as far as I got.
>
> In a video from the build conference they mentioned that the editor component is now the same as on Windows.

Do you have a link to the video?

At first glance, there doesn't seem to be any discernible middle ground between the two. I went looking for "extension points" and found these:

https://docs.microsoft.com/en-us/visualstudio/mac/extending-visual-studio-mac-walkthrough
https://docs.microsoft.com/en-us/visualstudio/extensibility/language-service-and-editor-extension-points

Building an abstraction-layer/adapter between those two doesn't seem like a weekend project =x

On 2017-08-08 21:04, bitwise wrote:

> Do you have a link to the video?

https://channel9.msdn.com/Events/Build/2017/B8095 starting from 2:20.

-- 
/Jacob Carlborg

On Tuesday, 8 August 2017 at 20:40:32 UTC, Jacob Carlborg wrote:
> On 2017-08-08 21:04, bitwise wrote:
>
>> Do you have a link to the video?
>
> https://channel9.msdn.com/Events/Build/2017/B8095 starting from 2:20.

Awesome, thanks for the link.
Busy day today, will have a look tomorrow.