-
Notifications
You must be signed in to change notification settings - Fork 10.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Razor Components support for VS4Mac #5490
Comments
@rynowak Edit: I'm hijacking Dan's cool comment to track the progress of this because it's under way! TODO:
|
We're going to take a look at this and see how far we can get with the latest VS for Mac preview. |
Didn't make it for 0.2.0. Moving to next milestone |
Any help required with this or are we waiting on the Visual Studio for Mac team? |
No help required at this time. We're still working with the VS for Mac folks on this. No ETA at this time. |
This does seem to work in Visual Code... |
sorry @stefandevo, just to be sure, are you on MacOS? |
@hcientist yes, running the FlightFinder |
C# 7.3 for Visual Studio Mac will be supported soon : |
Looks like C# 7.3 on macOS is only partially implemented. Still not supported by the csc command. See mono/mono#9796 |
In the latest version of visual for Mac (preview) its now possible to run and build blazor apps! |
@vertonghenb It's certainly something we want to do. It's just a matter of time and resources. |
@danroth27 I know there are more important features out there, I would just like to know the roadmap and where we can place this issue in it. Not so long ago there was a demo if Razor tooling in VS Code on live.asp.net, do we intent to initially support vs code or is the road to support VS for Mac shorter? Can the community help out to tackle this? |
That's completely reasonable. The priority backlog is a bit stale right now. I'll make sure it gets updated.
We intend to support both. We had investigated supporting VS for Mac a while back and hit some blocking issues with the Razor tooling that we need to revisit. Currently we're investigating what it would take to get basic Razor tooling support in VSCode. While the foundational piece we need in VS for Mac are further along, we think there's probably more value in VSCode tooling as that's currently the tool of choice for lots of web developers. |
Just curious if there's any new ETA for .razor Intellisense support in VS4Mac, with the advent of .NET Core 3.0 and Blazor in official preview now? Thanks @danroth27 and team. |
@leebenson We're hoping to deliver Blazor tooling support for VS4Mac in the 8.4 release of VS4Mac. /cc @sayedihashimi |
Yes that is correct, we (Visual Studio for Mac) are working on Blazor server side support currently and hoping to get it in the 8.4 release as Dan mentioned above. |
@sayedihashimi Any info yet on when the 8.4 preview will be out? |
@mrlife I don't have any specific dates to share at this time, but my guess is that it should be before the end of the year [no promises as usual :)] |
We're closing this as there is no action for us to take here. The support is already in preview in VS4Mac 8.4. |
For those interested we added support for Razor Components & Blazor in 8.4 which was recently released https://devblogs.microsoft.com/visualstudio/visual-studio-2019-for-mac-version-8-4-is-now-available/. |
I think that means I need an mpack instead of a vsix?
The text was updated successfully, but these errors were encountered: