Skip to content

Razor Components startup experience #4054

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.

Sign up for GitHub

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

Jump to bottom
Closed
danroth27 opened this issue Nov 16, 2018 · 3 comments
Closed

Razor Components startup experience #4054

danroth27 opened this issue Nov 16, 2018 · 3 comments
Assignees
@javiercn
Labels
area-blazor Includes: Blazor, Razor Components Done This issue has been fixed enhancement This issue represents an ask for new feature or an enhancement to an existing one
Milestone
3.0.0-preview4

Comments

@danroth27
Copy link
Member

No description provided.

@danroth27 danroth27 added enhancement This issue represents an ask for new feature or an enhancement to an existing one area-mvc Includes: MVC, Actions and Controllers, Localization, CORS, most templates labels Nov 16, 2018
@danroth27 danroth27 added this to the 3.0.0-preview2 milestone Nov 16, 2018
@SteveSandersonMS
Copy link
Member

SteveSandersonMS commented Dec 18, 2018 •
edited
Loading

I'm not sure there's anything to change about this in the preview 2 timeframe. So I question whether the PRI:0 label and "preview 2" milestone is correct. Reasoning:

  • For preview 2, Razor Components apps will still be required to be two projects. @rynowak's work on the Razor compiler will eventually make it possible to do it all in one project, but not for preview 2 (correct, Ryan?).
  • If we're having two projects, we might as well retain the benefit of being able to easily switch to client-side execution. Supporting this necessitates keeping the same Program.cs and Startup.cs in the app project.
  • If we're keeping Program.cs and Startup.cs in the app project, what is there to change?

So, I suspect there is work in this area eventually to enable a one-project system, but only after preview 2. So @danroth27, should we remove the pri-0 label and "preview 2" milestone, or is there any other specific work you think we should do on this for preview 2?

@SteveSandersonMS SteveSandersonMS added the area-blazor Includes: Blazor, Razor Components label Feb 6, 2019
@rynowak
Copy link
Member

rynowak commented Feb 21, 2019

Moves this to working, because I think #7770 has enough cleanup to call this "done". If we have other things we want to do after preview3 we can track them with separate issues.

@javiercn javiercn added Done This issue has been fixed and removed 2 - Working labels Feb 22, 2019
@rynowak
Copy link
Member

rynowak commented Feb 22, 2019

I just want to say that the end result of this is D O P E

@rynowak rynowak mentioned this issue Mar 4, 2019
Closed
56 tasks
@mkArtakMSFT mkArtakMSFT removed area-mvc Includes: MVC, Actions and Controllers, Localization, CORS, most templates labels May 9, 2019
@ghost ghost locked as resolved and limited conversation to collaborators Dec 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@javiercn javiercn

Labels
area-blazor Includes: Blazor, Razor Components Done This issue has been fixed enhancement This issue represents an ask for new feature or an enhancement to an existing one
Projects
None yet
Milestone
3.0.0-preview4
Development

No branches or pull requests
5 participants
@SteveSandersonMS @rynowak @danroth27 @javiercn @mkArtakMSFT