How do I include the .Net Framework in an Executable?

Hot Topic

Changing text box labels on the fly and pausable For loops
KB 917452 did just as much as kb 915038 NOTHING
BSTR type in VB
Displaying data from SQL Server stored procedure
Print a list of Word files or convert them to a single PDF.
retrieving a selected value from DataGridViewComboBoxColumn
Form Focus Issues
design question
CodeSnippets Manager
Blair Allen Stark

Visual Basic

Assigning a Variable value
Saving Image as jpg with particular size into access database
PageSettings.PaperSize.Kind
"object instance not set to an instance of an object vb.net" happens when switch form
MS Word Macro
DataGridView problem
Disabling the close button of a windows application has a problem
httpwebresponse not support arabic language !!!!
Arraylist of structure problem
Start application as Administrator.

How do I include the .Net Framework in an Executable?

Some of the users at my company will not have the .Net Framework installed on their PC's.  How do I include it in an executable with the Express Edition of Visual Studios

Thanks,

Matt

Answer this question

How do I include the .Net Framework in an Executable?

  • ericis_com

    Just to help clarify and expand on what Matt said:

    By default, a setup project will build a Bootstrapper that includes the .NET Frameworks. Also by default the bootstrapper is configured to download the .NET Frameworks installer from microsoft.com and then run your setup.msi file. So, you would need to deploy, or give to your customers, the setup.exe file and the setup.msi file (basically whatever is in the build output directory and any subfolders in there as well). This is the same bootstrapper as used with Click-Once publishing.

    In addition, a Setup project will include a launch condition that will show a link to the .NET Frameworks if it is not installed. This condition will only run if you don't run the bootstrapper to install the application and if the .NET Frameworks is not on the machine already. It's a great backup check, and one that works if you choose not to use the bootstrapper at all.

     

     



  • Bharath Kumar J

    Note that if you package the executable in a setup project and distribute it that way, then the setup will warn the user that they need to install the framework and will provide the link for them to do so.



    If instead you deploy the application via “Publish…” (i.e., click-once deployment), the requirement for .NET framework will be noted when the user tries to install it and they will walked through that installation.



    --Matt--*

  • Sindy

  • thelion

    There are 3rd party tools on the market that will *package* the framework with the executable, However to my knowledge, MS Does Not support any of those 3rd Party tools.  They do provide a download for the framework, that can be freely distributed:
    1.1 -
    http://www.microsoft.com/downloads/details.aspx FamilyID=262D25E3-F589-4842-8157-034D1E7CF3A3&displaylang=en

    2.0-
    http://www.microsoft.com/downloads/details.aspx FamilyID=0856EACB-4362-4B0D-8EDD-AAB15C5E04F5&displaylang=en

  • How do I include the .Net Framework in an Executable?
Answer this question