System.ServiceProcess.ServiceController.dll [SOLVED]
-
Hi, I just upgraded a .NET Framework project to .NET 8.0 using the .NET Upgrade Assistant extension for Visual Studio from Microsoft. I added a reference in the Dependencies folder to System.ServiceProcess.ServiceController.dll in the "C:\Program Files\dotnet\sdk\8.0.101" disk folder. For some reason, it's unable to resolve types within that DLL (such as
ServiceBase) and the reference in the Dependencies folder has a yellow triangle with an exclamation mark. Is the project fubared because it was in-place upgraded, or is there something else wrong? Why can't it resolve the types within that DLL, and why does the reference node have that yellow triangle icon? When I mouse over the icon, it doesn't display any tooltip to tell me what's wrong. SOLUTION: I added the file from the wrong folder. When I changed the reference to point to the same assembly in the "C:\Program Files\dotnet\sdk\8.0.101\runtimes\win\lib\net8.0\" folder, it resolved all the issues. Thanks for reading my post.The difficult we do right away... ...the impossible takes slightly longer.
-
Hi, I just upgraded a .NET Framework project to .NET 8.0 using the .NET Upgrade Assistant extension for Visual Studio from Microsoft. I added a reference in the Dependencies folder to System.ServiceProcess.ServiceController.dll in the "C:\Program Files\dotnet\sdk\8.0.101" disk folder. For some reason, it's unable to resolve types within that DLL (such as
ServiceBase) and the reference in the Dependencies folder has a yellow triangle with an exclamation mark. Is the project fubared because it was in-place upgraded, or is there something else wrong? Why can't it resolve the types within that DLL, and why does the reference node have that yellow triangle icon? When I mouse over the icon, it doesn't display any tooltip to tell me what's wrong. SOLUTION: I added the file from the wrong folder. When I changed the reference to point to the same assembly in the "C:\Program Files\dotnet\sdk\8.0.101\runtimes\win\lib\net8.0\" folder, it resolved all the issues. Thanks for reading my post.The difficult we do right away... ...the impossible takes slightly longer.
-
That will probably work, but I think you'll have a better time now and in the future if you add that as a nuget: NuGet Gallery | System.ServiceProcess.ServiceController 9.0.0-preview.1.24080.9[^]
Hey, thanks. I didn't know it's available as a nuget package.
The difficult we do right away... ...the impossible takes slightly longer.
-
Hey, thanks. I didn't know it's available as a nuget package.
The difficult we do right away... ...the impossible takes slightly longer.
Many of what you'd probably think of as common to .NET dependencies are out there in various forms. Dependency chaining has changed a little bit though. Mostly for the better. For the most part, transients can now be consumed without a direct reference and very little effort. If you have a nuget that then has as a dependency and you are already including that original nuget package, you do not generally also need a direct package reference in there... dotnet build will just figure that all out. (Assuming packagereference, but don't do packages.config anymore, ever)
