I am using VB Express to create an application and am pulling my hair out trying to get the cd to autorun.
Using Project->Properties->Publish and then Options... I have checked "For CD installations, automatically start Setup when CD is inserted"
In the publish folder, it creates an Autorun.inf file that contains:
[autorun]
open = setup.exe
icon = setup.exe,0
Then, using Iomega Hot Burn Pro I add all of the files in the publish folder to a cd and burn the cd.
When I insert it into any one of multiple different PCs nothing happens. I have verified that all of the test PCs have autorun enabled by inserting an Office install disk and watching it autorun.
I have searched all over and everything I have read makes it seem as simple as this. Am I missing something Do I have to use special media, or a special cd burner, or special burning software Do I have to tap my nose three times and click the burn button with my eyes closed There has to be something I am missing and I am willing to do anything at this point...
If anyone can offer any help I would greatly appreciate it!
Thanks,
Scott

Cannot get cd to autorun
shaunhey
Sebastien Andrivet
You are correct, except are you sure the executable file is called setup.exe In addition, when making an autorun CD, I always write the INF file myself, and it always works.
congminh6
It appears, after a lot of wasted time testing, that there is an issue with the autorun.inf file that gets generated by VB Express when you click "For CD Installations, automatically start Setup when CD is inserted".
I was able to write the INF file myself and it worked fine. However, after many attempts to modify the INF file that was generated by VB Express I could never get it to run. Although, in the end, the text looked IDENTICAL the generated INF was 37 bytes and the hand written INF was 34 bytes. My guess is that those extra three bytes (hidden characters) are corrupting the file so it cannot be interpreted correctly.
I would hope that the full version of Visual Studio does not have this same problem, but free or not, I would expect functionality to work if there is an option...
Fahad1
Those 3 extra bytes you see are because this file is saved with UTF-8 encoding, instead of ASCII encoding. You can fix this by opening the generated file in notepad, selecting Save As..., and set the "Encoding" combo to "ANSI".
This issue has been reported to the product feedback site: http://lab.msdn.microsoft.com/ProductFeedback/viewFeedback.aspx feedbackid=beb2b0f0-7c27-4515-b5b3-5ea140710fd8
Note that the above was originally logged by a Japanese user, but the issue appears to exist even for English users. If you are getting affected by this issue, feel free to go to the above link and add a vote (the more votes, the more likely any fix will get into a VS 2005 service pack).