Downloads:

97,861

Downloads of v 3.21:

4,222

Last Update:

12/28/2016

Package Maintainer(s):

Software Author(s):

  • Luan Nguyen

Tags:

nuget admin nupkg nuspec

Nuget Package Explorer

This is not the latest version of Nuget Package Explorer available.

3.21 | Updated: 12/28/2016

Downloads:

97,861

Downloads of v 3.21:

4,222

Software Author(s):

  • Luan Nguyen

Nuget Package Explorer 3.21

This is not the latest version of Nuget Package Explorer available.

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install Nuget Package Explorer, run the following command from the command line or from PowerShell:

>

To upgrade Nuget Package Explorer, run the following command from the command line or from PowerShell:

>

To uninstall Nuget Package Explorer, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade nugetpackageexplorer -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade nugetpackageexplorer -y --source="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure nugetpackageexplorer installed
  win_chocolatey:
    name: nugetpackageexplorer
    state: present
    version: 3.21
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'nugetpackageexplorer' do
  action    :install
  version  '3.21'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: nugetpackageexplorer,
    Version: 3.21,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller nugetpackageexplorer
{
   Name     = 'nugetpackageexplorer'
   Ensure   = 'Present'
   Version  = '3.21'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'nugetpackageexplorer':
  provider => 'chocolatey',
  ensure   => '3.21',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install nugetpackageexplorer version="3.21" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 3/15/2017.

Description

NuGet Package Explorer is an application which allows creating and exploring NuGet packages easily.
After installing it, you can double click on a .nupkg file to view the package content.
You can also load packages directly from the official NuGet feed.


ChocolateyInstall.ps1

    $drop = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
    $exe = "$drop\NugetPackageExplorer.exe"
    Install-ChocolateyDesktopLink $exe
    $allTypes = (cmd /c assoc)
    $testType = $allTypes | ? { $_.StartsWith('.nupkg') }
    if($testType -ne $null) {
        $fileType=$testType.Split("=")[1]
    } 
    else {
        $fileType="Nuget.Package"
        Start-ChocolateyProcessAsAdmin "cmd /c assoc .nupkg=$fileType"
    }
    Start-ChocolateyProcessAsAdmin "cmd /c ftype $fileType=`"$exe`" %1"
CodeExecutor.dll
md5: 78E89F3CDA366774F248F4D96F007D37 | sha1: 341B984D1AFB0A2A11393C151B1C36F89042692A | sha256: A75C4C5D119AA12528DFEBA8F431F31B087BF307B771C3C490A987B44E74B706 | sha512: BBBC2EB8029B6F8F0C9333BF040A232D4144B1F66A71835647F61376D599F9233B6980490DEBFF5BDA81B436022010FA7A4A8154BEB9D2EA7A46868E94B70553
Core.dll
md5: A8771CDEB78FEB57E6BADD472C1D07AA | sha1: C5191A1F95C3AB5AE527128BF9077ACBBB246908 | sha256: 9F30793A9F834572E25EBDA4D6A0F69EE164F95BF4ED42A8A67443749385BA17 | sha512: 119CE15D7B064A5377B73E93DA0F35E11570847DD8AA8D7047CD1B6984B09E63A73A0B40F425F676D8D39159F5BF12A190D1D9712C851D2AEB227C742F7DA81E
GrayscaleEffect.dll
md5: E7AD920A15DB8E01FC527411F7E7A753 | sha1: 62E5394DDEB1F8C6A329531F6FC089A7C6BBE912 | sha256: 533292846A70ABA5BB4FD67A2807C211CC265091A003BE6B8466987CC4F1F56B | sha512: 175ACF3CD22C3B53D0B22DA922A2B5A2C36B6182268B76B6233F1B850C3F073A768AEA987D95C0EA0E0306FE073DB1CA989AA52CF39CA05D06586090E995642F
Humanizer.dll
md5: 87A2200244B2819E9A8842ECC251EDEC | sha1: 35A22187107E0D5FB06877969B999AE2D5F5C623 | sha256: 785601E89F1415EAEFDB524D98365C53686DE186A33213943E3BD65B0728456A | sha512: A8E5132F251276BDFB7475880BB482C7F937460396CD108EB452C10956AE88D386C59A64AA50D90485B5268214DE08513FDB69D1F1FA1EBCE08DA8517A8A7017
ICSharpCode.AvalonEdit.dll
md5: 303D28A418B17EF5F59ECDA6E1BD22B2 | sha1: C15A5573FD84E1D2412BD3A56C6BD3054C192602 | sha256: 1337671B096B4B75381A86250129C93438E9626A300D40B48ADA7E62C3439DB5 | sha512: 50EEF42516F62B42AB9BE9F811CA690ACC867F51032C71C21BB9AE0A061367BD545E5A1072695CA3F14E4C1209678379599A54EFFFDE366EE2D1F9386343B542
Microsoft.Web.XmlTransform.dll
md5: 6AD7D1E92C9833F4BDDE6A4BC84F2E1A | sha1: B38D23B6A960F5F07664565835137FE3C8FDB7ED | sha256: 13DCF5066E00152238191314D4A46605204FFABDBB830BDD0C97DF3027D1261D | sha512: 01C4ECC46576618394FBBEE701F5A726F97D31FB39D5F1C6305D21CA7AD0B0ABC09B69FB733C42D4D1203FCE78DD3F3D5129C21EA0BC9B92D0AB3A7BF09C006C
NuGet.Core.dll
md5: CFE27B330347673C5EB1387C16F9B69B | sha1: AFD5E99854485B34559D9E122D452563AFAD0A82 | sha256: 784D2A3D7FBDB469CC3A67091763AADF283575A9BF3B873F771F5F87ED7327C7 | sha512: 4F4D9FC6A32EEE2EA52085580993645B651EBA2137A985E03D05645CB8A428840246430FA7EA1D080AB0042EEAB6E84E7BAF72A0C4E8515CCF03274063BAE64C
NuGetPackageExplorer.exe
md5: 4B2BADBB0B4D1A53F9704DAB0CD414A9 | sha1: 9FE3CBC8BF7EC78A1BEDE560C5A4ED07F5A4E28E | sha256: 1AF341EB35CE5CB5C74F60F3A0BFC53F33D5C50C95CAB2A447A5916FE4E105C2 | sha512: 584EDCB978FD8A15472F0DAA169B74137BFB43660E1D8207D5D66FB7C19CDC8BD5F5B7FDB55581C5E645B5800551630EC3A000877F327F8D98E3C6596E1ECCDD
NuGetPackageExplorer.exe.config
<?xml version="1.0"?>
<configuration>
    <configSections>
        <sectionGroup name="userSettings" type="System.Configuration.UserSettingsGroup, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
            <section name="PackageExplorer.Properties.Settings" type="System.Configuration.ClientSettingsSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" allowExeDefinition="MachineToLocalUser" requirePermission="false"/>
        </sectionGroup>
    </configSections>
    <userSettings>
        <PackageExplorer.Properties.Settings>
            <setting name="FontSize" serializeAs="String">
                <value>12</value>
            </setting>
            <setting name="ContentViewerHeight" serializeAs="String">
                <value>400</value>
            </setting>
            <setting name="PackageSource" serializeAs="String">
                <value>https://nuget.org/api/v2/</value>
            </setting>
            <setting name="WindowPlacement" serializeAs="String">
                <value />
            </setting>
            <setting name="PublishPrivateKey" serializeAs="String">
                <value />
            </setting>
            <setting name="PublishPackageLocation" serializeAs="String">
                <value>https://nuget.org</value>
            </setting>
            <setting name="PackageChooserDialogWidth" serializeAs="String">
                <value>630</value>
            </setting>
            <setting name="PackageChooserDialogHeight" serializeAs="String">
                <value>450</value>
            </setting>
            <setting name="IsFirstTime" serializeAs="String">
                <value>True</value>
            </setting>
            <setting name="PackageContentHeight" serializeAs="String">
                <value>400</value>
            </setting>
            <setting name="ShowTaskShortcuts" serializeAs="String">
                <value>True</value>
            </setting>
            <setting name="WordWrap" serializeAs="String">
                <value>False</value>
            </setting>
            <setting name="ShowLineNumbers" serializeAs="String">
                <value>False</value>
            </setting>
            <setting name="PublishAsUnlisted" serializeAs="String">
                <value>False</value>
            </setting>
            <setting name="ShowPrereleasePackages" serializeAs="String">
                <value>True</value>
            </setting>
            <setting name="SolicitInstallNpeForWin8" serializeAs="String">
                <value>True</value>
            </setting>
            <setting name="IsFirstTimeAfterMigrate" serializeAs="String">
                <value>True</value>
            </setting>
            <setting name="AutoLoadPackages" serializeAs="String">
                <value>True</value>
            </setting>
        </PackageExplorer.Properties.Settings>
    </userSettings>
    <system.net>
        <settings>
            <servicePointManager expect100Continue="false"/>
        </settings>
    </system.net>
    <runtime>
        <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
            <dependentAssembly>
                <assemblyIdentity name="NuGetPackageExplorer.Types" publicKeyToken="b33e3c54f0b885e9" culture="neutral"/>
                <bindingRedirect oldVersion="1.0.0.0-3.10.0.0" newVersion="3.10.0.0"/>
            </dependentAssembly>
        </assemblyBinding>
        <loadFromRemoteSources enabled="true"/>
    </runtime>
<startup><supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5"/></startup></configuration>
NuGetPackageExplorer.exe.gui
 
NuGetPackageExplorer.Types.dll
md5: 816A7EB599B6A610BB1969B8D8E65076 | sha1: 6B50ABA413FEA9D33C8E35F813B3E377A215780B | sha256: AE235B3308E7B5CBDFF359C00A303F0CB1A022CCCF586A45F34B8A0E5855C89C | sha512: 6718C42DA75830FCB40B009BABCE36B800C6B0C16B5F1A2FA289DA8282FB19310BEED4B2B7BD0FA90B7C80084303B02A2048E22889FF90DE8DCE299B1473B5E1
Ookii.Dialogs.Wpf.dll
md5: 02BE729F2B0863334120F2E50E4336B3 | sha1: C04BBBDD0D0570DF8257A44AE0746E174B7CBB80 | sha256: 9EAD9CD567CFDC16E58DA168E9C22BB367638DE4E191C205BDB4211D00D21ACE | sha512: 7008BA6EABF441D5B22F31AE8196994A5E5B13218BA4F961AF959F15FE37E499504F9E2E8AD624CA857220DFD11EF7B6DFC1ECB81A690D0693DD1E5C6E6592B6
PackageViewModel.dll
md5: 73488432C27E23016CB2E7E268474BD1 | sha1: A5709FF2F47435B618B814D2B925A3AB02F1C433 | sha256: 7799E3FD4D0DEDFC55ECA77A7A7F59F3E2170C178B144F74CA12E8D6AD0166CC | sha512: 7F0CC52B3DAA96001649F609D0A2AF3E327479C2417D6D82FDB823B5D81A24CBA620A67CB1A6EE3953A9EF494EAA7AE7DB5DD0191B540BCAA016C32588827212

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
NuGet Package Explorer 5.3.36 2342 Thursday, August 29, 2019 Approved
NuGet Package Explorer 5.2.88 2069 Monday, August 5, 2019 Approved
NuGet Package Explorer 5.2.70 1774 Sunday, July 14, 2019 Approved
NuGet Package Explorer 5.2.49 2334 Tuesday, June 11, 2019 Approved
NuGet Package Explorer 5.2.47 324 Monday, June 10, 2019 Approved
NuGet Package Explorer 5.2.15 2602 Wednesday, May 1, 2019 Approved
NuGet Package Explorer 5.0.230 1832 Monday, April 8, 2019 Approved
NuGet Package Explorer 5.0.229 954 Saturday, March 30, 2019 Approved
NuGet Package Explorer 5.0.227 322 Friday, March 29, 2019 Approved
Discussion for the Nuget Package Explorer Package

Ground Rules:

  • This discussion is only about Nuget Package Explorer and the Nuget Package Explorer package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Nuget Package Explorer, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus