Machine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks.https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/2019-05-01T08:08:52Zhttps://api.nuget.org/v3-flatcontainer/machine.fakes.rhinomocks/2.11.0/iconhttps://www.nuget.org/packages/Machine.Fakes.RhinoMocks/2.11.02019-05-01T08:04:44Z2019-05-01T08:08:52ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks.https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/2.11.0-beta12019-04-07T08:43:18Z2019-04-07T08:47:29ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks.https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/2.10.02018-11-22T13:26:51Z2018-11-22T13:31:05ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks.https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/2.9.02017-10-15T07:53:06Z2018-11-16T04:27:44ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks.https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/2.8.02017-03-12T14:04:21Z2018-11-16T04:28:40ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks.https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/2.8.0-beta32016-08-05T14:09:58Z2018-11-16T04:27:44ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks.https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/2.7.02015-08-29T20:43:35Z2018-11-16T04:28:00ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6.1https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/2.6.02015-05-01T15:52:28Z2018-11-16T04:27:53ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6.1https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/2.5.02014-11-05T21:08:47Z2018-11-16T04:28:00ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6.1https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/2.4.02014-07-26T13:45:35Z2018-11-16T04:27:47ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6.1https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/2.3.02014-04-28T04:17:00Z2018-11-16T04:27:44ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6.1https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/2.2.02014-03-31T20:20:04Z2018-11-16T04:27:45ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6.1https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/2.1.02014-02-16T06:48:12Z2018-11-16T04:27:47ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6.1https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/2.0.02013-12-27T10:28:49Z2018-11-16T04:27:45ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6.1https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/1.8.02013-10-26T06:02:04Z2018-11-16T04:27:50ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6.1https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/1.7.02013-08-02T10:36:55Z2018-11-16T04:27:45ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6.1https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/1.6.02013-06-09T06:34:56Z2018-11-16T04:27:56ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6.1https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/1.5.02013-05-12T04:54:02Z2018-11-16T04:27:52ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6.1https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/1.4.02013-04-15T20:19:06Z2018-11-16T04:27:45ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6.1https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/1.3.02013-03-22T08:56:24Z2018-11-16T04:27:58ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6.1https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/1.2.02013-03-16T23:36:59Z2018-11-16T04:27:56ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6.1https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/1.1.02013-02-19T21:35:35Z2018-11-16T04:27:45ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6.1https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/1.0.42012-12-31T08:48:31Z2018-11-16T04:27:52ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6.1https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/1.0.32012-12-28T00:00:32Z2018-11-16T04:27:46ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6.1https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/1.0.22012-11-15T22:39:22Z2018-11-16T04:27:47ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6.1https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/1.0.12012-11-04T06:47:27Z2018-11-16T04:27:50ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6.1https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/1.0.02012-10-28T12:13:43Z2018-11-16T04:27:50ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6.1https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/0.6.02012-10-11T21:31:38Z2018-11-16T04:27:49ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6.1https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/0.5.12012-07-07T06:17:51Z2018-11-16T04:31:58ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6.1https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/0.5.02012-07-05T06:30:14Z2018-11-16T04:31:58ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6.1https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/0.4.02012-07-01T05:37:21Z2018-11-16T04:31:58ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6.1https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/0.3.52012-04-04T06:27:25Z2018-11-16T04:31:02ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6.1https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/0.3.32011-12-21T13:27:51Z2018-11-16T04:31:12ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/0.3.22011-12-21T13:18:51Z2018-11-16T04:31:02ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/0.3.12011-12-13T12:35:58Z2018-11-16T04:32:03ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/0.3.02011-11-29T16:46:21Z2018-11-16T04:32:01ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/0.2.82011-11-07T12:54:12Z2018-11-16T04:31:55ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/0.2.62011-08-27T12:03:45Z2018-11-16T04:31:17ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/0.2.52011-07-20T11:05:41Z2018-11-16T04:31:17ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/0.2.42011-07-20T09:02:19Z2018-11-16T04:31:18ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/0.2.3.32011-06-03T12:21:11Z2018-11-16T04:31:17ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/0.2.3.22011-05-17T18:07:32Z2018-11-16T04:31:29ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/0.2.3.12011-05-06T09:11:52Z2018-11-16T04:31:05ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/0.2.32011-04-18T12:12:33Z2018-11-16T04:31:04ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/0.2.2.22011-04-13T09:30:20Z2018-11-16T04:31:03ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/0.2.1.22011-04-02T17:18:24Z2018-11-16T04:31:16ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/0.2.12011-03-30T10:50:38Z2018-11-16T04:31:06ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/0.2.0.62011-03-23T16:39:36Z2018-11-16T04:31:33ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/0.2.0.52011-03-21T08:26:23Z2018-11-16T04:31:31ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/0.2.0.42011-03-14T08:42:06Z2018-11-16T04:31:33ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/0.2.0.32011-03-13T15:24:11Z2018-11-16T04:31:02ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/0.2.0.22011-03-11T17:59:55Z2018-11-16T04:31:05ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/0.2.0.12011-03-10T18:49:12Z2018-11-16T04:31:07ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/0.2.02011-03-03T13:04:09Z2018-11-16T04:31:05ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/0.1.02011-02-25T12:34:55Z2018-11-16T04:31:02ZMachine.SpecificationsMachine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks. This is the adapter for RhinoMocks 3.6https://www.nuget.org/packages/Machine.Fakes.RhinoMocks/0.0.32011-02-24T15:52:05Z2018-11-16T04:31:01ZMachine.SpecificationsGeneric faking capabilites on top of Machine.Specifications