namespace SampleAddIn
{
    using NUnit.Core.Extensibility;

    [NUnitAddin(Name = "SampleAddIn", Description = "This is a Sample AddIn")]
    public class SampleNUnitAddin : IAddin
    {
        #region IAddin Members

        public bool Install(IExtensionHost host)
        {
            return true;
        }

        #endregion
    }
}

You can install the Addin, by copying the assembly to bin\Addins folder, relative to NUnit installation directory. You can verify your addin by starting NUnit, Tools > Addins menu.

Registered AddIns Dialog

This Addin does nothing. It simply registers itself to NUnit. You can more details about NUnit Addins here
If you are using VS2010, then please make sure your target framework is .Net 2.0. Otherwise Addin won’t work.

First we need to create a class library. Set the ComVisible attribute to true in the AssemblyInfo.cs manually.

[assembly: ComVisible(true)]

Or you can do it using Properties > Application Tab and select Assembly Information, from the Assembly Information dialog, Check the Make assembly COM-Visible check box.

Make Assembly COM Visible option from Assembly Information dialog

Build the assembly. Now we need register the assembly. We can do it using RegAsm.exe. If your OS in 64 bit, then you need to use Regasm command from Framework64 folder(Normally it will be C:\Windows\Microsoft.NET\Framework64\ folder). For running RegAsm command it is recommended to sign the assembly. You can Sign the assembly Properties > Signing Tab.

Sign Assembly option

As RegAsm command add / update information to Windows Registry, you need to run the RegAsm command as Administrator, otherwise it will not work.

You can register the assembly using following command, like this

regasm /codebase assemblyname.dll

You can unregister the assembly using RegAsm command, like this

regasm /u assemblyname.dll

That’s it. Now you can create the object of the .net assembly in VBScript. Like this, it will add 10 and 20 using C# Add method and returns the value.

Dim calcLib
Set calcLib = CreateObject("CalcLib.Math")
Dim result
result = calcLib.Add (10 , 20)
msgbox result

And here is the C# Class, which we are invoked from VBScript.

namespace CalcLib
{
    public class Math
    {
        public int Add(int number1, int number2)
        {
            return number1 + number2;
        }
    }
}

Happy Coding

string baseAddress = "net.tcp://localhost:8080/MyService1";
Uri[] addresses = { new Uri(baseAddress) };
using (var serviceHost = new ServiceHost(typeof(Service), addresses))
{
    var nettcpbinding = new NetTcpBinding();
    nettcpbinding.PortSharingEnabled = true;
    serviceHost.AddServiceEndpoint(typeof(IService),
        nettcpbinding, "IService");

    serviceHost.Open();
    Console.ReadKey(true);
    serviceHost.Close();
}

Also even if set the PortSharingEnabled to true, we also require to start the Net.Tcp port sharing service from the control panel. By default it will be disabled. If the service not started, and your tried to listen two services in same port number, you may get an exception like this AddressAlreadyInUseException – There is already a listener on IP endpoint 0.0.0.0:8080. This could happen if there is another application already listening on this endpoint or if you have multiple service endpoints in your service host with the same IP endpoint but with incompatible binding configurations.

Net.Tcp port sharing service in Services console.

You can also set the property via App.Config file also.

<bindings>
    <netTcpBinding>
        <binding portSharingEnabled="true" />
    </netTcpBinding>
</bindings>

Now you are able to run two services with same port number, in this port number 8080.

Happy Programming

MS Test running command line

Today while working on some regression build issues, me and my lead noticed one problem with MS Tests, we are running MSTest.exe from commandline to execute few tests. The problem was MSTest.exe was is not copying all the referenced assemblies to the Out folder, and this is causing failures. We initially thought the issue with commandline MSTest.exe, because all these test cases were running fine, when we run same using Visual Studio IDE. All the required assemblies are referenced to the test project, because of that we didn’t tried the DeploymentItem attribute. We tried the various MSTest commandline switches, but nothing worked. Later we found the issue, it was because of the referenced assemblies was not being used in the test. The problem fixed by creating instance of the all required assemblies in the test cases.

Thanks to Raghu Happy unit testing.

Plug-in Error occured - Messagebox from Windows Live Writer

It only shows the exception message, not the stack trace or any other information which helps to find the exception. For debugging, you need to attach the Windows Live writer to Visual Studio(we may need to run visual studio as Administrator) using Attach Process feature of Visual Studio from Debug menu.

Attach Windows Live Writer to Visual Studio

Happy Programming.