Downloads of v 1.20:


Last Update:

02 Jul 2018

Package Maintainer(s):

Software Author(s):

  • Dseph


ewseditor admin exchange ews .net dotnet web services api

ewseditor (Install)

  • 1
  • 2
  • 3

1.20 | Updated: 02 Jul 2018



Downloads of v 1.20:



Software Author(s):

  • Dseph

  • 1
  • 2
  • 3
ewseditor (Install) 1.20

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install ewseditor (Install), run the following command from the command line or from PowerShell:


To upgrade ewseditor (Install), run the following command from the command line or from PowerShell:


To uninstall ewseditor (Install), run the following command from the command line or from PowerShell:


Deployment Method:

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

1. Enter Your Internal Repository Url

(this should look similar to

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • 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 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. Copy Your Script

choco upgrade ewseditor -y --source="'INTERNAL REPO 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 ewseditor -y --source="'INTERNAL REPO URL'" 

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

Exit $exitCode

- name: Install ewseditor
    name: ewseditor
    version: '1.20'
    state: present

See docs at

chocolatey_package 'ewseditor' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '1.20'

See docs at

cChocoPackageInstaller ewseditor
    Name     = "ewseditor"
    Version  = "1.20"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'ewseditor':
  ensure   => '1.20',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

4. 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 by moderator gep13 on 19 Jul 2018.


EWSEditor has three goals:
Demonstrate the Exchange Web Services Managed API functionality and simplicity to developers through its source code.
Demonstrate the Exchange Web Services SOAP traffic used to perform actions initiated through an explorer user interface.
Assist non-developers in debugging and understanding Exchange stores by exploring items, folders, and their properties in depth.

Each release of EWSEditor includes the distribution of the EWS Managed API it was built for. EWSEditor uses .NET Framework version 4.5.1 which can be downloaded here: .NET Framework 4.5.1. The project is under Visual Studio 2013. This version of EwsEditor uses EWS Managed API built from GIT. The EWS Managed API requires a minimal of .NET 3.5. A copy of the 2.2 version of the EWS managed API is included in case you wish to use it instead of the version built from GIT.

$ErrorActionPreference = 'Stop'; # stop on all errors

$packageName= 'ewseditor'
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url        = ''
$installDir = "c:\tools\EwsEditor\";

$packageArgs = @{
  packageName   = $packageName
  url           = $url
  unzipLocation = $installDir
  checksum      = '9FC5842FA372B8A6F4386C9BD31390C8D4B116AB3AEA68E4DA1DD3B479AF82E5'
  checksumType  = 'sha256'

Install-ChocolateyZipPackage @packageArgs
$ErrorActionPreference = 'Stop';

$packageName = 'ewseditor'
$softwareName = 'ewseditor*'

$installDir = "c:\tools\EwsEditor\";

Remove-Item $installDir -Recurse;

Log in or click on link to see number of positives.

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.

Add to Builder Version Downloads Last Updated Status
ewseditor (Install) 1.19 353 Sunday, January 7, 2018 Approved
ewseditor (Install) 1.18 386 Sunday, September 10, 2017 Approved

This package has no dependencies.

Discussion for the ewseditor (Install) Package

Ground Rules:

  • This discussion is only about ewseditor (Install) and the ewseditor (Install) 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 ewseditor (Install), 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