Packaged asp.net web site to become an EXE convenient and quick customer demo

In the ASP era, there is a netbox product can be the entire ASP site ALLinONE packaged into an EXE, in the absence of IIS can be run independently of this EXE to open the entire Web site. There have been no similar products under ASP.net, perhaps IIS is very powerful, do not need similar products? But in a scenario that requires a product of a similar functionality, this product is not intended to partially replace IIS as a lightweight IIS, but rather as a quick and easy way to show customers.

For example, when completing a website development, or after partial completion of development, want to show customers, collect customer feedback, generally there are two ways:

1. Own host and domain name, publish the website to the Internet, let the user visit the website through the Internet.

2. Deploy the Web site to a laptop and have an engineer collect customer feedback with the site to the customer.

Combined with the idea of Netbox can be the entire site packaged into an EXE, as far as possible to the relevant things are allinone to an EXE, so that when the demo to the customer, you can directly to the EXE to the user, the user directly run this EXE can see the implementation of the situation of the site, Does this add a new tool to the site demo?

Jelly.Packer.exe is from this idea and developed the packaging program, the entire site packaged into a ALLinONE exe, and then the package generated EXE to the customer to do the demo. Home Directory: To package the location of the site, a folder of the sites you have compiled to publish, typically a folder for the Visual Studio site publish output.

Virtual Directory: Site virtualization path, general use "/", if you pack two sites, want to run on the same port, you can use the virtual path to differentiate.

List directory: whether to allow listing of directories when there is no default page.

Authentication: Secure identity access is required.

Auto Show: Whether to automatically open the site, and also open the default browser to access this site.

Default Files: Site Defaults page.

When the above attribute is configured, the point "OK" will generate a Jelly.SingleRunner.exe in the Jelly.Packer.exe same directory, this Jelly.SingleRunner.exe 　　is to specify the site ALLinONE packaged exe, you can send this EXE to customers to do demo. When you run Jelly.SingleRunner.exe, you open the specified Web site on the port that you just set up on Jelly.Packer.exe: you initially considered putting together a lightweight Web server, Web site, and a lightweight browser, So there's no need to take up the port, this is done as the MS-HELP protocol for the MSDN Help Manual, which later takes into account the need for multiple browsers to be accessible, as well as exposing the demo site to the local LAN, allowing other machines in the client's local network to access, based on this requirement, It might be a better choice to pack lightweight Web servers and Web sites together.

Packaging program Download:

Annex: 06_003955_khaojellypacker.rar (2011-2-16 12:01:48, 116.80 K)

BlogEngine V2.0 packaged into EXE:

Annex: Blogengine_jelly_singlerunner.rar (2011-2-16 12:01:48, 2639.24 K)

Related publications:

Annex: 06_32323_new_jellyrelease.rar (2011-2-16 12:01:48, 263.65 K)