Downloads:

1,038

Downloads of v 1.1:

1,038

Last Update:

25 Jul 2013

Package Maintainer(s):

Software Author(s):

  • OpenXMLDeveloper

Tags:

officecustomuieditor office customui ribbon xml

Custom UI Editor for Microsoft Office

1.1 | Updated: 25 Jul 2013

Downloads:

1,038

Downloads of v 1.1:

1,038

Maintainer(s):

Software Author(s):

  • OpenXMLDeveloper

Custom UI Editor for Microsoft Office 1.1

Some Checks Have Failed or Are Not Yet Complete

1 Test Unknown and 1 Failing Test


Validation Testing Unknown


Verification Testing Failed

Details

To install Custom UI Editor for Microsoft Office, run the following command from the command line or from PowerShell:

>

To upgrade Custom UI Editor for Microsoft Office, run the following command from the command line or from PowerShell:

>

To uninstall Custom UI Editor for Microsoft Office, 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 officecustomuieditor -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 officecustomuieditor -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 officecustomuieditor installed
  win_chocolatey:
    name: officecustomuieditor
    state: present
    version: 1.1
    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 'officecustomuieditor' do
  action    :install
  version  '1.1'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: officecustomuieditor,
    Version: 1.1,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller officecustomuieditor
{
   Name     = 'officecustomuieditor'
   Ensure   = 'Present'
   Version  = '1.1'
   Source   = 'STEP 3 URL'
}

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


package { 'officecustomuieditor':
  provider => 'chocolatey',
  ensure   => '1.1',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install officecustomuieditor version="1.1" 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 submitted prior to moderation and has not been approved. While it is likely safe for you, there is more risk involved.

Description

>There are times that you use the same basic structure of XML in different documents. For example, the XML for the <customUI> element and the <ribbon> element are the same for all Microsoft Office applications that support the Ribbon. It can be tiresome to have to type in the same information for each use. To eliminate this need, you can use the Custom UI Editor to store and access custom templates.


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

This package has no dependencies.

Discussion for the Custom UI Editor for Microsoft Office Package

Ground Rules:

  • This discussion is only about Custom UI Editor for Microsoft Office and the Custom UI Editor for Microsoft Office 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 Custom UI Editor for Microsoft Office, 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