<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Draft version of a new .NET Framework setup verification tool available for download</title><link>http://blogs.msdn.com/astebner/archive/2008/03/03/8015158.aspx</link><description>A while ago, I published a .NET Framework setup verification tool that can be run to provide a sanity check of the install state of the .NET Framework 1.0, 1.1 and 2.0 on a system. However, there are some limitations in that tool: It does not support</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>A nice to know...</title><link>http://blogs.msdn.com/astebner/archive/2008/03/03/8015158.aspx#8021151</link><pubDate>Tue, 04 Mar 2008 10:27:33 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8021151</guid><dc:creator>JeroenV</dc:creator><description>&lt;p&gt;I've used this tool before to check if a certain version of .NET was installed on my system: &lt;a rel="nofollow" target="_new" href="http://www.asoft.be/prod_netver.html"&gt;http://www.asoft.be/prod_netver.html&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;It is very easy for users to find out if they have a particular version, and if even provides links to the download site of the particular version if it's needed to install.&lt;/p&gt;
&lt;p&gt;For the .NET developers they allow you to distribute it along with their tools.&lt;/p&gt;
&lt;p&gt;My 2cts&lt;/p&gt;</description></item><item><title>re: Draft version of a new .NET Framework setup verification tool available for download</title><link>http://blogs.msdn.com/astebner/archive/2008/03/03/8015158.aspx#8030750</link><pubDate>Tue, 04 Mar 2008 20:35:02 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8030750</guid><dc:creator>astebner</dc:creator><description>&lt;p&gt;Hi JeroenV - Thanks for sending the link to this utility. &amp;nbsp;I can't tell how in-depth this tool goes in checking the install state of the .NET Framework though.&lt;/p&gt;
&lt;p&gt;I have run into cases in the past where the registry value that is officially documented as the way to detect the .NET Framework install state exists, yet something is wrong with the install and it doesn't work correctly. &amp;nbsp;That is the type of scenario I was targeting when I created the verification tool described in this blog post.&lt;/p&gt;
</description></item><item><title>re: Draft version of a new .NET Framework setup verification tool available for download</title><link>http://blogs.msdn.com/astebner/archive/2008/03/03/8015158.aspx#8074522</link><pubDate>Thu, 06 Mar 2008 20:26:59 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8074522</guid><dc:creator>lrios80</dc:creator><description>&lt;p&gt;Does this verification tool check the integrity of the .NET files (check to see if any files might be corrupted), or does it only check if the files are installed?&lt;/p&gt;</description></item><item><title>re: Draft version of a new .NET Framework setup verification tool available for download</title><link>http://blogs.msdn.com/astebner/archive/2008/03/03/8015158.aspx#8084130</link><pubDate>Fri, 07 Mar 2008 05:21:39 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8084130</guid><dc:creator>astebner</dc:creator><description>&lt;p&gt;Hi Lrios80 - Currently, the tool only checks for the existence of files in specified locations. &amp;nbsp;I am open to suggestions regarding checking for corruption. &amp;nbsp;The previous version of the tool contained some checksum information that it would compute and compare against, but that logic doesn't work if any service packs or hotfixes are installed for the .NET Framework. &amp;nbsp;Do you know of any other ways to check for file corruption from a tool like this?&lt;/p&gt;
&lt;p&gt;Also, have you run into cases where files have gotten corrupted for the .NET Framework? &amp;nbsp;If so, do you have any more information about how that happened and how you figured out the root cause?&lt;/p&gt;
</description></item><item><title>re: Draft version of a new .NET Framework setup verification tool available for download</title><link>http://blogs.msdn.com/astebner/archive/2008/03/03/8015158.aspx#8100189</link><pubDate>Fri, 07 Mar 2008 18:36:06 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8100189</guid><dc:creator>lrios80</dc:creator><description>&lt;p&gt;I've run into some cases where programs would not load, so .NET had to be uninstalled then reinstalled or repaired before it would work. The only time I've been able to find a specific cause for it was when SP1 for .NET 2.0 was downloaded and installed and the installation failed. (I'm not sure if this would be file corruption or if some files were removed when SP1 tried to install and then were not restored when the installation failed.) .NET 2.0 had to be completely uninstalled then reinstalled. &lt;/p&gt;</description></item><item><title>re: Draft version of a new .NET Framework setup verification tool available for download</title><link>http://blogs.msdn.com/astebner/archive/2008/03/03/8015158.aspx#8101519</link><pubDate>Fri, 07 Mar 2008 19:30:50 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8101519</guid><dc:creator>astebner</dc:creator><description>&lt;p&gt;Hi Lrios80 - Thanks for providing more details about this scenario. &amp;nbsp;I'll keep an eye out and see if I run into any similar .NET Framework 2.0 SP1 failures and check out the exact state of the files that are a part of the .NET Framework in that case. &amp;nbsp;If you run into this again, can you also try out the new verification tool and see if it reports any errors that might help narrow this down further?&lt;/p&gt;
&lt;p&gt;It would also help if you could send me any log files you have from one of these failures - the .NET Framework 2.0 SP1 creates a verbose log named %temp%\dd_net_framework*.txt during installation. &amp;nbsp;You can send the log to Aaron.Stebner (at) microsoft (dot) com.&lt;/p&gt;
</description></item><item><title>Unified .NET Framework Troubleshooting Guide</title><link>http://blogs.msdn.com/astebner/archive/2008/03/03/8015158.aspx#8342285</link><pubDate>Fri, 28 Mar 2008 22:31:26 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8342285</guid><dc:creator>Aaron Stebner's WebLog</dc:creator><description>&lt;p&gt;Details about the .NET Framework 2.0 setup packaging Available command line switches for .NET Framework&lt;/p&gt;
</description></item><item><title>re: Draft version of a new .NET Framework setup verification tool available for download</title><link>http://blogs.msdn.com/astebner/archive/2008/03/03/8015158.aspx#8401161</link><pubDate>Thu, 17 Apr 2008 08:07:58 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8401161</guid><dc:creator>szilvaa</dc:creator><description>&lt;p&gt;Regarding how you could check the integrity of the files: could you verify the digital signature? I suppose hotfixes keep that up to date.&lt;/p&gt;</description></item><item><title>re: Draft version of a new .NET Framework setup verification tool available for download</title><link>http://blogs.msdn.com/astebner/archive/2008/03/03/8015158.aspx#8403703</link><pubDate>Thu, 17 Apr 2008 19:41:23 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8403703</guid><dc:creator>astebner</dc:creator><description>&lt;p&gt;Hi Szilvaa - Yes, I think that would help for files that are digitally signed. &amp;nbsp;I'm not sure it fully guarantees that the files are not corrupt, but it would be a step in the right direction. &amp;nbsp;The trick there is that not all files in the .NET Framework are digitally signed, so the tool would need to keep track of which ones are and which ones aren't. &amp;nbsp;I'll look into options for doing something like this in the future.&lt;/p&gt;
</description></item><item><title>re: Draft version of a new .NET Framework setup verification tool available for download</title><link>http://blogs.msdn.com/astebner/archive/2008/03/03/8015158.aspx#8970304</link><pubDate>Tue, 30 Sep 2008 17:03:06 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8970304</guid><dc:creator>elguido</dc:creator><description>&lt;p&gt;Hi Aaron&lt;/p&gt;
&lt;p&gt;Is there a nice way to use your tool to scan dotnet installs across a LAN (assuming authentication requirement has been met)?&lt;/p&gt;
&lt;p&gt;Currently the best we have is the prospect of rclienting and running against network share and collating on network share.&lt;/p&gt;
&lt;p&gt;Your thoughts would be most welcome.&lt;/p&gt;
&lt;p&gt;Cheers,&lt;/p&gt;
&lt;p&gt;G&lt;/p&gt;</description></item><item><title>re: Draft version of a new .NET Framework setup verification tool available for download</title><link>http://blogs.msdn.com/astebner/archive/2008/03/03/8015158.aspx#8970540</link><pubDate>Tue, 30 Sep 2008 20:54:14 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8970540</guid><dc:creator>astebner</dc:creator><description>&lt;p&gt;Hi Elguido - This verification tool is designed to run on the local computer and return results from that computer. &amp;nbsp;It doesn't support running remotely across a network. &amp;nbsp;What I'd suggest doing here is scheduling some kind of job/task to run the tool on the machines on your network, and then collect the logs it creates and upload them to a network share for centralized analysis. &amp;nbsp;Hopefully this will be feasible in your scenario.&lt;/p&gt;
</description></item><item><title>re: Draft version of a new .NET Framework setup verification tool available for download</title><link>http://blogs.msdn.com/astebner/archive/2008/03/03/8015158.aspx#8971433</link><pubDate>Wed, 01 Oct 2008 14:32:17 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8971433</guid><dc:creator>elguido</dc:creator><description>&lt;p&gt;That could work for us, thanks Aaron.&lt;/p&gt;
&lt;p&gt;The only reason I asked is your method involves loads of signoffs and the like, the approach I'm heading from is something that the frontline support staff (of which I am a member) can organize on their own users.&lt;/p&gt;
&lt;p&gt;If there is any scope to handle UNCs that'd be excellent?&lt;/p&gt;
&lt;p&gt;Cheers,&lt;/p&gt;
&lt;p&gt;G&lt;/p&gt;</description></item><item><title>【日本語版】 .NET Framework のセットアップを検証する最新ツール （仮バージョン） をダウンロードできます</title><link>http://blogs.msdn.com/astebner/archive/2008/03/03/8015158.aspx#9000368</link><pubDate>Wed, 15 Oct 2008 08:50:03 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9000368</guid><dc:creator>Microsoft Japan Forum Operators Blog</dc:creator><description>&lt;p&gt;こんにちは！ フォーラム オペレーターの服部 清次です 昨日、郵便局に荷物を取りに行ったら、年賀状の案内ポスターが貼ってありました。 約 60 年の歴史を持つお年玉付き年賀はがきも、最近では時代の波を反映して、当選商品にデジカメなどが用意されていますが、今年は一体どんな商品が当たるのでしょうか？&lt;/p&gt;
</description></item><item><title>re: Draft version of a new .NET Framework setup verification tool available for download</title><link>http://blogs.msdn.com/astebner/archive/2008/03/03/8015158.aspx#9038883</link><pubDate>Tue, 04 Nov 2008 14:38:19 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9038883</guid><dc:creator>jschlager</dc:creator><description>&lt;p&gt;Hi Aaron,&lt;/p&gt;
&lt;p&gt;I'm trying to use the draft version of your tool in silent mode on my local machine. The interactive version is working fine, but I had no success using the /p switch so far. I've used the syntax from the included readme.txt and after a call to&lt;/p&gt;
&lt;p&gt;./netfx_setupverifier.exe /q:a /c:&amp;quot;setupverifier.exe /p .NET Framework 1.1&amp;quot;&lt;/p&gt;
&lt;p&gt;the program quits without any noticeable action and without setting the exit code. Even if I extract the files from the archive and call &lt;/p&gt;
&lt;p&gt;./setupverifier /e &amp;quot;d:\error.txt&amp;quot; /l &amp;quot;d:\log.txt&amp;quot; /p &amp;quot;.NET Framework 1.1&amp;quot;&lt;/p&gt;
&lt;p&gt;nothing happens. I've tried both with and without quotes, using cmd32 and the windows power shell and would appreciate any hints...&lt;/p&gt;
&lt;p&gt;Cheers,&lt;/p&gt;
&lt;p&gt;J&amp;#246;rg&lt;/p&gt;</description></item><item><title>re: Draft version of a new .NET Framework setup verification tool available for download</title><link>http://blogs.msdn.com/astebner/archive/2008/03/03/8015158.aspx#9040960</link><pubDate>Tue, 04 Nov 2008 22:10:54 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9040960</guid><dc:creator>astebner</dc:creator><description>&lt;p&gt;Hi Jschlager - There is information about how to run the verification tool in silent mode in the user's guide at &lt;a rel="nofollow" target="_new" href="http://blogs.msdn.com/astebner/pages/8999004.aspx"&gt;http://blogs.msdn.com/astebner/pages/8999004.aspx&lt;/a&gt;. &amp;nbsp;I have tried the following command line and it works fine:&lt;/p&gt;
&lt;p&gt;netfx_setupverifier.exe /q:a /c:&amp;quot;setupverifier.exe /p .NET Framework 1.1&amp;quot;&lt;/p&gt;
&lt;p&gt;You need to make sure the EXE is in the exact path that you're using for your command line. &amp;nbsp;Also, in silent mode, the program doesn't display any progress UI during verification, so you need to look at the log files it produces to determine exactly what it is doing.&lt;/p&gt;
&lt;p&gt;I'm not sure what the ./ syntax is that you listed before the names of the EXEs that you're running, but that could be the problem here. &amp;nbsp;It gives me an error if I try to do that on my system, but that isn't being caused by the verification tool - I can't run any command with syntax like that.&lt;/p&gt;
</description></item><item><title>re: Draft version of a new .NET Framework setup verification tool available for download</title><link>http://blogs.msdn.com/astebner/archive/2008/03/03/8015158.aspx#9043786</link><pubDate>Wed, 05 Nov 2008 12:36:30 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9043786</guid><dc:creator>jschlager</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;the syntax I've posted is for calling the executable from the windows power shell. I've tried with cmd32 and without the &amp;quot;./&amp;quot; part, but had no success.&lt;/p&gt;
&lt;p&gt;The setupverifier does not do anything on my system when started in silent mode. There is no logfile or errorfile, the executable just returns immediately without setting the exit code.&lt;/p&gt;
&lt;p&gt;BTW, I'm using a modified MUI version of Windows XP SP2, currently with the German language packs.&lt;/p&gt;
&lt;p&gt;Again, the interactive version is working fine.&lt;/p&gt;</description></item><item><title>re: Draft version of a new .NET Framework setup verification tool available for download</title><link>http://blogs.msdn.com/astebner/archive/2008/03/03/8015158.aspx#9044750</link><pubDate>Wed, 05 Nov 2008 20:11:47 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9044750</guid><dc:creator>astebner</dc:creator><description>&lt;p&gt;Hi Jschlager - I'm not sure what to suggest here. &amp;nbsp;The command line syntax documented in the users guide consistently works for me on all systems that I've ever tried the tool on. &amp;nbsp;Can you post a screenshot that shows the exact command line you're using and the exact way that you're launching it (is it a cmd prompt, or a batch file or something else for example?)&lt;/p&gt;
</description></item><item><title>Visual Studio 2008 SP and .NET Framework 3.5 SP1 has NOT Installed but says it has! &amp;laquo; WickedW&amp;#8217;s Blog</title><link>http://blogs.msdn.com/astebner/archive/2008/03/03/8015158.aspx#9165101</link><pubDate>Tue, 02 Dec 2008 19:25:28 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9165101</guid><dc:creator>Visual Studio 2008 SP and .NET Framework 3.5 SP1 has NOT Installed but says it has! &amp;laquo; WickedW&amp;#8217;s Blog</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://wickedw.wordpress.com/2008/12/02/visual-studio-2008-sp-and-net-framework-35-sp1-has-not-installed-but-says-it-has/"&gt;http://wickedw.wordpress.com/2008/12/02/visual-studio-2008-sp-and-net-framework-35-sp1-has-not-installed-but-says-it-has/&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: Draft version of a new .NET Framework setup verification tool available for download</title><link>http://blogs.msdn.com/astebner/archive/2008/03/03/8015158.aspx#9254426</link><pubDate>Sat, 27 Dec 2008 19:15:02 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9254426</guid><dc:creator>jamieleecho</dc:creator><description>&lt;p&gt;Thank you for all of our insights into .NET.&lt;/p&gt;
&lt;p&gt;I gave this a try on my Windows XP SP2 laptop and the UI works well.&lt;/p&gt;
&lt;p&gt;Unfortunately, when I use the command line mode and enter bogus things like:&lt;/p&gt;
&lt;p&gt;netfx_setupverifier.exe /q:a /c:&amp;quot;setupverifier.exe /p .NET Framework 10.1&amp;quot;&lt;/p&gt;
&lt;p&gt;netfx_setupverifier always returns 0. The internal setupverifier seems to be doing the right thing according to the log, but it seems that the netfx_setupverifier is hardcoded to always return 0.&lt;/p&gt;
&lt;p&gt;I extracted the setupverifier program and ran it separately and it indeed is returning the expected error - so something seems to be getting lost between the two. In this case, my command line would look like:&lt;/p&gt;
&lt;p&gt;setupverifier.exe /p .NET Framework 10.1&lt;/p&gt;
&lt;p&gt;Am I doing anything wrong here?&lt;/p&gt;</description></item><item><title>re: Draft version of a new .NET Framework setup verification tool available for download</title><link>http://blogs.msdn.com/astebner/archive/2008/03/03/8015158.aspx#9271005</link><pubDate>Sun, 04 Jan 2009 09:21:18 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9271005</guid><dc:creator>astebner</dc:creator><description>&lt;p&gt;Hi Jamieleecho - The .NET Framework setup verification tool is a Windows application, not a console application. &amp;nbsp;This means that it returns the appropriate error code to the calling process in this type of scenario, but it does not update the %errorlevel% environment veriable that it sounds like you're checking in your scenario. &amp;nbsp;You'll need to have your calling process check the return code and/or manually set the errorlevel to the return code of the verification tool if you need it to work the way you're describing.&lt;/p&gt;
</description></item><item><title>Failure of .Net Framework Update &amp;laquo; HLC IT&amp;#8217;s Blog</title><link>http://blogs.msdn.com/astebner/archive/2008/03/03/8015158.aspx#9411316</link><pubDate>Tue, 10 Feb 2009 23:56:12 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9411316</guid><dc:creator>Failure of .Net Framework Update &amp;laquo; HLC IT&amp;#8217;s Blog</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://hlcit.wordpress.com/2009/02/10/failure-of-net-framework-update/"&gt;http://hlcit.wordpress.com/2009/02/10/failure-of-net-framework-update/&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: Draft version of a new .NET Framework setup verification tool available for download</title><link>http://blogs.msdn.com/astebner/archive/2008/03/03/8015158.aspx#9448698</link><pubDate>Fri, 27 Feb 2009 16:03:14 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9448698</guid><dc:creator>SPACESHIP</dc:creator><description>&lt;p&gt;Hi, I used your program to check if .net framework was correctly installed on a win98 machine - it reported me several missing dll files and following errors:&lt;/p&gt;
&lt;p&gt;Error: GetProcAdress failed for SHGetFolderPath with error code 127&lt;/p&gt;
&lt;p&gt;Error: Unable to ind an ExecutablePath value for custom action 'Custom Action - .NET framework 2.0 test application', exiting now&lt;/p&gt;
&lt;p&gt;I guess these two are connected somehow, but I dont know how to fix it. There is already the shfolder.dll in windows\system\ what else do I need to do?&lt;/p&gt;</description></item><item><title>re: Draft version of a new .NET Framework setup verification tool available for download</title><link>http://blogs.msdn.com/astebner/archive/2008/03/03/8015158.aspx#9451590</link><pubDate>Sun, 01 Mar 2009 05:06:29 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9451590</guid><dc:creator>astebner</dc:creator><description>&lt;p&gt;Hi Spaceship - To fix the missing files, I'd suggest uninstalling and re-installing the version(s) of the .NET Framework that you have installed on your system. &amp;nbsp;The steps at &lt;a rel="nofollow" target="_new" href="http://blogs.msdn.com/astebner/archive/2008/03/07/8108332.aspx"&gt;http://blogs.msdn.com/astebner/archive/2008/03/07/8108332.aspx&lt;/a&gt; might be helpful too if you run into any uninstall issues.&lt;/p&gt;
&lt;p&gt;For those 2 errors in the verification tool, could you please upload your verification tool log files to a file server (such as &lt;a rel="nofollow" target="_new" href="http://skydrive.live.com"&gt;http://skydrive.live.com&lt;/a&gt;) and then reply back with a link to the server location so I can take a look and see if I can figure out why the tool is reporting those errors on your system?&lt;/p&gt;
</description></item></channel></rss>