Integrate lightweight IIS to generate EXE files for ASP. NET websites for convenient and quick customer demonstration

This article will share with you how to package an ASP. NET Website to become an EXE for convenient and quick customer demonstration.

In the ASP era, a netbox product can package the entire ASP Website allinone into an EXE. Without IIS, you can run this EXE separately to open the entire website. There have been no similar products in ASP. NET. It may be that IIS is already very powerful and similar products are not needed? However, in some scenarios, a product with similar functions is still needed. This product is not used to partially replace IIS for a lightweight IIS, but to facilitate and quickly display the customer.

For example, if you want to show your feedback to the customer after developing a website or partially developing a website:
1. You have your own host and domain name to publish your website to the Internet so that you can access your website over the Internet.
2. Deploy the website on a notebook so that an engineer can take the website to the customer to collect customer feedback.

In combination with the idea of netbox, can the entire website be packaged into an EXE, and related things should be stored in allinone into an EXE as much as possible, so as to demonstrate to the customer, you can directly send this EXE to the user, and the user can directly run this EXE to see the implementation of the website. Does this Add a new way for the website demonstration.

Jelly.packer.exe is a package program developed from this idea. It packs the entire website into an allinone EXE and then sends it to the customer for demonstration.

Home Directory: the location where the website to be packaged is located. The folder of a site that you have compiled to publish is generally the folder output by the Visual Studio site publish.
Virtual directory: the site virtual path. Generally, "/" is used. If you package two sites and want to run them on the same port, you can use virtual paths to differentiate them.
List Directory: whether to allow the list of directories when there is no catalog page.
Authentication: whether secure access is required.
Auto Show: whether to enable the site automatically and enable the default browser to access the site.
Default files: default website page.

After the preceding attributes are configured, click "OK". This jelly.singlerunner.exe is the EXE packaged by the specified website allinone. You can send this EXE to the customer for demonstration.

After jelly.singlerunner.exe is run, the specified website will be enabled on the port just set by jelly.packer.exe:

I have initially considered packaging a lightweight web server, website, and a lightweight browser so that no port is needed, it is implemented like the MS-help protocol in the msdn help manual. Later, considering the need to allow access from multiple browsers, you can also publish the demo site to the local LAN, so that other machines in the customer's local network can also access it. Based on this requirement, it may be a good choice to package the lightweight Web server and website together.

Package download:

Attachment: 06_003955_khaojellypacker.rar (12:01:48, 116.80 K)

Package blogengine V2.0 into an EXE:

Attachment: blogengine_jelly_singlerunner.rar (12:01:48, 2639.24 K)

Related releases:

Attachment: 06_32323_new_jellyrelease.rar (12:01:48, 263.65 K)