exe files in vb.net

i'm in my programming class and i'm wondering if i can create exe files that willopen independantly of the visualstudio.net program?

thanks
-=[the]Punisher=-

They probably will not, because the .NET framework is necessary to run any applications coded in .NET. At least it is my experience that you have to have the framework. Also, I'm not positive but I've heard that .NET actually runs your created applications in a virtual machine, but MS calls it a common language runtime, which means that the code that you write isn't actually compiled into machine language (really no programming language is compiled into native machine language, but that is something that is discussed in programming classes) it's compile into something similar, and so when you call this program into execution what happens is that the computer (that has the .NET Framework) knows that this program requires the CLR to run and so it invokes it and from there it invokes the actual program that you've written into execution. This, however, isn't new to Microsoft, it is quite similar to the way in which Java works, except Java calls their's a Java Runtime Environment. Hopefully that your desired answer.

Quote:

---

because the .NET framework is necessary to run any applications coded in .NET.

---

true... but thats not exactly what was asked (as far as I understand anyway), punisher asked if the .exe would run outside visualstudio.net - which is the coding environment - the answer to which is of course yes the .exe will run outside of visual studio (but within the .NET framework of course) . However I'd pretty much agree with everything else you've said.

Z

Quote:

---

Originally posted here by BigDick
(really no programming language is compiled into native machine language, but that is something that is discussed in programming classes) it's compile into something similar, and so when you call this program into execution what happens is that the computer (that has the .NET Framework)

---

Pure...
Bullshit...

Grab an assembler and just TRY to say that statement with honesty.

well i know that the whole "no programming language is compiled into machine language" isnt true, and i just was fiddling around, and answered my own question (funny how that works), the exe file is stored int he "bin" folder, i just ran one of them and sure enough it worked, thanks for the help though. zonewalker, thanks for your help, it's good to see you again after our battle of the bluetooth thread!

Quote:

---

zonewalker, thanks for your help, it's good to see you again after our battle of the bluetooth thread!

---

no prob...I've not been around much cos personal life totally went to the wall about 6 weeks ago... its marginally better than it was but its still lying in a small heap somewhere near the bottom of the abyss at the moment so I ain't going to be around much.... but I thought I'd pop over anyway. by the way punisher have you tried using the visualstudio compiler to produce a setup/install routine for your .exe? you may want to have an play with that too :)

Quote:

---

Pure...
Bullshit...

Grab an assembler and just TRY to say that statement with honesty.

---

and I must thank specialist for pointing that out... I was of course answering in a general sense in terms of VB.net without getting into specifics.

Z

Z's on a role! thanks man, i will have to check that out. life gets better, i'm feeling the same way though. just try to sedate yourself by being around people you like to hang out with and (as long as they want to hang out with you) you'll feel fine. or you could always follow the words of the Oracle "Have a cookie, and by the time your finished eating it, you'll feel right as rain."

-=[t]P=-

assembly is compiled into machine. C, C++, etc are not, they are compiled into assembly, which is in turn compiled into machine language, compiler's have several steps (I'm not saying this to insult your intelligence, but some people may not know much about compiler construction) one of which is the intermediate code generator, this is a step that generates code that is a step between what you as the developer have written and the machine native instructions that are executed. Which is to say, it's compiled into a language understood by that machine architecture, assembly. Also there is the hardware abstraction layer:
from the webpedia :
"hardware abstraction layer, programming in an operating system that functions as an interface between a system’s hardware and software, providing a consistent hardware platform on which to run applications. When a HAL is employed, applications do not access hardware directly but access the abstract layer provided by the HAL. Like APIs, HALs allow applications to be device-independent because they abstract information from such systems as caches, I/O buses and interrupts and use this data to give the software a way to interact with the specific requirements of the hardware on which it is running. "
which means that no, your programs are directly compiled into machine, they are something close that this HAL interprets and allows the machine to execute. Which is why your windows compilers are different from the compilers on other OS architectures.

I hope this further explained why I said what I said, but it also serves to show that there was a reason that I said that.

i didnt need to know how it was compiled, just wheter i could access the .exe file without opening visual studio.net! but thanks (even though i'll leave the compiler stuff alone for righ now), but isn't assembly read by the machine? if not, why does it have to convert it twice, seems inefficient?

thanks
-=[t]P=-

I'm not to sure why it is done that way, I just remembered hearing that in one of my classes and decided to check it out, by the way it was in response to theSpecialist's comment, not yours. He's the one that said what I said was bs. And because I knew where there was evidence to prove what I said, I figured I should defend my argument. But sorry if I didn't fully answer your question earlier.

Quote:

---

I'm not saying this to insult your intelligence, but some people may not know much about compiler construction

---

I don't feel insulted at all... infact my intelligence is not worth insulting. I mean... hey, I could have simply hit up on google, in search for an entire definition of various PC jargon just to build up the defensive agianst others' posts... no matter if things have become off topic.