How to deploy .bin files from Visual Studio project? - vb.net

I'm making windows application in VB.NET and I added some files in my project in solution explorer and I set on every file I added
"Copy to Output Directory: Copy Always"
but it deploy every file except .bin files after publishing.
It work in debugging mode, but not when I publish it. any help please, how to deploy .bin files?
Thanks.

What is the Build Action property of those files set to? If it is Content then I believe that they should be included in the deployment automatically. If not, open the Publish page of the project properties and click the Application Files button. There you can control what files are included in the ClickOnce deployment.

Related

What files need to be deployed with a VS2019 app with a report viewer control

I have a VS 2019 app that uses a report viewer control. The control was added to the ToolBox by adding the file "[ProjectName]\packages\Microsoft.ReportingServices.ReportViewerControl.Winforms.150.1484.0\lib\net40\Microsoft.ReportViewer.WinForms.dll. There are a bunch of other files in this \package folder.
Which of these folders and/or files need to be deployed with this app. I'm using InnoSetup to create the deployment package? Should I deploy all files for the references in this project?
Adding the report viewer control to VS 2019 involves installing the NuGet package "Microsoft.ReportingServices.ReportViewerControl.Winforms". This added a subfolder to the project folder entitled "packages". All .dll files included in that folder need to be installed on the users' PC's.

Change the icon of a file with a .application extension

I'm building an application in vb.net/visual studio 2012. When I publish my application, the .exe file and some other files are uploaded to a server.
Publishing my application also generates a .application file. I can use this file to search for updates on my server and to automatically open the latest version of my application.
I want to change the icon of this file to the icon of my .exe file, but I don't know how. Is there any way of changing the icon of this file?
follow these steps:
Right click on the application name in the solution explorer
Select properties
Now you can see
now select Application---> change default icon to <..Browse..>
it will opens a new window from their you can browse apropriate .ico file and then publish the application
It turns out that the icon of the .application file, is not set by visual studio. It is the icon of the application that opens .application files: ClickOnce Application Deployment Support Library.
If I change the icon of that application, it will only change on my own pc and it will change the icon of all my .application files to the same one. So I think there is no solution.
Thanks anyway!

Can't figure out how to allow user to set install path

I am using Visual Studio 2010 and coding in VB.NET.
I have gone through the publish section in the program properties.
There is a Publish Location section and I have that set where I want,
but when you install the program, it never asks where you want to install it
and it installs in the the User AppData folder.
In the publish properties there is a section for Installation Folder URL.
But it only will allow a web url and not a file path.
Any help would be greatly appreciated.
You are confusing ClickOnce setups (that's the Publish) and MSI setups (which require you to create a setup project to buold an MSI file). ClickOnce doesn't sound like what you need if you want files in the UserAppDataFolder location.

Copy to AppX output directory with Visual Studio 2013 (WinRT app)?

I have a WinRT app built with VS2013 using C#. It uses SQLite so it needs the sqlite3.dll included in the project to be in the output directory. I included that DLL in my project and set it to always copy to the output directory. The problem is VS2013 copies it to the Debug directory, but not the AppX directory underneath Debug, which appears to be the WinRT output directory. Because of the the app fails because it can't find sqlite3.dll, which is up in the parent Debug directory instead of the AppX directory.
For now I'm just hand-copying the DLL into the AppX directory. What's the best way to fix this problem so that the DLL is copied to the correct directory?
In your project's Properties window choose Build Events tab. On Post-build window include similar string (please, mind to change the path to sqlite3.dll):
xcopy /Y $(ProjectDir)3DParties\sqlite3\$(PlatformName)\sqlite3.dll $(TargetDir)AppX\
Or even better option. This page https://www.sqlite.org/download.html contains section named "Precompiled Binaries for Windows Runtime" where you can download VSIX package. When you install this package into your system, you can simply reference sqlite3.dll for all target platforms (ARM, x86, x64) including all necessities automatically like this: Add Reference -> Windows 8.1 -> Extensions -> SQLite for Windows Runtime (Windows 8.1)
I can't be sure this is the "right" solution, but I set the file's property to Content/Copy-if-newer.
THEN what I've found is that if the AppX directory is already there, VS doesn't update it, just as you describe above, BUT if you delete the Appx directory then VS will create it from scratch and add the necessary files.
Not as good as having everything automated, but beats hand-copying.

changing "application files" folder in vb.net

i understand that some files get published to this folder in my application. i want all the files to be in the same folder. how do i do this?
meaning that i want the setup.exe and everything to be in one folder after i have published the application. i dont want to have an application files folder at all
You are getting hung up on what the IDE looks like when you create a Setup project. There is no "application files" folder, the Setup project creates a setup.exe file when it is built. That's the only file that you need to distribute to your client.
The "application files" node on the screen is simply a container in which you can put files while you create your Setup project. Those files will be available in the application's install directory after your client runs the setup.exe installer on her machine.
Actually run the setup.exe on your machine to see what it will look like on your client's machine.