Creating one file from all the files created using 'Publish'
-
hi, after i clicked on 'publish' - a SetUp file was created with a group of files added to it. i want to distribute it in the internet and in order to do that i need only one file. do i need to use external program to do that or is there a way to do it from inside the .NET ? are there any recomendations for external programs to use ? thanks in advance, avi
-
hi, after i clicked on 'publish' - a SetUp file was created with a group of files added to it. i want to distribute it in the internet and in order to do that i need only one file. do i need to use external program to do that or is there a way to do it from inside the .NET ? are there any recomendations for external programs to use ? thanks in advance, avi
If you're referring to ClickOnce deployment using Visual Studio, then you will need *more* than one file; you will need at least three: the *.application file, the *.manifest file, and your application file. You can read all about it at ClickOnce Deployment[^]. If you have any problems following their advice, you can post a question here and I'll respond to it. I've done that ClickOnce thing more than once.... As long as you stick with the wizard, then you should have little problem. But, you need to read about ClickOnce to understand how it works.
"we must lose precision to make significant statements about complex systems." -deKorvin on uncertainty
-
If you're referring to ClickOnce deployment using Visual Studio, then you will need *more* than one file; you will need at least three: the *.application file, the *.manifest file, and your application file. You can read all about it at ClickOnce Deployment[^]. If you have any problems following their advice, you can post a question here and I'll respond to it. I've done that ClickOnce thing more than once.... As long as you stick with the wizard, then you should have little problem. But, you need to read about ClickOnce to understand how it works.
"we must lose precision to make significant statements about complex systems." -deKorvin on uncertainty
yes , i've allready done that , but in order for someone to download a setup program from the internet he needs one EXE file only to run. ofcorse i can compress them and ask him to decompress before running setup but this is not professional. i tried the winzip self exctractor but it seems to be unable to handle subdirectories and thus the setup fails.
-
yes , i've allready done that , but in order for someone to download a setup program from the internet he needs one EXE file only to run. ofcorse i can compress them and ask him to decompress before running setup but this is not professional. i tried the winzip self exctractor but it seems to be unable to handle subdirectories and thus the setup fails.
Curtis Schlak. wrote
But, you need to read about ClickOnce to understand how it works.
shabya wrote:
yes , i've allready done that , but in order for someone to download a setup program from the internet he needs one EXE file only to run.
Are you *sure* that you read it? ClickOnce isn't just a single executable that get's downloaded and runs an installation. It makes a lot of files, but the user doesn't need to download those himself. Just build an installation using ClickOnce, upload it somewhere, and try the generated installation-procedure. Set back, imagine you're a user, click on the link that ClickOnce gives you, and relax :) The reason that it's called "ClickOnce" is that the user only needs to click once to download all required components, install and update them. Do you think that it's more professional to let the user download a single file that needs be extracted and stuff?
I are troll :)
-
yes , i've allready done that , but in order for someone to download a setup program from the internet he needs one EXE file only to run. ofcorse i can compress them and ask him to decompress before running setup but this is not professional. i tried the winzip self exctractor but it seems to be unable to handle subdirectories and thus the setup fails.
You have confused me with your questions. Let's think about the two scenarios that you've presented so far:
(Your First Post) Using the ClickOnce feature in Visual Studio
ClickOnce is part of the Windows Installer system and you only need to publish the ClickOnce files to a public Web server or share. Windows installer does the rest. Windows Installer will download and install all of the necessary files. The user only needs to click on a link.
(This Most Recent Post) Traditional Installation
The user downloads a setup package that you built using an Installer project or WiX project or InstallShield project or XXX project. That installation executable then unpacks and installs the software on the machine.
These two choices are essentially mutually exclusive, though some scenarios will have you use a local installer to bootstrap a ClickOnce installation. You really need to understand the difference between these distribution options before you can ask questions about them. My question to you is which one do you want to do: use ClickOnce and let Windows Installer handle everything for your users by using the Publish feature in Visual Studio, or build a traditional installation package that a user can download? In either case, here are resources for your education: Again, I point you to ClickOnce Deployment[^]. And, here's an article right here on CodeProject for Visual Studio Windows Application Setup Project[^] by the somewhat prolific kubben[^].
"we must lose precision to make significant statements about complex systems." -deKorvin on uncertainty
-
Curtis Schlak. wrote
But, you need to read about ClickOnce to understand how it works.
shabya wrote:
yes , i've allready done that , but in order for someone to download a setup program from the internet he needs one EXE file only to run.
Are you *sure* that you read it? ClickOnce isn't just a single executable that get's downloaded and runs an installation. It makes a lot of files, but the user doesn't need to download those himself. Just build an installation using ClickOnce, upload it somewhere, and try the generated installation-procedure. Set back, imagine you're a user, click on the link that ClickOnce gives you, and relax :) The reason that it's called "ClickOnce" is that the user only needs to click once to download all required components, install and update them. Do you think that it's more professional to let the user download a single file that needs be extracted and stuff?
I are troll :)
Again, I stand agape before your excellent answer!
"we must lose precision to make significant statements about complex systems." -deKorvin on uncertainty
-
Again, I stand agape before your excellent answer!
"we must lose precision to make significant statements about complex systems." -deKorvin on uncertainty
I should really learn some social skills. My answer might be correct (which is something to be happy for on it's own account), but it only showed that I know what you are talking about and doesn't motivate to try again. Your answer does both help and motivate :)
I are troll :)
-
I should really learn some social skills. My answer might be correct (which is something to be happy for on it's own account), but it only showed that I know what you are talking about and doesn't motivate to try again. Your answer does both help and motivate :)
I are troll :)
I've recently returned to the CP forums and I always look forward to reading a reply that ends in "I are troll." Keep up the good work!
"we must lose precision to make significant statements about complex systems." -deKorvin on uncertainty
-
I've recently returned to the CP forums and I always look forward to reading a reply that ends in "I are troll." Keep up the good work!
"we must lose precision to make significant statements about complex systems." -deKorvin on uncertainty