I am a rookie at this which I'm sure this question will show. Someone sent me an .exe file for a Visual Basic application and asked me to update some code. I'm not sure how to do this. When I open Visual Studio, it wants to find the .sln file which I don't seem to have. Is there a way to create the .sln file from the .exe or do I need to ask for the .sln file?
You need the source file that contains the source code.
https://social.msdn.microsoft.com/Forums/vstudio/en-US/535986d2-5fd7-43ea-91b7-10b1234bc0f9/editing-an-executable-file?forum=vseditor
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.
I have some vb code that is structured like this:
./AssemblyInfo.vb
./WindowsApplication1/AppUtils.vb
./WindowsApplication1/Form1.vb
./WindowsApplication1.Form1.resx
./WindowsApplication1.My/MyApplication.vb
./WindowsApplication1.My/MyComputer.vb
./WindowsApplication1.My/MyProject.vb
./WindowsApplication1.My/MySettings.vb
./WindowsApplication1.My/MySettingsProperty.vb
./WindowsApplication1.My.Resources/Resources.vb
./WindowsApplication1.Resources.resx
./WindowsApplication1.vbproj
I have tried several times trying to create an empty solution and then import the .vb and the .vbproj but I can not stumble on the right combination to get it to expose the build button on the menu so we can build it.
I am not a windows person so googling is difficult because the terminology is difficult to understand: Example: I use the New Project button to create a solution; that is confusing.
In short, I am hoping to get instructions that will cover:
A) Creating a new solution,
B) Importing the code listed above into the solution, and
C) Compiling the code into an .exe.
BTW: I am using Visual Studio 2008.
If you give me you best guess I will edit your answer as I try it and figure out more precise instructions.
[EDIT] When I double click on the .vbproj file on windows explorer visual studio opens and the .vbproj file is displayed as XML. No build button is shown.
[EDIT] When I do File -> Open Project... .vbproj is not listed as a supported extension so there is no way to load the project from that menu item. That menu items does not have a *.* all source option. The .vbproj file has an icon that indicates that windows knows what it is: "Visual Basic Project file". This code is the result of a decompiling an .exe of the original project where the source was lost.
[EDIT] I just followed Joel's advice, but I used VS2005 rather than VS2008 and it was able to find the .vbproj file. Does that make sense? Is there something wrong with my VS2008 that makes it not open .vbproj files or is that to be expected?
[EDIT] The version of VS that CANNOT see the .vbproj is VS2008 9.0.30729.4462. The version of VS that CAN see the .vbproj is VS2005 8.0.50727.762. By "see" I mean when I follow Joel's instructions of using File->Open Project VS will recognize the .vbproj file as something it can open.
When I double click on the .vbproj file on windows explorer visual studio opens and the .vbproj file is displayed as XML
Something is broken with file associations on your Windows system.
You can open Visual Studio first and choose "Open Project/Solution" inside Visual Studio. Doing this will makes sure Visual Studio treats it as a project file, rather than just an XML file, and will allow you to attempt to build the project.
BTW, recent versions of Visual Studio are free. You might be able to fix this by updating to a more recent version.
I have glut32.dll file which needs to be in the Debug folder whenever I compile a source. It's very frustrating to manually put in the Debug folder of each project file to have it run properly.
Is it possible I can put it in some folder and point the project to it?
I am a newbie with Visual Studio 2012.
Before this question being tagged as a duplicate, I want to add I keep seeing suggestions Referencing third party dlls, but I couldn't get it.
Any help appreciated !
If you add a project reference to this DLL, I believe it should be copied to the Debug folder automatically.
I have successfully program a VB.NET 2010 program connected with access database.
I wanna to know how can I run my program on another PC haven't visual studio on it?
what I must copy and how many file are them? and what the extensions of the files? and how can I get these files?
You can create an installation/setup project which will copy and install all the relevant files.
Read this tutorial for more details.
When a source code is run through visual studio, an executable file is created in the directory of the project. The directory is in the project file \bin\debug. You could also find the database there if connected.
The program that you are looking for is usually in the extension .exe. You also need to make sure that the database is always in the same directory as the .exe file if you will run it on a different computer without visual studio or any other compiler just that the machine is compatible with .exe files (eg. windows OS on machine)