UWP and External Lib Dependencies












0















I have a solution with several UWP projects that are using "Microsoft.Extensions.DependencyInjection"



I can't see any references in NuGet Package Manager to this extension nor in the project s References.
Using VS, how can I list all these external dependencies that my solution is using for each project inside.










share|improve this question























  • The package does not support UWP. The package installer races a bit too fast to see the error message, but you can see it from the Package Manager Console window when you type "Install-Package Microsoft.Extensions.DependencyInjection -Version 2.1.1"

    – Hans Passant
    Nov 15 '18 at 16:24











  • If I create a new UWP project, I can see the package installed, and I get no errors installing it. The problem is this solution that I have that is using some version of the "Microsoft.Extensions.DependencyInjection" but I can t see it in the Package Manager nor in References, but the application runs fine and is using it for sure. So my problem is that I don't have any information in the solution that shows that reference to the "Microsoft.Extensions.DependencyInjection". I can see in the dll that the version is 2.0.17205.

    – J_PT
    Nov 15 '18 at 17:33











  • The UWP project is targeting Windows 10 Fall Creators update 10.0 build 16299, as min and target versions

    – J_PT
    Nov 15 '18 at 17:35


















0















I have a solution with several UWP projects that are using "Microsoft.Extensions.DependencyInjection"



I can't see any references in NuGet Package Manager to this extension nor in the project s References.
Using VS, how can I list all these external dependencies that my solution is using for each project inside.










share|improve this question























  • The package does not support UWP. The package installer races a bit too fast to see the error message, but you can see it from the Package Manager Console window when you type "Install-Package Microsoft.Extensions.DependencyInjection -Version 2.1.1"

    – Hans Passant
    Nov 15 '18 at 16:24











  • If I create a new UWP project, I can see the package installed, and I get no errors installing it. The problem is this solution that I have that is using some version of the "Microsoft.Extensions.DependencyInjection" but I can t see it in the Package Manager nor in References, but the application runs fine and is using it for sure. So my problem is that I don't have any information in the solution that shows that reference to the "Microsoft.Extensions.DependencyInjection". I can see in the dll that the version is 2.0.17205.

    – J_PT
    Nov 15 '18 at 17:33











  • The UWP project is targeting Windows 10 Fall Creators update 10.0 build 16299, as min and target versions

    – J_PT
    Nov 15 '18 at 17:35
















0












0








0








I have a solution with several UWP projects that are using "Microsoft.Extensions.DependencyInjection"



I can't see any references in NuGet Package Manager to this extension nor in the project s References.
Using VS, how can I list all these external dependencies that my solution is using for each project inside.










share|improve this question














I have a solution with several UWP projects that are using "Microsoft.Extensions.DependencyInjection"



I can't see any references in NuGet Package Manager to this extension nor in the project s References.
Using VS, how can I list all these external dependencies that my solution is using for each project inside.







c# visual-studio nuget






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 15 '18 at 15:26









J_PTJ_PT

16711




16711













  • The package does not support UWP. The package installer races a bit too fast to see the error message, but you can see it from the Package Manager Console window when you type "Install-Package Microsoft.Extensions.DependencyInjection -Version 2.1.1"

    – Hans Passant
    Nov 15 '18 at 16:24











  • If I create a new UWP project, I can see the package installed, and I get no errors installing it. The problem is this solution that I have that is using some version of the "Microsoft.Extensions.DependencyInjection" but I can t see it in the Package Manager nor in References, but the application runs fine and is using it for sure. So my problem is that I don't have any information in the solution that shows that reference to the "Microsoft.Extensions.DependencyInjection". I can see in the dll that the version is 2.0.17205.

    – J_PT
    Nov 15 '18 at 17:33











  • The UWP project is targeting Windows 10 Fall Creators update 10.0 build 16299, as min and target versions

    – J_PT
    Nov 15 '18 at 17:35





















  • The package does not support UWP. The package installer races a bit too fast to see the error message, but you can see it from the Package Manager Console window when you type "Install-Package Microsoft.Extensions.DependencyInjection -Version 2.1.1"

    – Hans Passant
    Nov 15 '18 at 16:24











  • If I create a new UWP project, I can see the package installed, and I get no errors installing it. The problem is this solution that I have that is using some version of the "Microsoft.Extensions.DependencyInjection" but I can t see it in the Package Manager nor in References, but the application runs fine and is using it for sure. So my problem is that I don't have any information in the solution that shows that reference to the "Microsoft.Extensions.DependencyInjection". I can see in the dll that the version is 2.0.17205.

    – J_PT
    Nov 15 '18 at 17:33











  • The UWP project is targeting Windows 10 Fall Creators update 10.0 build 16299, as min and target versions

    – J_PT
    Nov 15 '18 at 17:35



















The package does not support UWP. The package installer races a bit too fast to see the error message, but you can see it from the Package Manager Console window when you type "Install-Package Microsoft.Extensions.DependencyInjection -Version 2.1.1"

– Hans Passant
Nov 15 '18 at 16:24





The package does not support UWP. The package installer races a bit too fast to see the error message, but you can see it from the Package Manager Console window when you type "Install-Package Microsoft.Extensions.DependencyInjection -Version 2.1.1"

– Hans Passant
Nov 15 '18 at 16:24













If I create a new UWP project, I can see the package installed, and I get no errors installing it. The problem is this solution that I have that is using some version of the "Microsoft.Extensions.DependencyInjection" but I can t see it in the Package Manager nor in References, but the application runs fine and is using it for sure. So my problem is that I don't have any information in the solution that shows that reference to the "Microsoft.Extensions.DependencyInjection". I can see in the dll that the version is 2.0.17205.

– J_PT
Nov 15 '18 at 17:33





If I create a new UWP project, I can see the package installed, and I get no errors installing it. The problem is this solution that I have that is using some version of the "Microsoft.Extensions.DependencyInjection" but I can t see it in the Package Manager nor in References, but the application runs fine and is using it for sure. So my problem is that I don't have any information in the solution that shows that reference to the "Microsoft.Extensions.DependencyInjection". I can see in the dll that the version is 2.0.17205.

– J_PT
Nov 15 '18 at 17:33













The UWP project is targeting Windows 10 Fall Creators update 10.0 build 16299, as min and target versions

– J_PT
Nov 15 '18 at 17:35







The UWP project is targeting Windows 10 Fall Creators update 10.0 build 16299, as min and target versions

– J_PT
Nov 15 '18 at 17:35














1 Answer
1






active

oldest

votes


















1















UWP and External Lib Dependencies




I can install the nuget package Microsoft.Extensions.DependencyInjection to the UWP project, which target Windows 10 Fall Creators update 10.0 build 16299 without any error.



I can also see it in the Package Manager and in References:



enter image description here



enter image description here



So, please double check if it in the Package Manager under the Installed tab nor in References.



If you still can not see it, please try to restart your Visual Studio and PC, and try to uninstall and reinstall the nuget package.




how can I list all these external dependencies that my solution is
using for each project inside.




You can right on your solution in the Solution Explorer, then select Manage NuGet Packages for Solution ..., you will get following window:



enter image description here



You can find the external dependencies that your solution is using for each project inside.



Update:




My problem is that I don't know how many more references are mangled,
and I can t search for something that I don't know it exists




When you don't know how many more references are mangled, you can just delete the globe cache of nuget package, the default path is C:Users<UserName>.nugetpackages. When you build the project, VS will re-download those packages.



Hope this helps.






share|improve this answer


























  • Hi, as I told before in new projects I can see the reference, the problem is in this solution that does not list dependencies correctly. I also know that reinstalling the missing reference will make it appear in the references and NuGet Package manager... My problem is that I don't know how many more references are mangled, and I can t search for something that I don't know it exists... This is a very large solution with many projects

    – J_PT
    Nov 16 '18 at 10:33






  • 1





    When you don't know how many more references are mangled, you can just delete the globe cache of nuget package, the default path is C:Users<UserName>.nugetpackages. When you build the project, VS will re-download those packages.

    – Leo Liu-MSFT
    Nov 19 '18 at 8:15






  • 1





    Thank you, that help

    – J_PT
    Nov 21 '18 at 17:42











  • @J_PT, I have updated the comment to the answer. Since that helps you resolve the issue, you could accept it as an answer. This can be beneficial to other community members reading this thread and we could close this thread, thanks.

    – Leo Liu-MSFT
    Nov 27 '18 at 1:43











  • Thank you......

    – J_PT
    Dec 21 '18 at 17:24











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53322690%2fuwp-and-external-lib-dependencies%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









1















UWP and External Lib Dependencies




I can install the nuget package Microsoft.Extensions.DependencyInjection to the UWP project, which target Windows 10 Fall Creators update 10.0 build 16299 without any error.



I can also see it in the Package Manager and in References:



enter image description here



enter image description here



So, please double check if it in the Package Manager under the Installed tab nor in References.



If you still can not see it, please try to restart your Visual Studio and PC, and try to uninstall and reinstall the nuget package.




how can I list all these external dependencies that my solution is
using for each project inside.




You can right on your solution in the Solution Explorer, then select Manage NuGet Packages for Solution ..., you will get following window:



enter image description here



You can find the external dependencies that your solution is using for each project inside.



Update:




My problem is that I don't know how many more references are mangled,
and I can t search for something that I don't know it exists




When you don't know how many more references are mangled, you can just delete the globe cache of nuget package, the default path is C:Users<UserName>.nugetpackages. When you build the project, VS will re-download those packages.



Hope this helps.






share|improve this answer


























  • Hi, as I told before in new projects I can see the reference, the problem is in this solution that does not list dependencies correctly. I also know that reinstalling the missing reference will make it appear in the references and NuGet Package manager... My problem is that I don't know how many more references are mangled, and I can t search for something that I don't know it exists... This is a very large solution with many projects

    – J_PT
    Nov 16 '18 at 10:33






  • 1





    When you don't know how many more references are mangled, you can just delete the globe cache of nuget package, the default path is C:Users<UserName>.nugetpackages. When you build the project, VS will re-download those packages.

    – Leo Liu-MSFT
    Nov 19 '18 at 8:15






  • 1





    Thank you, that help

    – J_PT
    Nov 21 '18 at 17:42











  • @J_PT, I have updated the comment to the answer. Since that helps you resolve the issue, you could accept it as an answer. This can be beneficial to other community members reading this thread and we could close this thread, thanks.

    – Leo Liu-MSFT
    Nov 27 '18 at 1:43











  • Thank you......

    – J_PT
    Dec 21 '18 at 17:24
















1















UWP and External Lib Dependencies




I can install the nuget package Microsoft.Extensions.DependencyInjection to the UWP project, which target Windows 10 Fall Creators update 10.0 build 16299 without any error.



I can also see it in the Package Manager and in References:



enter image description here



enter image description here



So, please double check if it in the Package Manager under the Installed tab nor in References.



If you still can not see it, please try to restart your Visual Studio and PC, and try to uninstall and reinstall the nuget package.




how can I list all these external dependencies that my solution is
using for each project inside.




You can right on your solution in the Solution Explorer, then select Manage NuGet Packages for Solution ..., you will get following window:



enter image description here



You can find the external dependencies that your solution is using for each project inside.



Update:




My problem is that I don't know how many more references are mangled,
and I can t search for something that I don't know it exists




When you don't know how many more references are mangled, you can just delete the globe cache of nuget package, the default path is C:Users<UserName>.nugetpackages. When you build the project, VS will re-download those packages.



Hope this helps.






share|improve this answer


























  • Hi, as I told before in new projects I can see the reference, the problem is in this solution that does not list dependencies correctly. I also know that reinstalling the missing reference will make it appear in the references and NuGet Package manager... My problem is that I don't know how many more references are mangled, and I can t search for something that I don't know it exists... This is a very large solution with many projects

    – J_PT
    Nov 16 '18 at 10:33






  • 1





    When you don't know how many more references are mangled, you can just delete the globe cache of nuget package, the default path is C:Users<UserName>.nugetpackages. When you build the project, VS will re-download those packages.

    – Leo Liu-MSFT
    Nov 19 '18 at 8:15






  • 1





    Thank you, that help

    – J_PT
    Nov 21 '18 at 17:42











  • @J_PT, I have updated the comment to the answer. Since that helps you resolve the issue, you could accept it as an answer. This can be beneficial to other community members reading this thread and we could close this thread, thanks.

    – Leo Liu-MSFT
    Nov 27 '18 at 1:43











  • Thank you......

    – J_PT
    Dec 21 '18 at 17:24














1












1








1








UWP and External Lib Dependencies




I can install the nuget package Microsoft.Extensions.DependencyInjection to the UWP project, which target Windows 10 Fall Creators update 10.0 build 16299 without any error.



I can also see it in the Package Manager and in References:



enter image description here



enter image description here



So, please double check if it in the Package Manager under the Installed tab nor in References.



If you still can not see it, please try to restart your Visual Studio and PC, and try to uninstall and reinstall the nuget package.




how can I list all these external dependencies that my solution is
using for each project inside.




You can right on your solution in the Solution Explorer, then select Manage NuGet Packages for Solution ..., you will get following window:



enter image description here



You can find the external dependencies that your solution is using for each project inside.



Update:




My problem is that I don't know how many more references are mangled,
and I can t search for something that I don't know it exists




When you don't know how many more references are mangled, you can just delete the globe cache of nuget package, the default path is C:Users<UserName>.nugetpackages. When you build the project, VS will re-download those packages.



Hope this helps.






share|improve this answer
















UWP and External Lib Dependencies




I can install the nuget package Microsoft.Extensions.DependencyInjection to the UWP project, which target Windows 10 Fall Creators update 10.0 build 16299 without any error.



I can also see it in the Package Manager and in References:



enter image description here



enter image description here



So, please double check if it in the Package Manager under the Installed tab nor in References.



If you still can not see it, please try to restart your Visual Studio and PC, and try to uninstall and reinstall the nuget package.




how can I list all these external dependencies that my solution is
using for each project inside.




You can right on your solution in the Solution Explorer, then select Manage NuGet Packages for Solution ..., you will get following window:



enter image description here



You can find the external dependencies that your solution is using for each project inside.



Update:




My problem is that I don't know how many more references are mangled,
and I can t search for something that I don't know it exists




When you don't know how many more references are mangled, you can just delete the globe cache of nuget package, the default path is C:Users<UserName>.nugetpackages. When you build the project, VS will re-download those packages.



Hope this helps.







share|improve this answer














share|improve this answer



share|improve this answer








edited Nov 22 '18 at 1:18

























answered Nov 16 '18 at 2:57









Leo Liu-MSFTLeo Liu-MSFT

20.7k22634




20.7k22634













  • Hi, as I told before in new projects I can see the reference, the problem is in this solution that does not list dependencies correctly. I also know that reinstalling the missing reference will make it appear in the references and NuGet Package manager... My problem is that I don't know how many more references are mangled, and I can t search for something that I don't know it exists... This is a very large solution with many projects

    – J_PT
    Nov 16 '18 at 10:33






  • 1





    When you don't know how many more references are mangled, you can just delete the globe cache of nuget package, the default path is C:Users<UserName>.nugetpackages. When you build the project, VS will re-download those packages.

    – Leo Liu-MSFT
    Nov 19 '18 at 8:15






  • 1





    Thank you, that help

    – J_PT
    Nov 21 '18 at 17:42











  • @J_PT, I have updated the comment to the answer. Since that helps you resolve the issue, you could accept it as an answer. This can be beneficial to other community members reading this thread and we could close this thread, thanks.

    – Leo Liu-MSFT
    Nov 27 '18 at 1:43











  • Thank you......

    – J_PT
    Dec 21 '18 at 17:24



















  • Hi, as I told before in new projects I can see the reference, the problem is in this solution that does not list dependencies correctly. I also know that reinstalling the missing reference will make it appear in the references and NuGet Package manager... My problem is that I don't know how many more references are mangled, and I can t search for something that I don't know it exists... This is a very large solution with many projects

    – J_PT
    Nov 16 '18 at 10:33






  • 1





    When you don't know how many more references are mangled, you can just delete the globe cache of nuget package, the default path is C:Users<UserName>.nugetpackages. When you build the project, VS will re-download those packages.

    – Leo Liu-MSFT
    Nov 19 '18 at 8:15






  • 1





    Thank you, that help

    – J_PT
    Nov 21 '18 at 17:42











  • @J_PT, I have updated the comment to the answer. Since that helps you resolve the issue, you could accept it as an answer. This can be beneficial to other community members reading this thread and we could close this thread, thanks.

    – Leo Liu-MSFT
    Nov 27 '18 at 1:43











  • Thank you......

    – J_PT
    Dec 21 '18 at 17:24

















Hi, as I told before in new projects I can see the reference, the problem is in this solution that does not list dependencies correctly. I also know that reinstalling the missing reference will make it appear in the references and NuGet Package manager... My problem is that I don't know how many more references are mangled, and I can t search for something that I don't know it exists... This is a very large solution with many projects

– J_PT
Nov 16 '18 at 10:33





Hi, as I told before in new projects I can see the reference, the problem is in this solution that does not list dependencies correctly. I also know that reinstalling the missing reference will make it appear in the references and NuGet Package manager... My problem is that I don't know how many more references are mangled, and I can t search for something that I don't know it exists... This is a very large solution with many projects

– J_PT
Nov 16 '18 at 10:33




1




1





When you don't know how many more references are mangled, you can just delete the globe cache of nuget package, the default path is C:Users<UserName>.nugetpackages. When you build the project, VS will re-download those packages.

– Leo Liu-MSFT
Nov 19 '18 at 8:15





When you don't know how many more references are mangled, you can just delete the globe cache of nuget package, the default path is C:Users<UserName>.nugetpackages. When you build the project, VS will re-download those packages.

– Leo Liu-MSFT
Nov 19 '18 at 8:15




1




1





Thank you, that help

– J_PT
Nov 21 '18 at 17:42





Thank you, that help

– J_PT
Nov 21 '18 at 17:42













@J_PT, I have updated the comment to the answer. Since that helps you resolve the issue, you could accept it as an answer. This can be beneficial to other community members reading this thread and we could close this thread, thanks.

– Leo Liu-MSFT
Nov 27 '18 at 1:43





@J_PT, I have updated the comment to the answer. Since that helps you resolve the issue, you could accept it as an answer. This can be beneficial to other community members reading this thread and we could close this thread, thanks.

– Leo Liu-MSFT
Nov 27 '18 at 1:43













Thank you......

– J_PT
Dec 21 '18 at 17:24





Thank you......

– J_PT
Dec 21 '18 at 17:24




















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53322690%2fuwp-and-external-lib-dependencies%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Florida Star v. B. J. F.

Danny Elfman

Lugert, Oklahoma