Downloads of v 4.5
Developed By Microsoft. The CLR Profiler is a free tool to profile their .NET applications.
To install Microsoft CLR Profiler, run the following command from the command line or from PowerShell:
C:\> choco install clrprofiler
To upgrade Microsoft CLR Profiler, run the following command from the command line or from PowerShell:
C:\> choco upgrade clrprofiler
## Summary How do I create packages? See https://github.com/chocolatey/choco/wiki/CreatePackages If you are submitting packages to the community feed (https://chocolatey.org) always try to ensure you have read, understood and adhere to the create packages wiki link above. ## Automatic Packages? Consider making this package an automatic package, for the best maintainability over time. Read up at https://github.com/chocolatey/choco/wiki/AutomaticPackages ## Shim Generation Any executables you include in the package or download (but don't call install against using the built-in functions) will be automatically shimmed. This means those executables will automatically be included on the path. Shim generation runs whether the package is self-contained or uses automation scripts. By default, these are considered console applications. If the application is a GUI, you should create an empty file next to the exe named 'name.exe.gui' e.g. 'bob.exe' would need a file named 'bob.exe.gui'. See https://github.com/chocolatey/choco/wiki/CreatePackages#how-do-i-set-up-batch-redirects-for-applications-that-have-a-gui If you want to ignore the executable, create an empty file next to the exe named 'name.exe.ignore' e.g. 'bob.exe' would need a file named 'bob.exe.ignore'. See https://github.com/chocolatey/choco/wiki/CreatePackages#how-do-i-exclude-executables-from-getting-batch-redirects ## Self-Contained? If you have a self-contained package, you can remove the automation scripts entirely and just include the executables, they will automatically get shimmed, which puts them on the path. Ensure you have the legal right to distribute the application though. See https://github.com/chocolatey/choco/wiki/Legal. You should read up on the Shim Generation section to familiarize yourself on what to do with GUI applications and/or ignoring shims. ## Automation Scripts You have a powerful use of Chocolatey, as you are using PowerShell. So you can do just about anything you need. Choco has some very handy built-in functions that you can use, these are sometimes called the helpers. ### Built-In Functions https://github.com/chocolatey/choco/wiki/HelpersReference A note about a couple: * Get-BinRoot - this is a horribly named function that doesn't do what new folks think it does. It gets you the 'tools' root, which by default is set to 'c:\tools', not the chocolateyInstall bin folder. * Install-BinFile - used for non-exe files - executables are automatically shimmed... * Uninstall-BinFile - used for non-exe files - executables are automatically shimmed ### Getting package specific information Use the package parameters pattern - see https://github.com/chocolatey/choco/wiki/How-To-Parse-PackageParameters-Argument ### Need to mount an ISO? https://github.com/chocolatey/choco/wiki/How-To-Mount-An-Iso-In-Chocolatey-Package ### Environment Variables Chocolatey makes a number of environment variables available (You can access any of these with $env:TheVariableNameBelow): * TEMP = Overridden to the CacheLocation, but may be the same as the original TEMP folder * ChocolateyInstall = Top level folder where Chocolatey is installed * chocolateyPackageName = The name of the package, equivalent to the id in the nuspec (0.9.9+) * chocolateyPackageVersion = The version of the package, equivalent to the version in the nuspec (0.9.9+) * chocolateyPackageFolder = The top level location of the package folder #### Advanced Environment Variables The following are more advanced settings: * chocolateyPackageParameters = (0.9.8.22+) * CHOCOLATEY_VERSION = The version of Choco you normally see. Use if you are 'lighting' things up based on choco version. (0.9.9+) - Otherwise take a dependency on the specific version you need. * chocolateyForceX86 = If available and set to 'true', then user has requested 32bit version. (0.9.9+) - Automatically handled in built in Choco functions. * OS_PLATFORM = Like Windows, OSX, Linux. (0.9.9+) * OS_VERSION = The version of OS, like 6.1 something something for Windows. (0.9.9+) * OS_NAME = The reported name of the OS. (0.9.9+) * IS_PROCESSELEVATED = Is the process elevated? (0.9.9+) #### Experimental Environment Variables The following are experimental or use not recommended: * OS_IS64BIT = This may not return correctly - it may depend on the process the app is running under (0.9.9+) * CHOCOLATEY_VERSION_PRODUCT = the version of Choco that may match CHOCOLATEY_VERSION but may be different (0.9.9+) - it's based on git describe * IS_ADMIN = Is the user an administrator? But doesn't tell you if the process is elevated. (0.9.9+) * chocolateyInstallOverride = Not for use in package automation scripts. (0.9.9+) * chocolateyInstallArguments = the installer arguments meant for the native installer. You should use chocolateyPackageParameters intead. (0.9.9+)
$ErrorActionPreference = 'Stop'; $packageName= 'CLR Profiler' $toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)" $url = 'https://clrprofiler.codeplex.com/downloads/get/532810' $checksum = 'E024DFEEDFE19B5BC1198BA34E14B9A7' $desktop = $([System.Environment]::GetFolderPath([System.Environment+SpecialFolder]::DesktopDirectory)) Install-ChocolateyZipPackage 'clrprofiler' $url $toolsDir -checksum $checksum Install-ChocolateyShortcut -shortcutFilePath "$($desktop)\clrprofiler.lnk" -targetPath "$($toolsDir)\64\CLRProfiler.exe"
Virus Scan Results
- clrprofiler.4.5.nupkg (4fd5a4894b53) - ## / 57 - Log in or click on link to see number of positives
- CLRProfiler45Binaries.zip (0b94824109af) - ## / 59 - Log in or click on link to see number of positives
This package has no dependencies.
|Microsoft CLR Profiler 18.104.22.16880517||8641||Thursday, May 17, 2018||approved|
|Microsoft CLR Profiler 4.5||1089||Tuesday, January 19, 2016||approved|
Discussion for the Microsoft CLR Profiler Package
- This discussion is only about Microsoft CLR Profiler and the Microsoft CLR Profiler 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 Microsoft CLR Profiler, 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.