http://www.geektieguy.com/2007/08/25/troubleshooting-clickonce-deployment-issues/ News and views from the geek tie guy. Fri, 25 Jul 2008 16:17:09 +0000 http://wordpress.org/?v=2.5.1 http://www.geektieguy.com/2007/08/25/troubleshooting-clickonce-deployment-issues/#comment-697 GeekTieGuy Thu, 06 Sep 2007 00:31:13 +0000 http://www.geektieguy.com/2007/08/25/troubleshooting-clickonce-deployment-issues/#comment-697 Good question. I can't speak for Microsoft, so I can only give you my guess. It probably has to do with the complexity of checking timestamps/file contents and whatnot. Checking the version number is a well-defined, relatively reliable, non-ambiguous way of doing things. If you're using Visual Studio, you can tell it to increment the version number automatically every time you publish your files, so it's not too much of a headache for me personally. It doesn't even have to be a major or minor version change, it can be all the way down in the revision group (1.0.0.xyz). I'd ask the question on the Microsoft MSDN forums, if I were you. Good question. I can’t speak for Microsoft, so I can only give you my guess. It probably has to do with the complexity of checking timestamps/file contents and whatnot. Checking the version number is a well-defined, relatively reliable, non-ambiguous way of doing things. If you’re using Visual Studio, you can tell it to increment the version number automatically every time you publish your files, so it’s not too much of a headache for me personally. It doesn’t even have to be a major or minor version change, it can be all the way down in the revision group (1.0.0.xyz). I’d ask the question on the Microsoft MSDN forums, if I were you.

]]> http://www.geektieguy.com/2007/08/25/troubleshooting-clickonce-deployment-issues/#comment-696 Howard Wed, 05 Sep 2007 21:47:05 +0000 http://www.geektieguy.com/2007/08/25/troubleshooting-clickonce-deployment-issues/#comment-696 Hi, maybe this is a newbie question but why does .NET require to increment the version number on everytime an application is deployed via clickonce? This is very annoying especially when I make a test version multiple times; but maybe there is some reasonable explanation. Why can't .NET recognize the new files and without generating a new version number and filling the cache up? Hi, maybe this is a newbie question but why does .NET require to increment the version number on everytime an application is deployed via clickonce? This is very annoying especially when I make a test version multiple times; but maybe there is some reasonable explanation. Why can’t .NET recognize the new files and without generating a new version number and filling the cache up?

]]>