Simple publishing items developed using NetAdvantage
I am now asked in the question, in which "How to release the project using NetAdVantage, need to install NetAdVantage to the release machine?", The answer is not necessary to install NetAdVantage for the release machine. So I am going to tell the release step, just for the for ASP.NET project.
After we installed the NetAdVantage for ASP.NET control, we can develop. We may have discovered when developing, there are many client JS scripts that support these controls, so when publishing, except for packaging DLL In addition, we must also find ways to hit these JS scripts to the installation package. These scripts are placed in the system disk / INETPUB / WWWROOT / ASPNET_CLIENT / INFRAGISTISTICS directory, the released web application name is: Ig_common, so we are publishing, as long as we can guarantee web applications with IG_COMMON on the release machine Yes. Ok, you can start now.
1) Add a web installation project, this everyone will:
2) Add the main output, these don't say it, it is very simple. At this time, you will add the DLL of those referenced NetAdVantage to the dependency:
Relying on content:
At this time, the normal installation item is basically completed, and then set a message when installing, etc.
3) Enter the file system view: Right click on the project name
Add a web custom folder:
Named INFRAGISTICS.
4) Add content, drag all the contents in the infragitics directory in the ASPNET_CLIEN to the above-mentioned folder, will automatically add all JS files:
5) Set the properties of INFRAGITICS: The virtual directory is named: IG_COMMON, and is set as a web application project:
Ok, in this way, the installation package is installed, and you can create IG_COMMON's JS script items, so that you can use NetAdVantage on the published machine.
Very simple, of course, there may be other installation methods, anyway, just install IG_COMMON's script on the release.
PS: Of course, friends can put these scripts in their own projects, but when using the NetAdvantaeg control, you must manually set the script's directory.
Ok. I wish you success!
