Downloads:

1,314

Downloads of v 1.66:

743

Last Update:

15 Nov 2016

Package Maintainer(s):

Software Author(s):

  • Nir Sofer

Tags:

exports functions dll memory address

DLL Export Viewer

1.66 | Updated: 15 Nov 2016

Downloads:

1,314

Downloads of v 1.66:

743

Maintainer(s):

Software Author(s):

  • Nir Sofer

DLL Export Viewer 1.66

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install DLL Export Viewer, run the following command from the command line or from PowerShell:

>

To upgrade DLL Export Viewer, run the following command from the command line or from PowerShell:

>

To uninstall DLL Export Viewer, 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 dllexp -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 dllexp -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 dllexp installed
  win_chocolatey:
    name: dllexp
    state: present
    version: 1.66
    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 'dllexp' do
  action    :install
  version  '1.66'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: dllexp,
    Version: 1.66,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller dllexp
{
   Name     = 'dllexp'
   Ensure   = 'Present'
   Version  = '1.66'
   Source   = 'STEP 3 URL'
}

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


package { 'dllexp':
  provider => 'chocolatey',
  ensure   => '1.66',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install dllexp version="1.66" 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.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved as a trusted package on 30 Oct 2019.

Description

This utility displays the list of all exported functions and their virtual memory addresses for the specified DLL files.

You can easily copy the memory address of the desired function, paste it into your debugger, and set a breakpoint for this memory address.

When this function is called, the debugger will stop in the beginning of this function.

For example: If you want to break each time that a message box is going to be displayed,
simply put breakpoints on the memory addresses of message-box functions: MessageBoxA, MessageBoxExA, and MessageBoxIndirectA (or MessageBoxW, MessageBoxExW, and MessageBoxIndirectW in unicode based applications)
When one of the message-box functions is called, your debugger should break in the entry point of that function, and then you can
look at call stack and go backward into the code that initiated this API call.


tools\chocolateyInstall.ps1
$packageName = 'dllexp'
$url = 'http://www.nirsoft.net/utils/dllexp.zip'
$checksum = '5a1149dc83b22f2c47600ab0f1f60c922607aaaa36feaee9c984f00ab7d96ec5'
$checksumType = 'sha256'
$url64 = 'http://www.nirsoft.net/utils/dllexp-x64.zip'
$checksum64 = '07d4ddd976679891eee2a252de585e1c101089bb4220a4cf3b221473db2bb3fd'
$checksumType64 = 'sha256'
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$installFile = Join-Path $toolsDir "$($packageName).exe"

Install-ChocolateyZipPackage -PackageName "$packageName" `
                             -Url "$url" `
                             -UnzipLocation "$toolsDir" `
                             -Url64bit "$url64" `
                             -Checksum "$checksum" `
                             -ChecksumType "$checksumType" `
                             -Checksum64 "$checksum64" `
                             -ChecksumType64 "$checksumType64"

Set-Content -Path ("$installFile.gui") `
            -Value $null

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
DLL Export Viewer 1.65 277 Saturday, March 5, 2016 Approved
DLL Export Viewer 1.63 294 Thursday, April 2, 2015 Approved

Package

  • Automatically built and uploaded by dtgm

This package has no dependencies.

Discussion for the DLL Export Viewer Package

Ground Rules:

  • This discussion is only about DLL Export Viewer and the DLL Export Viewer 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 DLL Export Viewer, 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