You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For scaffolding there are two high level scenarios.
Scaffolding from the command line
Scaffolding in Visual Studio
When we started scaffolding our goal was to create a command line scaffolding experience and then build the VS experience on top of that.
After working on the command line scaffolding experience, we realized that we need to take a step back to ensure that we have the right set of features there. At the same time many users are used to, and expect, a scaffolding experience in Visual Studio.
Our current plan is to shelve the command line support and focus on the in Visual Studio experience. At a later time we will revisit the command line scaffolding experience, and when we do we will update the in Visual Studio support to call those new command line scaffolders. You can find a click through of the experience we are targeting at https://github.com/aspnet/Tooling/blob/master/specs/vs-scaffolding.pptx.
With that said, the Visual Studio support that we are currently working on building will use the gen package to execute scaffolding. The gen command won't be included in the templates. You can add the command to projects and invoke it from the command line, but that scenario won't be formally supported until we revisit command line scaffolding later.
For discussion please use dotnet/Scaffolding#135. I'm locking this thread as we normally do in this repo.
FYI this announcement has no impact on the Yeoman asp.net generator, that project continues with the team still being committed to releasing the same day as asp.net runtime updates.
The text was updated successfully, but these errors were encountered:
For scaffolding there are two high level scenarios.
When we started scaffolding our goal was to create a command line scaffolding experience and then build the VS experience on top of that.
After working on the command line scaffolding experience, we realized that we need to take a step back to ensure that we have the right set of features there. At the same time many users are used to, and expect, a scaffolding experience in Visual Studio.
Our current plan is to shelve the command line support and focus on the in Visual Studio experience. At a later time we will revisit the command line scaffolding experience, and when we do we will update the in Visual Studio support to call those new command line scaffolders. You can find a click through of the experience we are targeting at https://github.com/aspnet/Tooling/blob/master/specs/vs-scaffolding.pptx.
With that said, the Visual Studio support that we are currently working on building will use the gen package to execute scaffolding. The gen command won't be included in the templates. You can add the command to projects and invoke it from the command line, but that scenario won't be formally supported until we revisit command line scaffolding later.
For discussion please use dotnet/Scaffolding#135. I'm locking this thread as we normally do in this repo.
FYI this announcement has no impact on the Yeoman asp.net generator, that project continues with the team still being committed to releasing the same day as asp.net runtime updates.
The text was updated successfully, but these errors were encountered: