NET Standard 2.1 project - like Task.IsCompletedSuccessfully), I can copy files and make custom shivs that will get me through the transition period.Īnother place where linked files can come in handy is if we create shared libraries (or NuGet packages) that will be used in different environments. NET Framework project.įor anything that doesn't match up (for example, I might be using additional APIs in the. NET Standard 2.1 project) that I can use today with the. NET Standard 2.0 project (that links to the files in the. NET Standard 2.1 class library with the intention that this will be the library referenced by the. NET Core 3.0, I may want to set up some interim projects to help with the transition. NET Framework 4.7.2 project, I will not be able to use a. NET Standard 2.1.īut most people have a lot of applications that are. NET Core 3.0 is still coming (it will be released on September). We are in a bit of a transition period with. This example is a bit contrived, so let's explore something a little more realistic. In this case, we may not be able to reference one assembly from another. And this is what I do when I can.īut in this scenario, we have 3 different class libraries all with different targets. So why would we want to do this? Usually if we want to use an existing class, we would reference that assembly and use it directly. So if we make changes in one location, it is reflected in both. You can also use Ctrl + /, which puts the > in place for you automatically.What we have done is create a reference in one project to a file in a different project. (If you change your mind about addins, SonicFileFinder is for this very purpose, and free.) You need the Find box in the toolbar for this to work. It then autocompletes the filename for you. Not a single keystroke, but yes: Ctrl+D > o f filename (so that's five keystrokes before you start typing the filename). For more keys and for Visual Studio 2012 to 2015 take a look at this. We are writing f to make VS search only on files.Press these keys to open "Go to" popup:.Now pressing Ctrl + Shift + T and typing file name works!įor Visual Studio 2019 now it's possible to do similar search via Ctrl + Q.īut it works slightly sloppy since it shows VS-related stuff as well. The accepted solution doesn't work in newer versions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |