I may do something like this rather than or inaddition to the current link I have to an executable setup file. Note that the current setup file posted does not work yet! Don Marang From: RicksPlace Sent: Thursday, March 25, 2010 8:11 AM To: programmingblind@xxxxxxxxxxxxx Subject: Re: Deployment with Visual Studio 2008 I have not used the Microsoft methods of deployment to clients. I did, once, put an exe file in a zip folder with a ReadMe and a few other files. Then I put the zip file up as a hyperlink. I put the words, something like, Download Now, as the text of the HyperLink. When the user clicked the link the standard pop up box ccame up asking if they wanted to download or run the program. If they click download, the next standard pop up would come up and ask where they wanted to download it with the file navigation treeview. That did what I needed at the time so never messed with the Microsoft methods of building an Installation Project thingy or even their method of distributing software from a webpage. Anyway, it is one method of getting something out there fast, down and dirty. If you want I will dig through my old projects to see if I can find the actual VWD code I used to get it done. I forget the gory details but it was pretty straight forward if I remember. Rick USA ----- Original Message ----- From: Donald Marang To: programmingblind@xxxxxxxxxxxxx Sent: Wednesday, March 24, 2010 7:36 PM Subject: Deployment with Visual Studio 2008 I have an alpha version of my QuickOCR application ready to post to a personal website. It was written in Visual Basic .Net using Visual Studio 2008. It is meant to be a quick and dirty method to efficiently OCR screen snapshots and files. Currently it relies on the Microsoft Office Document Imageing (MODI) tools in Office 2003 and 2007. It does more than I expected, like MODI officially only supports MDI and some TIFF files. In practice, it handles many others. I would appreciate feedback and I have a few design and deployment questions. The source is at: http://mysite.verizon.net/marangs/QuickOCR.html There is an "QuickOCREnhancements.rtf" file that lists the known deficiencies and expresses my future ideas for this application. I have not figured out the strange Publish options in Visual Studio. It clearly provides for deployment from a CD or an IIS web server. The most common deployment, a single executable setup file copied or downloaded from anywhere is not so clear. Could someone give me some pointers or direction? I have not created Windows applications in over a decade. What are the advantages to having the application installed and involved in the registry fiasco vs just a stand-alone application? Is it possible to have a simple Windows application with a Graphical User Interface which does not require installation? How is this done? Is the executable in the Debug directory useable elsewhere on my computer? Can it be distributed to other computers? I assume at the least, .Net 3.5 must be installed on their computer. Would this be different if the application had no interface, just command line options? I have a design layout question as well, but perhaps that should be a separate message. Don Marang