Currently, in my project, there is a folder named "Properties" which contains one item, Settings.settings, which contains one subitem, Settings. if i try to do that here by creating a folder named config and moving App.
However, I tend to like to keep all my config files in one location under a config directory.
Is there a way to get the 'tool Settings.json' file to work for both project types?
You do have it under your VS installation dir plus relative path Common7\IDE\Extensions\Microsoft\Web Tools\Project System\tool
A Case Study/Guide Our corporate website was built primarily using VB. NET framework releases, and we are happy with the power and readability of VB.
Dotnet Core projects can have both of them as targets. NET Core web projects, for example: Home Controller. This was working in 2015, is this functionality going to be added back into 2017? Would love to help get this fixed before 2017.3's RTM, as this is causing problems for us. The key is that, because all files are included by default, you're updating an existing compilation reference, not creating a new one. in this case I append I'm seeing nesting not working in VS2017 for . So if I add support for appsetttings to my app and then add appsettings.it doesn't properly nest. Really disappointed in the VS team for removing functionality which worked in VS2015.
Did you actually mean two different project system types: Dot Net Core (new project system) vs full . is automatically being nested under Home Doesn't seem to be working in non-web projects however, which was previously working in 2015. We are using EF Core and running "dotnet ef migrations". There are many cases outside of web projects where the ability to nest files without explicitly declaring each one is very beneficial.
But I discovered that there’s a context menu item called “Run Custom Tool”.
The most obvious choice is to select “Run Custom Tool” from the EDMX file, but that doesn’t do anything: If you F4 the corresponding T4 file you can see that the custom tool associated with the T4 file is: Text Templating File Generator So, I selected “Run Custom Tool” from the T4 context menu: And that generated the file: But I still didn’t have the Foo class in my object model: So I selected the “Run Custom Tool” on the “Conf Speakers. I will ping the product team to see if they can run the custom tool on the EDMX file when it is saved and recursively run on all the tt files associated with that EDMX parent.