There might be a time in which you need to strongly name the VimServer.dll that gets created from the WSDL within the SDK. If you need help with that, check out a previous post here
I wont re-hash the previous article but will just focus on making the DLL strongly named.
The first step is to create a private/public key pair. You can do this by using the .NET SDK utility sn.exe. This will create a signing file for you, that you can now use for signing. Now, if you are going to use this is production, I would probably invest in a public cert, but for the purposes of this post, that’s not necessary :)
So lets get to creating a signing cert.
Open up a command prompt, navigate to the .NET SDK directory.
Execute the following command.
sn.exe /k c:testcert.snk
Once you have created you signing key, you will need to add it to the VimService.cs file that was generated from the WSDL. The basic steps here are to recompile the cs into a library (dll) and add the signing key to that compilation step. That can be done with the following command
From here to create the strongly named dll we can execute the following command.
csc /t:library /keyfile:c:testcert.snk
This will output a new dll with a strong name, that you can now use in your apps that need a strongly named assembly. As you can see from the screen all is good.
Hope this helps.