I have created a window setup file for my window project in visual studio 2008. This setup file is running properly and installed the software in computer. But I want to add a external exe file into my setup project. But this external exe should not be installed on computer. How can I add this another exe file in my setup not for installing?
Well that is relatively easy, follow these steps and you will be on:
Add new setup project (if you already have one, disregard this step)
Click on the setup project, then on the left panel select the application folder.
right click the application folder --> Add --> File.
Select the file you want to install with your setup.
you can choose in the application folder properties whether to always create this folder and its files or not.
That it :)
Related
I have a very simple Windows Forms application (not the one with the .NET Framework) and I want to make an installer for it. The problem is that whenever I'm trying to run the installed application, it displays an error saying that it requires .NET Core to run, even if it's already installed. I tried including everything from the project output folder, including .exe and .dll files, but that doesn't seem to work. Here's how installer project files look like.
Please check out my nanny-level teaching！
Environment：
1.Add Enxtention:
2.Install Microsoft Visual Studio Installer Project：
3.Closs the ide to start installing:
4.Create a setup project:
5.Modify the information as needed:
6.Right click Setup (Application Folder) > add > file > (all the file)：
7.Then create a shortcut, cut it to User Desktop and, after creating a shortcut, put it in User Program:
8.Build：
8.Install and run:
I have a Win Form(.net 4.7.2) project developed with C#. I right click on my project in Visual Studo and use the Publish menu to create setup files. I have a code signing certificate for my project that I renew every year.I get an error when I want to add my app to the Windows Store.
`App Policies: 10.2.9
Win32 products must be submitted as a standalone/offline installer. Installers must not be a downloader that downloads the bits it needs to run. Please resubmit with an appropriate installer.`
For more details for App Policies: 10.2.9: https://learn.microsoft.com/tr-tr/windows/uwp/publish/store-policies
Do I need to create a setup project in Visual Studio? I didn't understand exactly what to do. How can I research this?
When I Publish the project, the installation file and many folders are created. I know this is not a professional setup file, but I need a solid, secure setup file signed with certificates. I couldn't figure out how to do this, I don't even know how to search.
The simplest way to distribute a C# (WinForms/WPF) application in Microsoft Store would be to package the app into an Appx package using Visual Studio. I uploaded my WPF application to MS Store by the following procedure:
Add a Windows Application Packaging Project to my solution in Visual Studio
Right click Dependencies of the Packaging project -> Add Project Reference to my application project
Right click the Packaging project -> Publish -> Create App Packages
I have a solution in Visual Studio 2010, with seven projects. I have added a Installshield LE Setup project and when I add my main projects Primary-Output and then add a shortcut for the Primary-Output on the desktop, in the Installshield assistant.
Now when I install my application it creates a shortcut on the desktop, as expected. But when I run my application; it has a built-in logging class that generates a few log files. Now when I click the shortcut on the desktop to run the application, it creates my log files on the desktop, as well as where they are supposed to be created, which is the applications directory.
Why does installshield do this, because it's my understanding that it should only link to the .exe in the applications install folder, not think that it's launching the application from it's install folder.
I have gotten this to work by manually adding my output files to the setup project, but this is not ideal, as I would love to be able to configure this and then when I need to build a new installer, just build project and it's done.
If anybody can recommend a better installer that fits my needs, that would be great.
Installer Requirements
shortcut on desktop for application
shortcut on desktop for a url shortcut
shortcut in startup folder for application
eula
Something that is simple to get a setup project created, as I have a deadline and was only given 1 day to build and package a release build for a client.
Sounds like your app is creating log files wherever it's launched from, which isn't really Installshield's fault. You should really be writing to somewhere like the LocalApplicationData folder: http://msdn.microsoft.com/en-us/library/system.environment.specialfolder.aspx
I have completed my program and would like to send that program in its compiled state to other pc's.
I understand that in the Debug folder there is the programName.exe file, which when I open it on the PC I created it with - it opens.
But if I send that .exe file to other pc's, it crashes or simply doesnt run!
Is there a way for others to see and use my program without installing visual studio?
I have asked this question before on another programming website with not much help, this is the link that they showed me, which i then followed:
http://www.dreamincode.net/forums/topic/58021-deploying-a-c%23-application-visual-studio-setup-project/#-application-visual-studio-setup-project/
The installer installs the program, but there is no files with it to open!
Other machines won't need to have Visual Studio installed - but they will need the appropriate version of .NET, depending on what you built against. If you target the "client" profile, the .NET distribution is fairly small.
You could build a setup project which kicks off the .NET framework installation if necessary, but it's likely to be quite a lot of work - in many cases it's probably simpler just to tell people what they need to install first, particularly if this is for personal use or friends/family.
There are most likely other DLLs that your project is dependent on that do not get copied over when only transporting that .exe file. You COULD just copy those over as well.
However, the best practice is to add a new Project under Setup for a Installer. It should detect those dependencies. Then the other users will just have to run the setup.exe that gets created (but you have to include the other folders and files that get generated). Open up the File System Editor tab of the Installer project. Then inside the Application Folder, I right click on "Primary output from [Main Project] (Active)", then select "Create Shortcut to ..." and drop the Shortcut into the Program Files and User Desktop folders on the left.
For something simple, the other DLLs should be fine.
Create the MSI Installer project for your application.
Copy your project output as input of MSI Installer.
.Exe is depends on .msi file, so when you click the .exe must verify the msi file existed in same directory.
Verify the .Net framework and Installation 3.0 before run the .exe or .Msi file.
The easiest approach would be:
1: Right click on your Solution Explorer and add a new project. The new project would be a Setup project, which would be under Other Projects -> Setup and Deployment -> Visual Studio installer and then choose Setup Project from the right side.
2: Add all your bin folder files to Application folder and then build your solution.
3: It will create a file with .msi extension. You can distribute that to anyone you want and they wouldn't need any VS.
I've seen popping up around the web recently .application files, for .NET installations. (Application manifests, per the extension details).
How exactly does one create these .application files in Visual Studio, and how do they differ from a standard windows setup? Please enlighten me.
I'm a C# developer, but never used a .application installer before.
How exactly does one create these .application files in Visual Studio?
.application file is automatically created when you do a click-once deployment.
For click-once deployment, you can
Right click on the project you want to release and choose publish menu item.
-- or --
Right click on the project, select properties, go to publish tab to publish.
how do they differ from a standard windows setup?
You would create a standard windows setup program by creating a setup project in your solution. And also they differ in a way that, for click-once, end-user does not have to install the program on their local machine.
You can learn more about differences between them from MSDN
Choosing Between ClickOnce and Windows Installer