Age | Commit message (Collapse) | Author |
|
VS Windows shows all item templates as "Razor ...", without any mention
to MVC, which causes confusion, so change to match the descriptions.
Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1016547
|
|
Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1021958
|
|
Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1012759
|
|
Add period to the template description.
|
|
Add period to the template description.
|
|
Add period to the template description.
|
|
Add period to the template description.
|
|
Add period to the template description.
|
|
Add period to the template description.
|
|
Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/944132
|
|
|
|
|
|
Since Razor Class libraries are libraries, they target .NET Standard,
so the condition for those item templates need to be extended
to check for "DotNetCoreRazor" project capability.
|
|
|
|
|
|
|
|
Adding a new .cshtml file from a file template to an ASP.NET Core
project would modify the project file (.csproj) when it should not be
modified. The problem was the files were added as None items whilst
.cshtml are Content items. The project file would contain the
following after adding a new cshtml file from a template:
<ItemGroup>
<Content Remove="Views\Index.cshtml" />
</ItemGroup>
<ItemGroup>
<None Include="Views\Index.cshtml" />
</ItemGroup>
Another problem was that the Razor Page with view model file
template specifies a DependentUpon property so this is added to the
project file and the .cshtml and .cs files are nested where as
the other .cshtml and .cs files created with the initial ASP.NET
Core project template are not nested. The project file would include
the following:
<ItemGroup>
<Compile Update="Views\Index.cshtml.cs">
<DependentUpon>Index.cshtml</DependentUpon>
</Compile>
</ItemGroup>
Note that the .NET Core SDK does not indicate that .cshtml and .cs
files are dependent on each other so they are not currently nested
in the Solution window. New .cshtml files created from these updated
file templates will not be nested in Solution window.
Fixes VSTS #585219 Only new Razor Pages are nested
|
|
|