Terry 01 on Fri, 23 Jan 2015 18:25:56

On my stand-alone PC, I have a number of applications that use the VS icon, and I want to change all of them to use unique icons I developed.  This will better enable me to chose the correct icon the first click.  I have read more Help files and forum responses on this subject than I care to acknowledge.  However, none of them appear to have a response that explains how to do this. 

MY PROBLEM - I can't publish any of the applications, because the signing expiration dates have expired on all of them.

How do I update/change the expiration date on these applications, so I can publish them on my stand-alone PC? 

Terry 01



Jamles Hez on Mon, 26 Jan 2015 08:41:45

Hi Terry01,

If you want to publish them on your stand-alone PC, you may want to resign the apps, see Sn.exe (Strong Name Tool) for more options.

However if your certification already expired, probably you may need to extend/renew your certification by request to your certification provider.


Terry 01 on Mon, 26 Jan 2015 13:29:55


Thanks for your response, but I'm not sure what you meant by "you may need to extend/renew your certification by request to your certification provider". I'm the owner/single user of my PC.  I believe this makes me the certification provider, so how do I "extend/renew" the certification?


Jamles Hez on Tue, 27 Jan 2015 09:01:26

Hi Terry01,

Oh, that means you generate the certification by yourself.

That make things easier, in your visual studio, I don't know which project are you working but you should be able to see the signing option in the properties page, new a strong name key file can probably help you fix the issue.


Terry 01 on Tue, 27 Jan 2015 16:49:23


When I did as you suggested, I still can't change the date.  I noticed the old strong name/temporary name remained, and I deleted it.  However, when investigating the problem, the original temporary name still shows on a number of screens.

I currently use Visual Studio 2008, and ordered VS 2013 Sunday.  I'm waiting for it to arrive before I can install it.  Will I encounter the same problem with VS 2013?  I'm willing to suspend my problem until then.

Should I delete this thread, and possibly re-open it after VS 2013 is installed, assuming I have the same problem?

Jamles Hez on Wed, 28 Jan 2015 13:49:00

Hi Terry,

Well, It's ok, I would like to suggest you ask such question at CLR forum( since your issue is more related with Application Signing Date, MSBuild is more related with build the application base on the configuration on the proj file.

Thanks for your understanding.


We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click HERE to participate the survey.