projectTemplate | project template | Frontend Framework library

So I managed to solve this for my kind of problem. Not saying this is the way of handling expressions with collection properties, but question is specific, and so is the answer:)

The solution was to

• stringify the expression
• tokenize it
• remove noise
• evaluate parts by getting PropertyInfo by Reflection
• keep track of the current type within the expression tree to get correct results

That allows me to have a nice fluent API for strong typed generation of query strings, as visible below.

Usage

Use some structure like:

Just to clarify, this isn't .NET checking for updates to .NET itself, it's checking for updates to the templates. Having stale templates could have a security implication if a template generates code that's vulnerable.

But your concern stands: it's making network connections to machines not under your control and sending data that you might consider private.

I am looking at the source code that implements this check and there doesn't appear to be a way to configure this at this time.

The error message is printed by TemplateInvocationAndAcquisitionCoordination.DisplayUpdateMessage. Neither that file, nor the actual checker in TemplateUpdateChecker seem to have a way to configure this check.

I think you should file a bug against dotnet/templating repo requesting this.

You didn't include the entire directory address of where you checked, so I'll assume you haven't looked in the following locations from the docs. Check these directories, they should contain all the templates installed. I just checked mine, all there.

%ProgramFiles(x86)%\Microsoft Visual Studio\2019\\Common7\IDE\ProjectTemplates\\

%ProgramFiles(x86)%\Microsoft Visual Studio\2019\\Common7\IDE\ItemTemplates\\

NOTE: These are default installation locations! If you installed to a custom path, different drive or if you changed the template location yourself, then obviously they won't be there. If you still can't find them, go into VS and check Tools > Options > Projects and Solutions > Locations and see what it's set to.

1. With react-router-dom you only want to have 1 top level Router that wraps around your routes. Your Links would also have to come at some point in the child tree of that 1 router. The outer Router holds the context of your current route and causes state updates which is how your different routes come in to effect. Because you are wrapping every single Link with it's own Router, when you click on one of those Links, the Router wrapping them is the only one getting updated which doesn't have any child routes to update/show. If you get rid of these wrapping Routers from your Links and just keep the top level one around your Routes, this should fix the issues you are running in to.

2. Change let projectRoutePlaceholder = `${ele.type}/project${this.props.index} to let projectRoutePlaceholder = `/${ele.type}/project${this.props.index} so that it has a leading slash at the beginning. If you don't put a leading slash, then react-router-dom will assume you want to append the url to the end of your current route which will cause the concatenation issue you're running in to. By adding a leading slash, you are telling react-router-dom to go directly to the route rather than append it.

Oh, It took me 2 days to find out how!

https://docs.microsoft.com/en-us/aspnet/core/security/authentication/scaffold-identity?view=aspnetcore-3.1&tabs=netcore-cli

In short - you need to run something like :

Had to upgrade from 5.8.0.6 to most recent version of TDS Hedgehog connector (6.0.0.8) to get this working. When in doubt, do an update.

[update - note that this post is now over 2 years old, and the tooling appears to have gotten much better] The best I seem to come up with is to look in

C:\Users\BozoJoe\.templateengine\dotnetcli\v2.1.104\packages

which has the nupkgs with the version numbers in the file names (as well as the nupkg zips)

Do Visual Studio templates support the new .csproj format? And if so, how can I have it copy files regardless of their presence in the .csproj file?

In fact, VS does not support creating project template for the new sdk format projects at present.

Actually, VS2019 only has the Net Framework project template which works for creating old sdk format projects. And if you simply modify the xxxx.csproj file in such project into the new sdk format like what you did in your situation, but the framework of the template project itself is still net framework(simply migrating the old sdk format to the new sdk format still has various compatibility issues), as a result, the final template still works for net framework projects rather than net core/net standard projects.

As a suggestion,

I suggest you could create a new sdk format project, make some requirements changes as you want and then use VS UI option Export Project Template to export such new sdk format projects and I think this will works well.

In addition, if you still want to create the project template which works for new sdk format projects, we recommend you could post a feature request in our User Voice forum(DC)----suggest a feature to share your idea and the team will seriously consider your idea and give you a satisfactory reply.