PreNIS: Difference between revisions
(PreNIS .Net PreProcessor for NSIS) |
No edit summary |
||
| Line 3: | Line 3: | ||
== PreNIS PreProcessor for NSIS == | == PreNIS PreProcessor for NSIS == | ||
[http://www.pixolut.com | [http://www.pixolut.com/prenis PreNIS Project Page] | ||
We at Pixolüt | We at Pixolüt use only NSIS for software deployment. We have .Net user applications and also server deployments and all of them use NSI scripts. | ||
The only problem with using an external installer system, especially a scipt based one is that its painful to manage the sync between the project file and the installer script to ensure that only required DLLs and content files are included. Also, every time a new DLL, file or folder is added to the project, the install script needs to be updated. | The only problem with using an external installer system, especially a scipt based one, is that its painful to manage the sync between the project file and the installer script to ensure that only required DLLs and content files are included. Also, every time a new DLL, file or folder is added to the project, the install script needs to be updated. | ||
What about version information - that needs to come from somewhere too! | What about version information - that needs to come from somewhere too! | ||
Wouldn't it be great to be able to use the .Net project file to dynamically create the NSI file whilst having all the power and features of NSIS? Well, with PreNIS you can. PreNIS provides a simple set of macro tags which will expand out and repeat for all folders or files specified and create a new NSI file which contains all correct files in the project. | Wouldn't it be great to be able to use the .Net project file to dynamically create the NSI file whilst having all the power and features of NSIS? Well, with PreNIS you can. PreNIS provides a simple set of macro tags which will expand out and repeat for all folders or files specified and create a new NSI file which contains all correct files in the project. | ||
Read the docs on the home page for more info. Presently only VS2003 with C# or VB.Net is supported. It is a simple extensible platform, contributors to support extending to other languages and VS2005 would be appreciated. | Read the docs on the home page for more info. Presently only VS2003 with C# or VB.Net is supported. It is a simple extensible platform, contributors to support extending to other languages and VS2005 would be appreciated. | ||
== See also == | == See also == | ||
* [http://www.pixolut.com Pixolüt Industries Website] | * [http://www.pixolut.com Pixolüt Industries Website] | ||
* [http://www.pixolut.com/ | * [http://www.pixolut.com/prenis PreNIS Project Page] | ||
[[Category:Development Environments]] | [[Category:Development Environments]] | ||
[[Category:Related Software]] | [[Category:Related Software]] | ||
Revision as of 06:58, 24 August 2006
| Author: Joe Cincotta (talk, contrib) |
PreNIS PreProcessor for NSIS
We at Pixolüt use only NSIS for software deployment. We have .Net user applications and also server deployments and all of them use NSI scripts.
The only problem with using an external installer system, especially a scipt based one, is that its painful to manage the sync between the project file and the installer script to ensure that only required DLLs and content files are included. Also, every time a new DLL, file or folder is added to the project, the install script needs to be updated.
What about version information - that needs to come from somewhere too!
Wouldn't it be great to be able to use the .Net project file to dynamically create the NSI file whilst having all the power and features of NSIS? Well, with PreNIS you can. PreNIS provides a simple set of macro tags which will expand out and repeat for all folders or files specified and create a new NSI file which contains all correct files in the project.
Read the docs on the home page for more info. Presently only VS2003 with C# or VB.Net is supported. It is a simple extensible platform, contributors to support extending to other languages and VS2005 would be appreciated.
