Well you see. It is really stupid to make a cool program that can't run on other computers that don't have the .net framework installed. I ve been searching for such a program that can compile my .exe (for .net) program into a normal .exe . I couldn't find anything like it so any help. If you are kinda new and you don't know why is this just rename your program into a *.txt file and open it. It says: This program cannot be run in DOS mode. That is the stupid thing. Any help would be appreciated.
Thanks anyway
How do I compile a VB.net application to a normal *.exe file? I mean that could be run in DOS mode.
KennsterDude
the .NET Framework is available as an optional update through windows update.
If you use windows, then you need a Windows executable. To take advantage of all the features that make programming so simple in VB2005, then you will need the .NET framework 2.0. If you wish to write a normal [sic] program, then you will need a compiler that will compile such a program. Perhaps an old copy of Borland Turbo C (I'm not sure - I don't even know what DOS looks like, now).
Regardless, it's NOT possible to create a VB2005 program without the .NET framework 2.0. Regardless as to how often the question is asked, or how many complaints are filed, that's the way it is. Even congress can't change this.
Mike Champion
DOS was an operating system. But, it didn't mean executing something without additional items.................do some research............If you have ever written a C program for DOS you used Header Files, and even .dll's for different functions that were not built into the language itself. There is no such thing as no dependencies for an application. Either they were Imported into the application at compile time or used at runtime. You'll have to pick a different argument here. There are some folks here that have used those "additional items" for a lot of stuff. Even back in the good old DOS days!! (not!!!!!!! )
I don't want to turn this into an argument, so this is all I'll say about this anymore. The simple answer is you can't get there from here with VB2005.
james
aka:Trucker
Have a nice day!!
Souhil Benammour
No any application created in .NET are dependent upon the framework. You cannot create a VB application that isnt. Not now, not in the past and I doubt not in the future. Even back in the days of VB Classic you still had file dependencies on the VBRunx.dll
You can create a deployment / installer (Click Once) which will install the framework if it doesnt exist on the machine. The framework only needs to be installed once on the machine for all applications written against that version of the framework to run.
Whether its a windows or console application - it still requires the .NET framework.
If you want to write DOS applications which dont require framework then I think you'll need to look at other languages outside of .NET.
rf7_15
If possible I mean
Paul Domag
IainDowns
.exe files in Windows are files you use everyday. Even DOS based applications had dependencies of some sort. Sometimes they were compiled into the application (.exe) itself. But, they are/were there. Visual Basic does not make a stand alone application of any kind. Even Quck Basic applications weren't really stand alone applications. You did have a choice to compile the application where the runtime could be seperate from the application or compiled into the application. That is something that caused a great deal of confusion with developers when Visual Basic came out. The first few versions of VB did basiclly the same thing. But, once the DotNet stuff came out, that changed. If you really want to write an application that "appears" to have no dependencies, you might want to check in to writing Unmanged code in C++. (not recommended for the feint of heart) But, that can quickly turn into a nightmare of memory leaks etc. when you forget to release memory and other resources correctly. Visual Basic does so much for the programmer and makes life so much easier and gives you many more choices now than were available in the past. Or were available but, with some very ugly hacks that might work in one OS and not the next. Or not even in the next version of Visual Basic. As for Microsoft putting the .NET Framework in the next update. It has been available at Windows Update for quite a while. But, it is not a forced update. It is an option to the end user. And without having something that points out the need, a lot of people (especially those on dial-up) won't download it. Even though it's not that huge of a download(well, for high speed folks it's not). But, as new games and applications come out, the framework(s) is/are getting distributed. It really is up to the developer to help their end users by checking for things like the Framework(s). It is really not that hard to do.
Now, in your original Subject Line you said something about something that can run in DOS mode. By any chance are you asking about a Console application That can be done in VB2005 quite easily. But, it still has the same dependencies on the framework as a regular Windows application that you would write.
james
aka:Trucker
Yuriy Gudz
Well thanks anyway
Al Lee MSFT
Jan Limpens
There really is no such thing as a "normal" .exe file. Every application has dependencies wheather it is a simple dll or something as complex as the .NetFramework. If you are going to use Visual Basic (any version) you will have dependencies on some sort of runtime. Older versions of VB can almost count on having the runtime for VB in the latest OS. Not so, for VB.NET and VB2005. You have to check to see if the Framework that is needed for your application to run is present on your end-user's machine. That is a neccessary evil. The ClickOnce Deployment model used in the Express Edition of VB will do the checking for you and prompt your user to either download it from online, or if you have built a deployment from CD or DVD, you can include the Framework on the disk. The next version of Windows,,,,,,,,,,Vista has the Framework 2.0 already in it. So, that might help if you know your user is running Vista , when it becomes available to everyone. But, until everyone is using Vista, you need to do some housekeeping and make the needed file(s) available. And even then, there will be another version of VB coming along and it's back to the same thing if you want to use that version. It's a never ending cycle that every developer faces and should just get over and do it.
james
aka:Trucker