I'm having problems getting my mobile device (Windows Mobile 6.1) to see my VB.NET application as genuine.
Here are the steps I am taking - can anybody see why there is a problem?
I use makecert.exe to create a new root certificate....
makecert -n "CN=McLernonsMARS" -r -sv McLernonsMARS.pvk McLernonsMARS.cer
Next I use cert2spc.exe to create the spc file....
cert2spc.exe McLernonsMARS.cer McLernonsMARS.spc
Now I use pvk2pfx.exe to create my pfx file....
pvk2pfx.exe -pvk McLernonsMARS.pvk -pi mypassword -spc \McLernonsMARS.spc -pfx McLernonsMARS.pfx -po mypassword
I import the pfx onto my development machine (automatically determine the certificate store)
I use this pfx file to sign all the dll's and the exe which forms the output of my VB.NET project (VS2008 - My Project - Devices - Authenticode signing - select the imported pfx) and I recompile the project.
On the mobile device I import the .cer file created above into the root certificate store.
I then copy all the dll's and the .exe to the mobile device and attempt to run it. (Note that I dont use a CAB file to deploy the application).
I still keep getting the annoying messages about attempting to run an application from an untrusted publisher. Any ideas why this might be the case?