Install New Templates In Visual Studio For Mac 2017

At the time of writing this post, default ASP.NET Core SPA templates allow you to create Angular 5/6 based app with Visual Studio without installing any third-party extensions or templates. This post talks about how to create an Angular 7 App with Visual Studio 2017. Getting up and running with Visual Studio Code is quick and easy. It is a small download so you can install in a matter of minutes and give VS Code a try. VS Code is lightweight and should run on most available hardware and platform versions. You can review the System Requirements to check if your.

Join GitHub today

GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.

Sign up 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.

Install New Templates In Visual Studio For Mac 2017

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

Comments

commented Nov 23, 2016
edited by mlorbetske

I'm not seeing the .NET Core folder for Core templates when trying to create New Solution in Visual Studio 2017 Community RC.

I can confirm I installed the .NET Core and Docker workload (Preview) in VS installer.

commented Nov 23, 2016

On my system (VS 2015 and VS 2017 installed) I could solve this by reinstalling .NET Core VS 2015 tooling.

commented Nov 23, 2016
edited

Why would I need those? It's not mentioned here https://www.microsoft.com/net/core#windowsvs2017

I'll wait for a confirmation from someone at MS before installing 2015 tooling.

commented Nov 28, 2016

I've reformatted the VM I use for testing and installed the VS 2017 RC Professional version and the templates are there.

I guess it's an issue with Community version.

commented Dec 3, 2016
edited

I just installed 2017 RC Professional, selected Core and don't see any Core templates. In fact the only C# template of any type I have is 'Shared Project'

I uninstalled VS 2017 RC Professional and installed 2017 RC Community and same story. How do I get templates? Not just Core ones, ASP. net ones, Console app ones? All I seem to have is C++ ones which are of no use to me.

commented Dec 5, 2016

I'm looking for the Middleware template in Add New Item and it's nowhere to be found (in VS2017 RC). I'm guessing this is related to this issue. It doesn't make sense to me to install VS2015 tooling to add support to VS2017... Can someone confirm that's necessary?

commented Dec 27, 2016

@joeloff any ideas?

commented Dec 27, 2016

TFS Bug#362764

commented Jan 2, 2017

Just installed VS 2017 Community and no templates. Not even the standard Web application templates, I was hoping to see the templates for .NET Core.

commented Jan 24, 2017

Install New Template In Visual Studio For Mac 2017

Are you still experiencing this issue with the latest update to VS 2017 RC? You can download it from the following location:

If it does, could you please go to http://aka.ms/vscollect and send us the setup logs? Thanks!

commented Jan 24, 2017

Logs would be useful. Nothing related to .NET Core is conditioned on the SKU type, but it's possible that something else in the setup engine failed and decided not to install certain packages and the logs will contain entries to show the decisions the engine made for all the packages.

commented Jan 25, 2017

I'd definitely like to see the installation logs @brgrz

I just did a clean install of the public RC, only selected the .NET Core / Docker preview workload and I'm seeing all the .NET Core templates in VS after install Community 2017 RC

commented Jan 27, 2017

I'll try this again this weekend with the new RC bits that were published today and will let you know how it goes.

commented Feb 6, 2017

This seems to be fixed in the latest RC bits.

commented Jul 12, 2017

I had to install the SDK from this link and restart my pc, only modifing the VS2017 P3 installation didn't worked for me.

commented Jul 12, 2017

@rodrigorf was this for the 2.0 templates? The 2.0 templates don't currently ship as part of VS and you have to install the SDK to obtain then.

commented Jul 12, 2017

Hahaha, that's a good one, I lost track of .net core versioning.

commented Jul 12, 2017

Exactly. I get it, some posts on the internet made me think the 2.0 templates would come together with Preview 3. Thanks @joeloff

commented Jul 12, 2017

@rodrigorf you're welcome. Just curious, were these posts from the official dotnet site or other sources? If it's from the Microsoft sites, we should definitely try to address any ambiguity.

FYI @leecow

commented Jul 12, 2017

@joeloff it was not an official site actually, its a independent blog(a famous one in brazil), the line that made me commit the error was like this: 'To build applications using ASP.NET Core 2.0, you need to install Visual Studio 2017 Preview 3.', but never mentioned any manual SDK install. Its not wrong but incomplete. My bad!

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Visual Studio 2017 15.8 Preview 3 is now available and it includes several improvements to the CMake tools. In addition to a few fixes we have simplified the way you can configure your CMakeSettings.json file by adding configuration templates.

If you are new to CMake in Visual Studio, check out how to get started.

Configuration Templates for CMake

If you have created a CMakeSettings.json file to customize your project’s settings in the past you might know that that file could be a little daunting. With both the Desktop and Linux workloads installed, the default CMakeSettings.json template was over 100 lines long. We received feedback from the community that this file was difficult to unpack and understand, so we have simplified the way we populate the default CMakeSettings.json file. We have also provided a way to access and edit this configuration file directly from the configuration selector.

Getting Started

When you open a CMake folder for the first time, we now implicitly create just one debug configuration that matches the current operating system. This way, you are still able to get up and running to target the local machine without needing to create a CMakeSettings.json file at all. However, once you do want to add or customize the CMake configuration list, it is easier than ever to do so:

Clicking “Manage Configurations…” in the configuration selection dropdown (right of the F5 button) will ask you to select a template that best fits how you want to debug your project. Visual Studio will add the selected template to a newly created CMakeSettings.json in the root CMakeLists file’s folder.

This has all the configurations we supported before plus a few new ones for targeting MinGW and ARM IoT devices. Once you select a template, it will be added to your CMakeSettings.json file. If we take “x86-Debug” for example, we see that it results in a very compact CMakeSettings.json:

At only 17 lines, this is quite a bit more manageable than this file has been in the past.

Adding New Configurations

Once you create this file, the “Manage Configurations…” button in the configuration selection dropdown will take you back to the CMakeSettings.json file. However, that doesn’t mean you can’t add more templates to it. To add new templates after creating the file just right click anywhere on the editor and select Add Configuration:

Alternatively, you can right click on the file itself in the Solution Explorer:

The newly selected template will be appended to the end of your configuration file.

Custom Configuration Templates (Experimental)

How to install templates in visual studio 2017

In addition to the built-in configuration templates, we have added an experimental way for you to create your own templates as well. Under Tools > Options > CMake there is now a “CMakeSettings.json Template Directory” entry:

You can point this at a directory with one or more JSON files containing custom templates for CMake. These files can have any name, and essentially have the same format as a standard CMakeSettings.json file. The array of “configurations” will be treated as templates and will appear in the template selector. To set their description in the template sector just add a “description” field to the configuration’s JSON.

We would love to hear how you use this and if it works well for you. Your feedback will help us shape this feature in future versions of Visual Studio.

Community Reported Issues and Other Improvements

We have fixed quite a few customer reported issues in the latest Visual Studio Preview, including several related to our IDE integration with CTest:

In addition to the issues reported by the community, we have also addressed the following customer impacting issues:

  • Fixed long delay when closing some CMake projects
  • Opening a new CMake project without closing a previously opened project no longer locks up the IDE
  • CMake project code scanning no longer waits forever if filters are defined in “.vscodesettings.json”
  • C# CMake projects now default to the Visual Studio generator and F5 starts the managed/mixed debugger (experimental)

Thanks again to everyone who reported these issues!

In addition to the changes to CMakeSettings and configuration, the latest version of the CMake tools also includes improved single file compilation. All errors and warnings now appear in the Error List instead of only the Output Window.

Send Us Feedback

Visual Studio For Mac Tutorial

Your feedback is a critical part of ensuring that we can deliver the best CMake experience. We would love to know how Visual Studio 2017 Preview is working for you. If you have any feedback specific to CMake Tools, please reach out to cmake@microsoft.com. For general issues please Report a Problem.