Unpacking Software Livestream

Join our monthly Unpacking Software livestream to hear about the latest news, chat and opinion on packaging, software deployment and lifecycle management!

Learn More

Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More

Chocolatey Coding Livestream

Join us for the Chocolatey Coding Livestream, where members of our team dive into the heart of open source development by coding live on various Chocolatey projects. Tune in to witness real-time coding, ask questions, and gain insights into the world of package management. Don't miss this opportunity to engage with our team and contribute to the future of Chocolatey!

Learn More

Calling All Chocolatiers! Whipping Up Windows Automation with Chocolatey Central Management

Webinar from
Wednesday, 17 January 2024

We are delighted to announce the release of Chocolatey Central Management v0.12.0, featuring seamless Deployment Plan creation, time-saving duplications, insightful Group Details, an upgraded Dashboard, bug fixes, user interface polishing, and refined documentation. As an added bonus we'll have members of our Solutions Engineering team on-hand to dive into some interesting ways you can leverage the new features available!

Watch On-Demand
Chocolatey Community Coffee Break

Join the Chocolatey Team as we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Watch The Replays
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand

Downloads:

6,997

Downloads of v 2.3.2:

1,438

Last Update:

12 Mar 2017

Package Maintainer(s):

Software Author(s):

  • Akira Sugiura

Tags:

tdd isolation mock mocks mocking fake fakes faking unittest unittesting

Prig - Open Source Alternative to Microsoft Fakes

  • 1
  • 2
  • 3

2.3.2 | Updated: 12 Mar 2017

Downloads:

6,997

Downloads of v 2.3.2:

1,438

Maintainer(s):

Software Author(s):

  • Akira Sugiura

Prig - Open Source Alternative to Microsoft Fakes 2.3.2

  • 1
  • 2
  • 3

This Package Contains an Exempted Check

Not All Tests Have Passed


Validation Testing Passed


Verification Testing Exemption:

Requires Visual Studio

Details

Scan Testing Successful:

No detections found in any package files

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Prig - Open Source Alternative to Microsoft Fakes, run the following command from the command line or from PowerShell:

>

To upgrade Prig - Open Source Alternative to Microsoft Fakes, run the following command from the command line or from PowerShell:

>

To uninstall Prig - Open Source Alternative to Microsoft Fakes, 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 https://community.chocolatey.org/api/v2/)


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 https://community.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. Copy Your Script

choco upgrade prig -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 prig -y --source="'INTERNAL REPO URL'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Install prig
  win_chocolatey:
    name: prig
    version: '2.3.2'
    source: INTERNAL REPO URL
    state: present

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'prig' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '2.3.2'
end

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


cChocoPackageInstaller prig
{
    Name     = "prig"
    Version  = "2.3.2"
    Source   = "INTERNAL REPO URL"
}

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


package { 'prig':
  ensure   => '2.3.2',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

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


4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

NOTE

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

Package Approved

This package was approved as a trusted package on 12 Mar 2017.

Description

Prig(PRototyping jIG) is a framework that generates a Test Double like Microsoft Fakes/Typemock Isolator/Telerik JustMock based on Unmanaged Profiler APIs. This framework enables that any methods are replaced with mocks. For example, a static property, a private method, a non-virtual member and so on.


tools\ChocolateyInstall.ps1
# 
# File: ChocolateyInstall.ps1
# 
# Author: Akira Sugiura ([email protected])
# 
# 
# Copyright (c) 2015 Akira Sugiura
#  
#  This software is MIT License.
#  
#  Permission is hereby granted, free of charge, to any person obtaining a copy
#  of this software and associated documentation files (the "Software"), to deal
#  in the Software without restriction, including without limitation the rights
#  to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
#  copies of the Software, and to permit persons to whom the Software is
#  furnished to do so, subject to the following conditions:
#  
#  The above copyright notice and this permission notice shall be included in
#  all copies or substantial portions of the Software.
#  
#  THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
#  IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
#  FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
#  AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
#  LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
#  OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
#  THE SOFTWARE.
#


'  Installing Prig.vsix...'
$packageName = 'Prig'
$vsixUrl = 'https://github.com/urasandesu/Prig/releases/download/v2.3.2/Prig.vsix'

Install-ChocolateyVsixPackage $packageName $vsixUrl
tools\ChocolateyUninstall.ps1
# 
# File: ChocolateyUninstall.ps1
# 
# Author: Akira Sugiura ([email protected])
# 
# 
# Copyright (c) 2015 Akira Sugiura
#  
#  This software is MIT License.
#  
#  Permission is hereby granted, free of charge, to any person obtaining a copy
#  of this software and associated documentation files (the "Software"), to deal
#  in the Software without restriction, including without limitation the rights
#  to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
#  copies of the Software, and to permit persons to whom the Software is
#  furnished to do so, subject to the following conditions:
#  
#  The above copyright notice and this permission notice shall be included in
#  all copies or substantial portions of the Software.
#  
#  THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
#  IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
#  FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
#  AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
#  LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
#  OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
#  THE SOFTWARE.
#


'  Uninstalling Prig.vsix...'
$vscomntoolsPaths = gci env:vs* | ? { $_.name -match 'VS\d{3}COMNTOOLS' } | sort name -Descending | % { $_.value }
if (0 -eq $vscomntoolsPaths.Length) {
    Write-Error "'VsDevCmd.bat' is not found."
    exit 1805378044
}
$vsDevCmdPath = [System.IO.Path]::Combine($vscomntoolsPaths[0], 'VsDevCmd.bat')
if (![System.IO.File]::Exists($vsDevCmdPath)) {
    Write-Error "'VsDevCmd.bat' is not found."
    exit 1805378044
}
cmd /c ('" "{0}" & vsixinstaller /q /u:0a06101d-8de3-40c4-b083-c5c16ca227ae "' -f $vsDevCmdPath)

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
Prig - Open Source Alternative to Microsoft Fakes 2.3.1 779 Sunday, August 14, 2016 Approved
Prig - Open Source Alternative to Microsoft Fakes 2.3.0 568 Friday, April 29, 2016 Approved
Prig - Open Source Alternative to Microsoft Fakes 2.2.0 454 Sunday, February 21, 2016 Approved
Prig - Open Source Alternative to Microsoft Fakes 2.1.1 394 Saturday, January 23, 2016 Approved
Prig - Open Source Alternative to Microsoft Fakes 2.1.0 425 Sunday, December 20, 2015 Approved
Prig: Open Source Alternative to Microsoft Fakes 2.0.0-alpha06 472 Friday, September 18, 2015 Exempted
Prig: Open Source Alternative to Microsoft Fakes 2.0.0-alpha05 432 Saturday, August 1, 2015 Exempted
Prig: Open Source Alternative to Microsoft Fakes 2.0.0-alpha04 470 Wednesday, May 27, 2015 Exempted
Prig: Open Source Alternative to Microsoft Fakes 2.0.0-alpha03 511 Monday, March 16, 2015 Exempted
Prig: Open Source Alternative to Microsoft Fakes 2.0.0-alpha02 467 Sunday, March 8, 2015 Exempted
Prig: Open Source Alternative to Microsoft Fakes 2.0.0-alpha01 449 Sunday, March 1, 2015 Exempted

Version 2.3.2

  • Fixed #83: Namespace / typename confusion. Added global namespace alias when Prig Assembly is generated.
  • Fixed #85: The method of generic type that has declaring type parameter excluding this cannot detour. Against the method that has the type as same as declaring the type as the signature, consider the problem that we cannot make the generic type instance that is instantiated by its generic parameter in the managed code.
  • Fixed #76: Unable to share unit test with team. Modify the processing so that adds Prig Assembly to reference the only assembly that is located at System Directory(e.g. C:\Windows) by full path.
  • Fixed #81: Support VS2013/VS2015 mixed environment. Change the machine wide installer behavior: change the target of Test Explorer for prig install from the latest Visual Studio to all versions Visual Studio.
  • Fixed #90, #91: MsTest issues. Indirection Stub is unintendedly crossed plural AppDomains by MsTest. Improve AppDomain isolation against the profiler generated code.
  • Fixed #92: Add Prig Assembly is failed immediately after installation. Set the log directory permission to everyone full control when installing.
    NOTE: You have to reinstall Prig explicitly to enable the above correction. For details, see our Wiki.

Version 2.3.1

  • Fixed #68: MSTest is crashed. This was regression by part of 6e0571f3386371e6c5404c17893038e05d6c906b.
  • Fixed #72: Problem for multi assemblies loading order(HRESULT: 0x80131124). This cause is wrong assembly identification. Add the flag that indicates whether the assembly is modifiable to determine their equality.
  • Fixed #74: Unable to register. Prig registration process didn't support except C drive. Now we support another.
  • Fix the bug that is low in reproducibility. Prig Assembly operation sometimes failed. It seems that the design of Start-Process is the reason.
  • Fix the adding Prig Assembly problem. The operation that adds Prig Assembly always failed if the target referenced assembly name is different from its project name. Until now, we had used Name property but it was wrong. To specify the assembly name, we have to use Identity property.
  • Change Chocolatey installation source from Visual Studio Gallery to GitHub. Because Visual Studio Gallery doesn't allow to keep the old version.

Version 2.3.0

  • Fixed the issue that stack trace isn't outputted in Windows 10. It seems that this correction doesn't effect against Windows 7 and Windows 8.1. There is a high probability that we used wrongly the api that handles stack trace.
  • Update middleware. NUnit is updated from 2.6.3.13283 to 2.6.4.14350.
  • Fixed #60: Don't create log directory in various places. When installing, add the environment variable to indicate the log directory. Also, remove the variable when uninstalling.
  • Fixed #62: Propose empty mock implementation for replacement target method. Improve Get-IndirectionStubSetting command more explanatorily. By the way, I added some code snippets, but it is an experiment -- possibly, they are removed at next release.
  • Fixed #64: Any Prig Assembly addition is failed in the environment that the environment variable VS###COMNTOOLS is installed only one. Fix the script bug.
  • Fixed #65: Prig cannot handle type reference generic parameter constraint. Change the AssemblyBuilderAccess of temporary assembly ReflectionOnly to Run, because it conflicts with the assembly that has been already loaded as runnable(this behavior is uncontrollable).
  • Fixed #66: Register Prig menu doesn't work in a x86 environment. Fix the behavior to choose the file path depends on the processor architecture.
  • Fixed a regression caused by Visual Studio 2015 support.
  • Fixed some potential bugs.

Version 2.2.0

  • Fixed #57: Support for Continuous Integration Server (like AppVeyor). Add some special APIs and maintenance document to explain them. For details, please see our Wiki.
  • Fixed #58: Needs more robustness for additional delegates. Ignore the additional delegate that doesn't exist, because build error occurs even if the delegate doesn't relevant.
  • Fixed potential bugs. Some multiple threads race conditions existed. These were found by Coverity.

Version 2.1.1

  • Update middleware. Boost is updated from 1.55.0 to 1.60.0.
  • Fixed infrastructure's bug. The function to parse PE header was wrong. This bug affected the environment installed Visual Studio 2015 or more. See also the comment of the issue.
  • Reduce environmental dependence. Until this improvement, Add-PrigAssembly command used absolute path instead of relative path or environment variable. So, any build will fail on another environment different from first setup without *.csproj modification.
  • Improve prig.exe help. Also, we maintain out wiki to explain it.

Version 2.1.0

  • Fixed #48: No longer need install.ps1 for NuGet. Clean up the content.
  • Fixed #49: Minimize the dependency to Chocolatey. Prig can support standalone installation via VSIX since this version.
  • Fixed #52: Support Visual Studio 2015 Update 1. Deal that the test execution engine is changed from vstest.executionengine to TE.ProcessHost.Managed.
  • Fixed some potentially bugs for prig command. It could not remove the symbolic link that has been already moved. Additionaly, improve some error messages.

Version 2.0.0

  • Fixed #31: Issue with out parameters.
  • Fixed #46: Support mocking DLL imports.
  • Against the comment-based help of Prig management commands, unified the definition of word because they were defined. See also our wiki.

Version 2.0.0-alpha06

  • Fixed #45: Support Visual Studio 2015
  • Fixed #44: Namespace reference not added for parameter that is array type
    [NOTICE] This issue has already been fixed in the family of V2. We just applied the fix to the family of V1.
  • Improve installation robustness. The ExecutionPolicy of PowerShell that is invoked during build tasks was sometimes unexpected, so modify to set explicit value.
  • Enhance supported signature. The unusual types that appear on the interface of a method is almost supported. For example, T[,][](T is a generic type parameter), List<DateTime[]>[,], out M[][,](M is a generic method parameter) and so on.
  • Prepare to support three or more out/ref parameters. By decreasing the dependencies of an indirection stub that profiler used, performance is also improved.

Version 1.1.1

  • [NOTICE] The family of v1 will be obsolete soon. We strongly recommend migrating to the family of the v2. About the way of the migration, please see our Wiki.
  • Support Visual Studio 2015.
  • Merge the fixes that were applied to the family of the v2.

Version 2.0.0-alpha05

  • Improve stability for the methods of the classes that are used on the boundary of application domains(e.g. AppDomain, BinaryReader, MemoryStream, Thread and so on).
  • Improve usability for the command to manage Prig a little(See also the Wiki).
  • Merge Infrastructure Bug Fix(See also Swathe issues #2)
  • Make the sequence that builds the indirection stub dll more efficient.

About more previous versions, please see https://github.com/urasandesu/Prig/releases.


This package has no dependencies.

Discussion for the Prig - Open Source Alternative to Microsoft Fakes Package

Ground Rules:

  • This discussion is only about Prig - Open Source Alternative to Microsoft Fakes and the Prig - Open Source Alternative to Microsoft Fakes 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 Prig - Open Source Alternative to Microsoft Fakes, 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