I cant wrap my head around this. If I try to build I just get a dll, but I want a exe!
If you have created a project using type Class Library, you will get a dll. Try creating a new project of type, for example, Windows Form App. When you compile it, you will end up with an exe file.
The Microsoft documentation has all the info you need.
Try using "Advanced Installer" to create a .exe or .msi installer that creates a .exe launcher. I hope this helped!
Related
So I got a crypter project from Github and I need help with it. Simply for the fact that I have no clue what I am doing when it comes to visual studio code and I need help with it. So below I have attached some pictures so you guys kinda understand the goal of what I am trying to achieve is (Building an exe file from .vb files).
img1
img2
Here I have opened the loadme.vb file
img3
I went to the build section and it is greyed out :(
img4
Like I said I have no clue what I am doing and I just want to take these .vb files from a project on Github and compile them into a simple .exe file to be executed.
Building .NET code in VS requires a project file. For VB, that's a file with extension .vbproj.
To do this, I suggest you create a new VB .NET project via File | New | Project... and selecting .NET Console Application with language VB.
Once you have a project, you can add the .vb source files to it by copying them into the project folder.
Then you just need to build the project.
I'm working on a VisualBasic project (its my first), and I wanted to ask:
How can I link an .exe file with the project?
Example: When the user opens the project, the .exe file also opens.
Easy I think (I'm newbie!)
To start another application in your application, use Process.Start
Example:
Process.Start("C:\MyApplication.exe")
I hope it will help you.
How can you publish a WinForm that uses a .dll extension into one .exe file? I'm using VB.NET on Visual Studio 2013.
I have tried several methods such as using only the program .exe file from both the Debug and Release folder but these didn't work in isolation - a runtime error happened every time a command from the extension was used, as if it didn't exist.
My problem is packaging the entire program into one file. I don't want to have to use ClickOnce applications because you can't use a custom logo and so it kinda looks bad. I'll use it if there's no alternative.
I realised that the answer was to use the setup.exe file when publishing. Also, changing the logo of a ClickOnce program is possible.
I wrote a program in VB.NET which uses several .dlls that I programed in c++. The dlls wrap some functions from an old version of the program. On my development computer everything works fine but I build a release version, copy it and the dlls onto the target machine and the .exe starts up fine. When the program tries to use a function from the .dll it throws an exception and says "unable to load DLL "c:/the path/my.dll" the specified module can't be found."
I don't know if it makes any difference, but I am defining the dll functions in the main vb project using:
Declare Function MyFunction Lib "c:/the path/my.dll" (ByVal in1 as Double, ByRef out1 as Double) as Integer
I have checked the .net framework on the target and version 4 seems to be installed same as the development computer. Both are windows XP machines. I have no idea if it is the way I programmed the .dlls or just something with my vb.net project. Any help is appreciated.
Use a path relative to your executable, rather than an absolute path.
Or, even better, don't use the path at all and just list the name of the dll file. Then add the dlls as resources to your project. You should then be able to easily bundle the inside your setup project and they'll automatically end up in the right place for both debugging and deployment.
If I am not mistaken, you want your application to function with all the .dll files you used and worked on your machine. The simplest thing to do is to publish your Program or application. But first, you have to follow the following steps in order to include all the .dll files that you want your published program to use.
Click the Project tab and select the Add References… menu.
from the opened new window, use the Browse… tab to locate the files you want to add to your project, then click Add.
Then from the project menu, select your project property: for example, if your project is named Johns_App, then in the project tab, you will find Johns_App Properties. Click this, and it will take you to a new window.
In this new window, click the Publish tab, then from the Application Files… tab, you can check, include, and exclude the project files. Then you are all set.
I suggest using the Publish Wizard…, as it will guide you step by step.
Hope this helps
Found a link to a CodeProject page which referenced this same problem.
Basically you need to check that all dependencies of the DLL file(s) are available in the running location. Using the Microsoft Dependency Walker led me to the solution that one of the dll files used in my VB application was referencing a different dll file. After placing that other DLL with other run files no more error!
I want to distribute the installer package to my clients. Please anybody provide me details information about how can I make setup.exe file for my visual studio 2008 projects. If I am failed to provide any necessary info please let me know. Thanks in advance.
Though this is written for C#, the tutorial should work fine in VB.NET as well, if that's what you're using.
http://www.dreamincode.net/forums/showtopic58021.htm
In VS2008, add a new project. Then click "Other Project Types" and Setup and Deployment underneath that. You can then pick "Setup Wizard" this will guide you through creating a setup.exe and an MSI installer. This can then be built just like any other project, so when you make a change to your project, you can rebuild the setup.
In order to create an installer package, do the following:
Go to File -> Add New Project
Select Setup Project from "Setup and Deployment Projects"
From here you can add your files and when you compile it will generate an MSI file.
If you have access to a web server, i would publish your file using clickonce. This way anytime you make a change your users will automatically get the updates. To do so, right click the main project that you want to expose and click on the publish tab.