You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 17, 2025. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 17, 2025. It is now read-only.
Improve IntelliSense to cover more properties/items/values #15
Hi Sayed,
I tried the Project File Tools: installation It's useful because gives intellisense while typing package names, but I need more tools too, mainly intellisense for the available options, check the correct framework names, and if possible check Conditions in the ItemGroup and PropertyGroup opening tag.
I checked in docs.microsoft.com and I found mainly documentation about migration from project.json to csproj, but not an organic documentation. I think this is not very useful for the ones that are starting to use dotnet core now, but beside this I have a lack of documentation for the options that are enumerable, for example.
For example, I'm having a problem with an asp.net mvc app I'm migrations and that now is using the logic in dotnet core libraries, but I see that logging exceptions not I cannot see the part of the stacktrace that belongs to the dotnet core library: I see the part of the stack trace of the dotnet app, but not the starting part inside the core libraries, though I deployed all the pdb files.
I suppose the problem could be the format of the pdb is portable and the framework is not able to use it, so I'm looking how to set the pdb format: from the documentation I see that the could be the property I need to configure, but in the documentation I find only the value Portable, so I have to search further, and I'm trying to see if setting it at Full solve the problem.
I hope I explained the problem, I would like to avoid this kind of problem.
Thanks,
luca
I don't know very well how is going to work with dotnet standard 2, but another quite problematic part is the configuration of the <PackageTargetFallback> property.
Could be possible to be prompted for the correct moniker when adding a library that needs it, or add it directly?
Activity
lucamorelli commentedon Jun 5, 2017
I don't know very well how is going to work with dotnet standard 2, but another quite problematic part is the configuration of the
<PackageTargetFallback>property.Could be possible to be prompted for the correct moniker when adding a library that needs it, or add it directly?