In Visual Studio, when using Manage NuGet Packages for Solution, the ProGet feeds never return. Visual Studio just hangs. No updates from the feed are ever delivered. When using Manage NuGet Packages at the project level, the ProGet feeds work great and are nice and quick.
Any resolution to this problem? It's the only issue preventing full usage of ProGet.
Update:
I'm now happily working with the ProGet team on this issue.
ProGet v3.5.x version has resolved the issue.
Related
I'm trying to build a visual studio 2015 dot-net application which has log4net reference in the code.
When I build in Azure DevOps using Nuget restore, Nuget Tool installer, Visual studio build, Publish Build artifacts I am getting an error:
Error CS0246: The type or namespace name 'log4net' could not be found (are you missing a using directive or an assembly reference?) Process 'msbuild.exe' exited with code '1'.
Please someone suggest whether I have to add another agent or make some reference to the package/nuget in Azure DevOps. need details since I'm new to Azure DevOps.
The error message suggests that either the using is missing or the assembly could not be found, meaning that probably the nuget restoration has failed.
If you can't figure out the issue by looking at the log, the first step should be to set system.debug to true, then you might get more info about what the issue might be.
My first instinct when I don't know what's going on would alsways be to look into the s folder of an agent but I don't have experience with hosted agents and as far as I know you cannot access the working folder of a hosted agent.
So as a workaround (only if everything else fails) I would suggest to zip the s folder ("$(Build.Sources)") or special parts of it into the a folder ("$(Build.Artefacts)") and publish that zip as an artefact. Then you can download it and look at it in great detail, e.g. look at the packages folder or open the solution and see why it doesn't compile.
Problem was partly solved as there was .gitignore and .gitattribute files in my source directory which i guess had entries to ignore the third party .dlls like log4net and several folders which were not getting checked-in when i did vsts push. But there arose some other errors in vsts build now which i am trying to figure out. I will create a new thread for that.
Thanks.
For some reason I lost ability to see it in
Tools -> Manage Nuget Packages for Solution
However from the docs
I used
Install-Package log4net
in Package Manager Console
That solved the issue.
Previously I had noticed the yellow triangle against log4net In Manage Packages For Solution, and may have tried removing it via Nuget.
However it was still showing as a reference
This is related to output of publish process in visual studio 2017 (version 15.7.1)
I am developing cross platform application using .net core 2.1. Application will also be compiled on .Net framework 472.
My application requires that output of compilation after publish process should generate dlls and not a nupkg. This is required because my application depend on dynamic loading of the libraries. Since the publish process generates nupkg, I am not able to use output of publish process for dynamically loading of libraries.
I googled the issue but most of the help that I found was on how to generate nuget package whereas my requirement is opposite of that.
Thank you in advance for your help.
I could resolve this issue by generating output using dotnet publish command over CLI.
https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-publish?tabs=netcore21
I have VS2017 and plan to do some C# development that needs to access Oracle 12c database.
I went in Oracle site and downloaded ODTforVS2017_122011.exe. The installation was successful.
But when I tried to declare my connection type OracleConnection, my project does not know it and I can not reference Oracle.ManagedDataAccess. I had to go to Nuget to install them to satisfy the compiler.
So, my curious question is: is the ODT installation from Oracle site necessary or Nuget installation only would suffice? I just do not want to install to much irrelevant stuff that I would not be able to justify.
I don't believe you need the tools, no. They're Visual Studio features, rather than tools needed at execution time.
From the download page:
Oracle Developer Tools for Visual Studio enables Visual Studio data features such as Server Explorer integration, TableAdapter Configuration Wizard and Entity Designer and also includes many useful Oracle specific tools.
So you may find it useful to have those tools, but I don't believe they're required on every machine where you want to either develop or deploy your application.
I am trying to deploy a wpf application with an embedded rdlc report using clickonce. The previous version of report viewer (in VS2015) was built-in so it was easy and convenient to use and I had no issues deploying this project.
Now since easy and convenient is not the goal anymore, in vs2017 after a failed deploy with an error message that gave me absolutely no help, I have come to realize that apparently you have to install 2 additional VS extensions and a report viewer runtime on every machine where an app uses and rdlc reports (feels like crystal reports all over again) and you have to exclude the automatically included Chinese localization files in your clickonce deployment (which cause a manifest parse error). Anyway, the instructions on MS website say that click once should have a "Microsoft Visual Studio Report Viewer" prerequisite option to select as requirement of installing your app. However, after installing the runtime on my development machine, restarting visual studio, this option is not available. Does anyone know how to get this to work?
I used Project|Manage NuGet Packages to add this package to my project.
https://www.nuget.org/packages/Microsoft.ReportViewer.Runtime.Common/12.0.2402.15
If you search with Manage NuGet Packages, there's quite a few ReportViewer related items. I'm not sure which ones are appropriate to your WPF app.
Anyway, the deployment project picked up the various ReportViewer assembly dependencies and everything seems to be working without the EXE redist from MS.
I'm trying to set up a NuGet server using ProGet and am hitting a brick wall when publishing a package and it doesn't appear in the feed. The package is written to disk and works in other NuGet feeds. Other packages also don't appear in the ProGet feed so I'm pretty certain that the package is fine and that the problem lies with ProGet.
I'm using the community version of ProGet, but I don't see why that would affect anything.
Any ideas are most welcome!
The ProGet service is responsible for indexing packages, so if it's not running, packages could be uploaded but not displayed in any feeds. Here are the common troubleshooting steps for this scenario:
Verify that the ProGet Windows service (INEDOPROGETSVC) is running.
Ensure that the user account hosting the ProGet service has access to the feed storage path. Since it is NETWORK SERVICE by default, it would not see your mapped drives, and may not have access to the UNC path where the packages are stored.
Try running the ProGet service interactively, i.e. stop the ProGet Windows service and run ProGet.Service.exe manually as a console application to see any live output. Remember to restart the ProGet service when you close the console application.
Check for feed indexing errors to see if there was a problem indexing a particular packages. I know in much older versions that single "poisoned" packages (bad .nuspec file, invalid directory structure, etc.) could halt the indexing altogether.
Thanks John Rasch, found that your first point gave me what i needed to look in the right direction.
I could not find the (INEDOPROGETSVC) service but I did find (ProGet Servie) - I restarted this and then refreshed the my feed and all the missing packages showed up.
My version of ProGet is v3.3.12
Thanks John.