Comments on: Visual Studio Build Events for MCML Applications http://www.anpark.com/index.php/2006/12/29/visual-studio-build-events-for-mcml-applications/ Media Center, Software Development, Woodworking Fri, 10 Sep 2010 05:04:32 +0000 http://wordpress.org/?v=2.7.1 hourly 1 By: Anthony Park http://www.anpark.com/index.php/2006/12/29/visual-studio-build-events-for-mcml-applications/comment-page-1/#comment-125 Anthony Park Fri, 27 Apr 2007 09:02:21 +0000 http://anpark.com/?p=54#comment-125 Thanks for pointing this out, Walker. I have corrected the quotes that are displayed in this blog post so that they are normal quotes instead of the fancy ones. Thanks for pointing this out, Walker. I have corrected the quotes that are displayed in this blog post so that they are normal quotes instead of the fancy ones.

]]> By: Walker Hagius http://www.anpark.com/index.php/2006/12/29/visual-studio-build-events-for-mcml-applications/comment-page-1/#comment-124 Walker Hagius Fri, 27 Apr 2007 04:15:42 +0000 http://anpark.com/?p=54#comment-124 D'oh! The software running this site changes double quotes to fancy quotes automagically, so don't copy/paste my example either. :) Just make sure to put regular quotes in manually. D’oh! The software running this site changes double quotes to fancy quotes automagically, so don’t copy/paste my example either. :) Just make sure to put regular quotes in manually.

]]> By: Walker Hagius http://www.anpark.com/index.php/2006/12/29/visual-studio-build-events-for-mcml-applications/comment-page-1/#comment-123 Walker Hagius Fri, 27 Apr 2007 04:13:11 +0000 http://anpark.com/?p=54#comment-123 Important note: If you copy-paste the build steps from this page, make sure to change the quotation marks back to regular double quotes (rather than spiffy opening/closing quotation marks). So instead of this: “C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin\gacutil.exe” /nologo /i “$(TargetPath)” /f you want this: "C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin\gacutil.exe" /nologo /i "$(TargetPath)" /f At least you have to do this to run it from a command line, maybe Visual Studio is smart enough to translate these internally. VS doesn't give an error, but then again it doesn't give an error when the assembly isn't strong named either--both give errors from the command line. Important note: If you copy-paste the build steps from this page, make sure to change the quotation marks back to regular double quotes (rather than spiffy opening/closing quotation marks). So instead of this:

“C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin\gacutil.exe” /nologo /i “$(TargetPath)” /f

you want this:

"C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin\gacutil.exe" /nologo /i "$(TargetPath)" /f

At least you have to do this to run it from a command line, maybe Visual Studio is smart enough to translate these internally. VS doesn’t give an error, but then again it doesn’t give an error when the assembly isn’t strong named either–both give errors from the command line.

]]>