# Visual Studio 2022 RC for Mac and Elements?
**URL:** https://talk.remobjects.com/t/visual-studio-2022-rc-for-mac-and-elements/26612
**Category:** Fire
**Created:** [May 2, 2022, 5:32am UTC](https://talk.remobjects.com/t/visual-studio-2022-rc-for-mac-and-elements/26612 "2022-05-02T05:32:48Z")
**Posts on this page:** 13
**Page:** 1
### Author:  [@chikega](https://talk.remobjects.com/u/chikega)
#### Post date: [May 2, 2022, 5:32am UTC](https://talk.remobjects.com/t/visual-studio-2022-rc-for-mac-and-elements/26612/1 "2022-05-02T05:32:49Z")
This appears to be rather big news as there will be some semblance of software parity between Win and Mac platforms - the rebranding of MonoDevelop appearing to have been a stop gap solution for the Mac platform. [MS dumps the Mono runtime for .Net 6](https://visualstudiomagazine.com/articles/2022/01/26/vs-mac-preview-5.aspx). Are there any plans to have Fire Elements work within [Visual Studio 2022 for Mac](https://visualstudio.microsoft.com/vs/mac/preview/) as Water has been working with Visual Studio for Windows? Exciting times š¤
---
### Author:  [@mh](https://talk.remobjects.com/u/mh)
#### Post date: [May 2, 2022, 12:06pm UTC](https://talk.remobjects.com/t/visual-studio-2022-rc-for-mac-and-elements/26612/2 "2022-05-02T12:06:16Z")
> [@chikega](#):
>
> Are there any plans to have Fire Elements work within [Visual Studio 2022 for Mac](https://visualstudio.microsoft.com/vs/mac/preview/) as Water has been working with Visual Studio for Windows? Exciting times š¤
Just to clarify on the naming, Fire and Water our _our_ IDEs (for Mac and Windows, respectively), separate from Visual Studio. Elements is the compiler, and it works in Fire, Water, and Visual Studio for Windows.
As for supporting the new Visual Studio for Mac: weāll have to have a look, but id say unless this literally _is_ the same Visual Studio as on Windows, with the same extension APIs, i would say chances are slim that weāll add support for it.
Adding and supporting a new IDE is a lot of effort (and supporting VS/Windows is the largest effort between the three IDEs, and thatās taking into account that we (i) wrote Fire/Water from scratch), so iām hesitant to add new workloads here, especially since i donāt expect demand for this to be huge (as, i think/hope, people are generally pretty happy with Fire). Also, i donāt believe anyone on our current VS team uses/has Macs at all, which adds another burden there.
But that said, if itās āthe sameā VS as VS/Windows, and our existing support for it more or less ājust worksā as is, we migh.
---
### Author:  [@mh](https://talk.remobjects.com/u/mh)
#### Post date: [May 2, 2022, 1:48pm UTC](https://talk.remobjects.com/t/visual-studio-2022-rc-for-mac-and-elements/26612/3 "2022-05-02T13:48:37Z")
Not a good first impression so far ;).
Installer looks nice, VS only seems to know one project template type for some reason (āAzure Functionā), and trying to create it fails with
> Unable to locate the .NET SDK. Check that it is installed and that the version specified in global.json (if any) matches the installed version."
even though .NET 6 is installed _and_ setup for some reason also installed .NET Core 3.0.1, as well.
Opening existing VC# projects works, but the IDE doesnāt;t look.feel _anything_ like VS/Windows (which is good, in general), which makes me think supporting this will _not_ be as simple as using our existing plugins. I think this is still based MonoDevelop, just evolved a lot.
---
### Author:  [@mh](https://talk.remobjects.com/u/mh)
#### Post date: [May 2, 2022, 1:51pm UTC](https://talk.remobjects.com/t/visual-studio-2022-rc-for-mac-and-elements/26612/4 "2022-05-02T13:51:05Z")
> [@mh](#):
>
> Unable to locate the .NET SDK. Check that it is installed and that the version specified in global.json (if any) matches the installed version."
Ah, if anyone cares, in Preferences the SDK location is set to `/Applications/Visual Studio (Preview).app/dotnet`, when it should be `/Applications/Visual Studio (Preview).app/Content/dotnet`. Changing that still doesnāt fix it š
---
### Author:  [@mh](https://talk.remobjects.com/u/mh)
#### Post date: [May 2, 2022, 1:54pm UTC](https://talk.remobjects.com/t/visual-studio-2022-rc-for-mac-and-elements/26612/5 "2022-05-02T13:54:23Z")
It also still seems to be running on Mono. Not that thatās bad; Mono is solid, and Fire still uses that (and will continue to use to for the foreseeable).
---
### Author:  [@chikega](https://talk.remobjects.com/u/chikega)
#### Post date: [May 2, 2022, 2:08pm UTC](https://talk.remobjects.com/t/visual-studio-2022-rc-for-mac-and-elements/26612/6 "2022-05-02T14:08:19Z")
Sorry about using the IDE names vs āElements Compilerā, the names just sound sexier. š Iām just getting a chance to play with VS 2022 for Mac as we speak(or write), my MBP was out of commission for a while, right shift key permanently disabled. But Iād have to agree with you. It feels like a more evolved Monodevelop which is not a bad thing at all. š„ø
---
### Author:  [@chikega](https://talk.remobjects.com/u/chikega)
#### Post date: [May 2, 2022, 2:57pm UTC](https://talk.remobjects.com/t/visual-studio-2022-rc-for-mac-and-elements/26612/7 "2022-05-02T14:57:06Z")
> [@mh](#):
>
> Ah, if anyone cares, in Preferences the SDK location is set to `/Applications/Visual Studio (Preview).app/dotnet`, when it should be `/Applications/Visual Studio (Preview).app/Content/dotnet`. Changing that still doesnāt fix it š
I confirm that I see it in the location you indicated:
But it appears the IDE is directing me here as well:
---
### Author:  [@JohnMoshakis](https://talk.remobjects.com/u/JohnMoshakis)
#### Post date: [May 2, 2022, 3:01pm UTC](https://talk.remobjects.com/t/visual-studio-2022-rc-for-mac-and-elements/26612/8 "2022-05-02T15:01:59Z")
> [@mh](#):
>
> (as, i think/hope, people are generally pretty happy with Fire)
I am, although I would like some support for azure and aws. I would also like to see Fire running using .net core. I wrote some azure and aws functions in Fire. It takes a bit of work but I do have working code. I think for azure it might be a bit more tricky because it appears to be tied into msbuild.
---
### Author:  [@mh](https://talk.remobjects.com/u/mh)
#### Post date: [May 2, 2022, 3:15pm UTC](https://talk.remobjects.com/t/visual-studio-2022-rc-for-mac-and-elements/26612/9 "2022-05-02T15:15:19Z")
> [@chikega](#):
>
> It feels like a more evolved Monodevelop which is not a bad thing at all. š„ø
Agreed. it does feel more Mac like than id expected, which is good for VS users. Its just bad news in terms of us erasing our integration.
I noticed one odd thing: after installing VS/Mac, I could no longer open solutions in Fire, the OS claiming Fire didnāt know how to open the āVisual Studio project structureā format.ā After deleting VS again itās fine.
Somehow VS seems to mess with how it registers the file extension that breaks other apps; so far I couldnāt figure out why, or what I could do about it. Did you notice that too, or is all still fine for you?
> [@chikega](#):
>
> But it appears the IDE is directing me here as well:
>
> 
ah it wants the exe, not the folder, so I guess is should have put in `/Applications/Visual Studio (Preview).app/Content/dotnet/dotnet` . š
I do have the system-wide install too of course, odd it didnāt use that one here. Ah wellā¦
> [@JohnMoshakis](#):
>
> I am, although I would like some support for azure and aws.
Iād love to hear more on what youād like supported here, in a separate thread. I assume mainly publishing options?
> [@JohnMoshakis](#):
>
> I would also like to see Fire running using .net core.
What benefit would you see from that, aside from maybe marginal performance improvements if .NET Core 6/7 runs faster than Mono (and thatād an _if_, Iām not seeing many performance issues from the managed code)?
> [@JohnMoshakis](#):
>
> I wrote some azure and aws functions in Fire. It takes a bit of work but I do have working code. I think for azure it might be a bit more tricky because it appears to be tied into msbuild.
Cool. lets have a look at that in a fresh thread. šš¼
---
### Author:  [@chikega](https://talk.remobjects.com/u/chikega)
#### Post date: [May 2, 2022, 3:33pm UTC](https://talk.remobjects.com/t/visual-studio-2022-rc-for-mac-and-elements/26612/10 "2022-05-02T15:33:09Z")
> [@mh](#):
>
> ah it wants the exe, not the folder, so I guess is should have put in `/Applications/Visual Studio (Preview).app/Content/dotnet/dotnet` . š
š
Just to wrap this thread up, I did a [quick āHello Worldā dotnet6 test.](https://d.pr/v/8DWqk6) Appears to be working as expected. And no I donāt type that slowly - Iām having to use the left shift key for everything. š
---
### Author:  [@mh](https://talk.remobjects.com/u/mh)
#### Post date: [May 2, 2022, 3:59pm UTC](https://talk.remobjects.com/t/visual-studio-2022-rc-for-mac-and-elements/26612/11 "2022-05-02T15:59:45Z")
> [@chikega](#):
>
> Iām having to use the left shift key for everything. š
Lol. I donāt think Iāve ever once used the _right_ shift key.
---
### Author:  [@JohnMoshakis](https://talk.remobjects.com/u/JohnMoshakis)
#### Post date: [May 2, 2022, 11:26pm UTC](https://talk.remobjects.com/t/visual-studio-2022-rc-for-mac-and-elements/26612/12 "2022-05-02T23:26:20Z")
> [@mh](#):
>
> What benefit would you see from that, aside from maybe marginal performance improvements if .NET Core 6/7 runs faster than Mono (and thatād an _if_, Iām not seeing many performance issues from the managed code)?
I donāt know of any technical reason, it would just be nice to that its using the latest .net rather than something that appears to be no longer supported.
---
### Author:  [@mh](https://talk.remobjects.com/u/mh)
#### Post date: [May 3, 2022, 12:01pm UTC](https://talk.remobjects.com/t/visual-studio-2022-rc-for-mac-and-elements/26612/13 "2022-05-03T12:01:39Z")
> [@JohnMoshakis](#):
>
> I donāt know of any technical reason, it would just be nice
Yeah, thats abut a month or two of work for āwould just be niceā ;). Fire deeply depends on [Marzipan](https://github.com/remobjects/Marzipan) for Mono/Native interop. Weāll basically have to reinvent that from scratch for .NET Core, and that will be a major undertakingā¦
Soā¦ eventually, sure. any time soon? probably not.