Should I remove FARO LS 1. FARO Technologies This is the software driver and associated device control package for the FARO LS color laser scanner. Cook Computing. April 1, 2. Written by Charles Cook. I received a couple of emails recently asking how to implement an XML RPC service in an ASP. Developer weblog mainly focused on. NET and XMLRPC. Should I remove ISO Creator 1. BunnyWabbit Learn how to remove ISO Creator 1. Introduction 1. 1 What is XMLRPC To quote the XMLRPC. Its a spec and a set of implementations that allow software running on disparate operating. Cookcomputing.Xmlrpcv2' title='Cookcomputing.Xmlrpcv2' />NET MVC application. In case anyone is interested this is how to do it this is an expanded version of an earlier post. Define an interface for your XML RPC service, for example using Cook. Computing. Xml. Rpc. IState. Name. Xml. Rpc. Methodexamples. State. Name. string Get. State. Nameint state. Number. Implement the service using Cook. Computing. Xml. Rpc. State. Name. Service Xml. Rpc. Service, IState. Comunidade Internacional Da Zona Sul 10 Anos more. Name. public string Get. State. Nameint state. Number. if state. Number lt 1 state. Number mstate. Names. Length. throw new Xml. Rpc. Fault. Exception1, Invalid state number. Namesstate. Number 1. Names. Alabama, Alaska, Arizona, Arkansas. California, Colorado, Connecticut, Delaware, Florida. Georgia, Hawaii, Idaho, Illinois, Indiana, Iowa. Kansas, Kentucky, Lousiana, Maine, Maryland, Massachusetts. Michigan, Minnesota, Mississipi, Missouri, Montana. Nebraska, Nevada, New Hampshire, New Jersey, New Mexico. New York, North Carolina, North Dakota, Ohio, Oklahoma. Oregon, Pennsylviania, Rhose Island, South Carolina. South Dakota, Tennessee, Texas, Utah, Vermont, Virginia. Washington, West Virginia, Wisconsin, Wyoming. Implement a custom route handler using System. Web. using System. Web. Routing. public class State. Name. Route. Handler IRoute. Handler. public IHttp. Handler Get. Http. HandlerRequest. Context request. Context. return new State. Name. Service. Register the custom route in global. Register. RoutesRoute. Collection routes. Ignore. Routeresource. Info. routes. Addnew Routeapistatename, new State. Name. Route. Handler. Check that everything is working by pointing your browser to the url for the handler, for example something like http localhost 3. Visual Studio. You should then see an automatically generated help page for the service. If this is ok then point your XML RPC client to the service and start making calls. March 1. 0, 2. 01. Written by Charles Cook. The Problem. Dealing with Now and why Im almost done with C and Java Karl Seguins post about how the way you code is a by product of the progamming language you use discusses how difficult it is to test unit code like this in C var audit new Audit. User. Name user. Name. Dated Date. Time. Now. The following test might work or not, depending on how quickly the code runs public void It. Sets. The. Audit. Time. To. Right. Now. Create. Audit. Itemnew UserName Leto. Dated. Should. EqualDate. Time. Now. Unfortunately its difficult to mock Date. Time. Now because its a static method, which leads to more complicated solutions such as injecting an abstract dependency into objects or using a C lambda such as Ayendes System. Time class public static class System. Time. public static Funclt Date. Time Now Date. Time. Now. This allows you to write test code like this System. Time. Now new Date. Time2. 00. 0,1,1. Reset. Failuresfailed. Msgs. System. Time. Now new Date. Time2. Get. All. Ready. Messages. Assert. Are. Equal2, msgs. Length. Another solution mentioned in the posts comments is to use NUnits Within Assert. Thataudit. Dated, Is. Equal. ToDate. Time. Now. Withinnew Time. Span0, 0, 0, 0, 5. This works, sort of, but isnt a general solution to this type of problem. Visual Studio 1. 1 Fakes. Some of the comments mention Type. Mock Isolator and the Moles project from Microsoft, and it so happens the Visual Studio 1. Moles has been productized into Visual Studio as the Fakes Framework. This can inject two types of dummy implementation into unit tests stub types for interfaces and overridable methods, and shim types for static and non overridables methods Stub types Stub types make it easy to test code that consumes interfaces or non sealed classes with overridable methods. A stub of the type T provides a default implementation of each virtual member of T, that is, any non sealed virtual or abstract method, property, or event. The default behavior can be dynamically customized for each member by attaching a delegate to a corresponding property of the stub. Octopus Dad Game. A stub is realized by a distinct type which is generated by the Fakes Framework. As a result, all stubs are strongly typed. Although stub types can be generated for interfaces and non sealed classes with overridable methods, they cannot be used for static or non overridable methods. To address these cases, the Fakes Framework also generates shim types. Shim types Shim types allow detouring of hard coded dependencies on static or non overridable methods. A shim of type T can provide an alternative implementation for each non abstract member of T. The Fakes Framework will redirect method calls to members of T to the alternative shim implementation. The shim types rely on runtime code rewriting that is provided by a custom profiler. Delegates Both stub types and shim types allow you to use delegates to dynamically customize the behavior of individual stub members. Faking Date. Time. To test the Date. Time code, create a unit test project and right click on one of the referenced assemblies in Solution Explorer. This displays a context menu which has an Add Fakes Assembly. Select this and two more referenced assemblies are automatically added to the project Microsoft. Quality. Tools. Testing. Fakes. Microsoft. Visual. Studio. Quality. Tools. Unit. Test. Framework. 1. 0. 0. Fakes. Visual Studio will automatically generate a file called Microsoft. Visual. Studio. Quality. Tools. Unit. Test. Framework. fakes in a directory in the project called Fakes. This XML file is used to configure the assembly for which fakes are generated and the namespaces and types that are included. We want to generate a shim type for Date. Time so we can change the file to specify the mscorlib assembly lt Fakes xmlnshttp schemas. Assembly Namemscorlib. Building the project results in Visual Studio creating an assembly containing the fake types in the Fakes. Assemblies directory. We need to then add a reference to this assembly so we can use the fake types in our test. So, say we have this code under test public class Audit. User. Name get set. Date. Time Dated get set. Test. Class. public static Audit Create. Audit. Itemstring user. Name. var audit new Audit User. Name user. Name, Dated Date. Time. Now. return audit. We can now write this unit test using System. System. Fakes. using Microsoft. Quality. Tools. Testing. Fakes. using Microsoft. Visual. Studio. Test. Tools. Unit. Testing. Audit. Tests. Test. Method. public void It. Sets. The. Audit. Time. To. Right. Now. Shims. Context to control. Shims. Context. Create. Date. Time. Now to return January 1st of 2. Shim. Date. Time. Now. Get new Date. Time2. 00. 0, 1, 1. Test. Class. Create. Audit. ItemLeto. Assert. Are. Equalaudit. Dated, Date. Time. Now. Calling Shims. Context. Create within the context of a using statement means that the shim will be de registered before the test function exits. If this is not done the shim will remain active for subsequent test and so might cause them to run in an unexpected way. Although this doesnt address the limitations of C that Karl described in his post assuming you see them as limitations, at least were not having to modify the original code using Date. Time. Now to make it testable. Once the fakes are configured in a test project writing tests using the fakes is straightforward. Testing Time. While Karls post was not really about the problem of mocking Date. Time. Now in itself, it is a good example of a non deterministic test that can cause problems.