.exe files

[dyakub]

i currently use Visual studio 2008 for visual basic and i have created an application. you probably already know that Visual Studio creates 2 folders:
"Debug" & "Release". Inside of these folders are .exe files for the programs that you created right. What im really trying to do is email .exe files that i created through Visual Studio to a recipient. I have already tried attaching the exe and emailing it but that was unsuccessful. I have already tried to upload the file on zshare.net and email the link to a recipient but when the recipient recieved it, the file crashed as soon as it opened.

any help on emailing .exe files created through Visual Studio 2008to a recipient?

[chemicalNova]

They must have the .NET framework installed. It must be the same version, or newer, than what you used to create it in.

Visual Studio 2008 is.. .NET 3.0 I'm pretty sure.. correct me if I'm wrong someone?

chem

[RhinoBull]

VS 2008 uses framework 3.5 so must advise your users about this mandatory prerequisite that can be downloaded directly from MS.

[Hack]

Does your receipent have VS Studio 2008 on their machines?

[Tom Sawyer]

Instead of emailing them the exe, create a setup program and send them the msi. That will check to see if they have the needed version of the .NET Framework on their machine when they try and install it and give them the option to download the framework.

[ComputerJy]

i currently use Visual studio 2008 for visual basic and i have created an application. you probably already know that Visual Studio creates 2 folders:
"Debug" & "Release". Inside of these folders are .exe files for the programs that you created right. What im really trying to do is email .exe files that i created through Visual Studio to a recipient. I have already tried attaching the exe and emailing it but that was unsuccessful. I have already tried to upload the file on zshare.net and email the link to a recipient but when the recipient recieved it, the file crashed as soon as it opened.

any help on emailing .exe files created through Visual Studio 2008to a recipient?

What was the error you're client got? perhaps the file wasn't completely downloaded.

[penagate]

You can't just send EXEs around unless they're native with no dependencies, which barely any non-trivial application is nowadays. Create an installation package, as advised above. The Application Deployment section of this site will help with that.

[Paul M]

VS 2008 uses framework 3.5 so must advise your users about this mandatory prerequisite that can be downloaded directly from MS.

It doesn't JUST use it though you made it sound like it did. It can target the 2.0 framework and above

[RhinoBull]

Of course it does. Not sure what you are trying to say...

[Paul M]

The way you said it, sounded like you thought it only targeted the 3.5 framework.

[RhinoBull]

What in the world are you talking about?
VS 2008 is based on .Net Framework 3.5 - without it your app will not run.
Period, end of story. For more information go to MS site and read all about it.

[penagate]

What in the world are you talking about?
VS 2008 is based on .Net Framework 3.5 - without it your app will not run.
Period, end of story. For more information go to MS site and read all about it.

http://msdn2.microsoft.com/en-us/library/bb398197.aspx

The key benefit of multi-targeting is that you can use Visual Studio 2008 to create projects that target .NET Framework version 2.0, 3.0, or 3.5. This also lets you continue to develop projects that were created in Visual Studio 2005 without adding new .NET Framework dependencies.

[RhinoBull]

I'm well aware of that. However, default is 3.5 and that's the bottom line as vast majority won't even bother (not to mention be aware) about backward compatibility.
And frankly I don't see any points in developing in most recent version with "limited functionality" in mind - it's almost the same as you would develop in VB 2008 using VB4 syntax/technics.

[Paul M]

I'm well aware of that. However, default is 3.5 and that's the bottom line as vast majority won't even bother (not to mention be aware) about backward compatibility.
And frankly I don't see any points in developing in most recent version with "limited functionality" in mind - it's almost the same as you would develop in VB 2008 using VB4 syntax/technics.

I use it for 2.0 development and you can change the default framework version

[penagate]

This is going nowhere.........


Bottom line is that any application developed using the .NET Framework requires that that version of the Framework be installed in order to run.


Since the release of Visual Studio 2008, the Visual Studio version used to develop an application is no longer 1:1 tied to which Framework version is required to run it.