project-reference

问题 I have a Solution with .NET Framework Project A which builds a winforms application containing a class, MyPlayer which requires LibVLCSharp . In order for the application to build and run correctly I had to add the following Nuget packages: LibVLCSharp LibVLCSharp.WinForms VideoLAN.LibVLC.Windows Now I want to move class MyPlayer to a separate .NET Standard class library, Project B , to separate out function from UI and so that it can be used by multiple other projects targeted to different

问题 I have 3 class library projects. Lets call them A, B & C. I have added project reference of A & B into the project C. A & B are building without any error or warning. Code(Class file) from the project C uses public classes from A & B. When I add project reference in C and look at the class file (before building project C) in the C project, I can clearly see that all the classes and namespaces from A & B are resolved. When I hover my mouse on the class name (class from either A or B), it shows

问题 Excuse the incredibly silly question but im new to C# . I just can’t figure out how to use classes from one Project in another Project. Lets say I want to take a string from Project1 to Project2 and have Project2 print said string . I reference Project2 from Project1 with the “add reference” menu , then I add “using Project2” and then I write this to trying and call "print" from "ClassA" in "Project2". Project2.ClassA Classa = new Project2.ClassA(); Console.WriteLine(Classa.print); but all i

问题 Setup: ASP.NET MVC3 Ninject v2.2.1.4 Ninject v3.0.0.15 Ninject.MVC3 v3.0.0.6 Ninject.Web.Common v3.0.0.7 Using NuGet, my UnitTest project references Ninject v2.2.1.4 My Web Project references Ninject v3.0.0.15, Ninject.MVC3 and Ninject.Web.Common Problem: With win explorer open at the bin folder of my web project, I build my solution and I can see Ninject v2.2.1.4 copied into the bin directory of my web project. And then being replaced by Ninject v3.0.0.15. When i hit F5 to debug, Ninject.dll

问题 Setup: ASP.NET MVC3 Ninject v2.2.1.4 Ninject v3.0.0.15 Ninject.MVC3 v3.0.0.6 Ninject.Web.Common v3.0.0.7 Using NuGet, my UnitTest project references Ninject v2.2.1.4 My Web Project references Ninject v3.0.0.15, Ninject.MVC3 and Ninject.Web.Common Problem: With win explorer open at the bin folder of my web project, I build my solution and I can see Ninject v2.2.1.4 copied into the bin directory of my web project. And then being replaced by Ninject v3.0.0.15. When i hit F5 to debug, Ninject.dll

问题 What process does .NET use to locate a referenced assembly at runtime and is it different than the process used to locate a referenced assembly during compilation? I am specifically interested in the locations that are searched and their search order and any parameters/configuration settings that might affect the outcome. 回答1: There are three types of references that can be made in a .NET application. This answer will only cover the first two in the list below. File references. Project

问题 I was building/deploying my Windows Phone app in Visual Studio Professional 2013 with Update 3. The following console output showed up: 1>------ Build started: Project: CapturingVideos, Configuration: Debug ARM ------ 2>------ Deploy started: Project: CapturingVideos, Configuration: Debug ARM ------ 2>Deploying to Phone Internal Storage... 2>Creating a new clean layout... 2>Copying files: Total <1 mb to layout... 2>Checking whether required frameworks are installed... 2>Warning : DEP0810 :

问题 I have a solution with other 70 projects into it. My question is : How can I know where the project is used? I do not want to open all those 70 projects to verify the References one by one. How can I see which project use one project in particular? Edit I do not want to do 1 by 1 search in XML or in the Reference in VS. I would like a quick way to do it. 回答1: There's a pretty cool codeplex project that creates dependecy visualizations that I've used before. Although, with 70 projects, you

问题 We Have a large VS solution using project references which is build by TFS Build like so: Solution - Project 1 - Project 2 - Project ... - Project N Because the solution is too large we have several smaller solutions which we use day to day: SubSolution - Project 1 - Project 19 The problem is that developers working on SubSolution find that it is not building because the project references could not be found, so they change the projects to use file references. This then goes on to break the

问题 We Have a large VS solution using project references which is build by TFS Build like so: Solution - Project 1 - Project 2 - Project ... - Project N Because the solution is too large we have several smaller solutions which we use day to day: SubSolution - Project 1 - Project 19 The problem is that developers working on SubSolution find that it is not building because the project references could not be found, so they change the projects to use file references. This then goes on to break the