Hi @arozanski_1087, I just wanted to let you know that we just released a new version of pgscan, 1.4.2. Going forward it will automatically scan npm packages anytime it is scanning for NuGet packages using a .NET solution or project, there will not be any new parameter needed to enable the search. We are still working on adding yarn support, but that one will take us a bit of time to add. We will update you when that one is ready to be used. Thanks, Rich

@atripp that's extremely informative! What I found this morning that was deleting and re-adding the connector for the IP feed after clearing the cache(because I'm paranoid) was what needed to happen for it to stop being cached by our Mainline feed.

@atripp you're the best. I'll give these a shot and come back if i run into something i can't work through.

@arozanski_1087 that's a slightly different caching setting If you navigate Feeds > Connectors >your conenctor, it will be here: [image: 1630687457379-c8f90f17-7cae-4e96-b777-d934f1ee96ce-image.png] Clicking on 'status" will show you all the cached queries.

Hello; Thanks for reporting this bug/layout issue! I just made a simple change (PG-1956) to fix this, and it will be available in the next maintenance release (5.3.29)

@arozanski_1087 no problem! And by the way, the pgscan tool is open source, so if you see opportunities to improve it, or want to devleop something on your own, please don't hesitate to use the sources - https://github.com/Inedo/pgscan

@atripp You bet. I'll see what I can do and let you know

Yeah, that's a nightmare and a half and I can see why you did that. Currently I've tried repackaging the nuget but it brings about other errors, where it restores properly but later on in compile I get build errors. Right now I'm using the legacy version/older version of the nuget URL instead of the current v3 one until they get off of that package and I can remove it from my feed. It follows the format: https://url.domain/nuget/feedName/ instead of https://url.domain/nuget/feedName/v3/index.json .

Hi @arozanski_1087, That's great! I'm sorry it took this long to get this working. Thanks for working with me to figure this out! I'm going to make a change to the documentation right now to include the requirement of naming the extension file. I will also get a full release of this extension out today so it will lock in that version with the ProGet release tomorrow. Thanks, Rich

Hi @arozanski_1087, Thanks for following up with us. I'm glad you got this working! Please don't hesitate to reach out if you have any other questions for us. Thanks, Rich

Hi @arozanski_1087, Technically they do not need to run as the same account, but it does simplify things. Especially since they share the configuration file that contains the connection string. Also, please make sure that your IIS has the correct features installed. You can see the Configuring IIS Roles & Features for Inedo Products documentation for that information. Were you using that exact service account previously on the integrated web server install? If you were there shouldn't be any iossue connecting from IIS then. Thanks, Rich