Downloads:

297

Downloads of v 5.5.0.3:

297

Last Update:

27 Feb 2019

Package Maintainer(s):

Software Author(s):

  • mooglie

Tags:

worldwide-telescope worldwide world wide telescope astronomy

WorldWide Telescope Windows Client

5.5.0.3 | Updated: 27 Feb 2019

Downloads:

297

Downloads of v 5.5.0.3:

297

Maintainer(s):

Software Author(s):

  • mooglie

WorldWide Telescope Windows Client 5.5.0.3

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install WorldWide Telescope Windows Client, run the following command from the command line or from PowerShell:

>

To upgrade WorldWide Telescope Windows Client, run the following command from the command line or from PowerShell:

>

To uninstall WorldWide Telescope Windows Client, 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 worldwide-telescope -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 worldwide-telescope -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 worldwide-telescope installed
  win_chocolatey:
    name: worldwide-telescope
    state: present
    version: 5.5.0.3
    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 'worldwide-telescope' do
  action    :install
  version  '5.5.0.3'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: worldwide-telescope,
    Version: 5.5.0.3,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller worldwide-telescope
{
   Name     = 'worldwide-telescope'
   Ensure   = 'Present'
   Version  = '5.5.0.3'
   Source   = 'STEP 3 URL'
}

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


package { 'worldwide-telescope':
  provider => 'chocolatey',
  ensure   => '5.5.0.3',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install worldwide-telescope version="5.5.0.3" 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 by moderator gep13 on 28 Feb 2019.

Description

WorldWide Telescope

The purpose of the American Astronomical Society's WorldWide Telescope project is to enable the seamless visualization and sharing of scientific data and stories from major telescopes, observatories, and institutions among students and researchers, through science museums and full-dome immersive planetariums, and in scholarly publications.


tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop';
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url        = 'https://wwtweb.blob.core.windows.net/drops/WWTSetup.5.5.03.msi'

#===============================================================================
# Ensure that user is not on Windows XP/Vista
#
# The following version check code is lifted straight from the 'powershell' install script
#===============================================================================

$osversionLookup = @{
  "5.1.2600" = "XP";
  "5.1.3790" = "2003";
  "6.0.6001" = "Vista/2008";
  "6.1.7600" = "Win7/2008R2";
  "6.1.7601" = "Win7 SP1/2008R2 SP1"; # SP1 or later.
  "6.2.9200" = "Win8/2012";
  "6.3.9600" = "Win8.1/2012R2";
  "10.0.*" = "Windows 10/Server 2016"
}

$os = Get-WmiObject Win32_OperatingSystem
$osVersion = $os.version

$ProductName = (Get-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion' -Name 'ProductName').ProductName
$EditionId = (Get-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion' -Name 'EditionID').EditionId

#This will show us if we are running on Nano Server (Kernel version alone won't show this)
Write-Output "Running on: $ProductName, ($EditionId), Windows Kernel: $osVersion"

if( ([version]$osVersion).Major -eq "10" ) {
  $osVersion = "$(([version]$osVersion).Major).$(([version]$osVersion).Minor).*"
}

switch ($osversionLookup[$osVersion]) {
  "XP" {
    throw "$packageName is not supported on $ProductName, ($EditionId), Windows Kernel: $osVersion"
  }
  "2003" {
    throw "$packageName is not supported on $ProductName, ($EditionId), Windows Kernel: $osVersion"
  }
  "Vista/2008" {
    throw "$packageName is not supported on $ProductName, ($EditionId), Windows Kernel: $osVersion"
  }
}
#===============================================================================

# Windows version is OK, proceed

$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  unzipLocation = $toolsDir
  fileType      = 'MSI'
  url           = $url
  softwareName  = 'WorldWide Telescope'
  checksum      = '47FE3DAFB826898331998C6FD4612526B25AB842B3B01E9C8B318D80100D73E7'
  checksumType  = 'sha256'
  silentArgs    = "/qn /norestart /l*v `"$($env:TEMP)\$($packageName).$($env:chocolateyPackageVersion).MsiInstall.log`" AUTOUPDATE=0"
  validExitCodes= @(0, 3010, 1641)
}

Install-ChocolateyPackage @packageArgs

# Disable automatic updates (direct registry update since the AUTOUPDATE=0 MSI parameter is ignored by the installer)
# https://github.com/WorldWideTelescope/wwt-windows-client/issues/133
$path = "HKCU:\Software\Microsoft\WorldWide Telescope"
if (Test-Path $path) {
  New-ItemProperty -Path $path -Name "AutoUpdates" -Value 0 -PropertyType DWORD -Force
}

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.

Version Downloads Last Updated Status

This package has no dependencies.

Discussion for the WorldWide Telescope Windows Client Package

Ground Rules:

  • This discussion is only about WorldWide Telescope Windows Client and the WorldWide Telescope Windows Client 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 WorldWide Telescope Windows Client, 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