PreNIS: Difference between revisions

From NSIS Wiki
Jump to navigationJump to search
No edit summary
(Updated project info and description clarification.)
Line 5: Line 5:
[http://www.pixolut.com/prenis PreNIS Project Page]
[http://www.pixolut.com/prenis PreNIS Project Page]


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.
At Pixolüt we have been developing apps using .Net for a while. We generally use NSIS for packaging every kind of release. We found that we can reliably deploy server-based applications using NSIS too which can be a real time saver over silly and unreliable ftp deployment.  


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 real problem with server based deployments (and some normal apps too) is that the application contains hundreds of dependant files in many subdirectories and tracking which files are active and which are no longer in the project is a massive waste of time duplicating what is essentially already in the .Net project file.


What about version information - that needs to come from somewhere too!
Another thing which can be annoying when developing applications is updating version numbers between the assembly.cs and the NSIS script.
 
 
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 files 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. There are also commands for inserting version information and other things in the final NSIS script.


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.


Update: PreNIS is now on SourceForge with all source code in SVN. See link below.


Update: PreNIS now has its own [http://www.pixolut.com/kb.aspx Knowledge Base]. Contributions from use in the field is always welcome.


== See also ==
== See also ==
* [http://www.pixolut.com Pixolüt Industries Website]
* [http://www.pixolut.com Pixolüt Industries Website]
* [http://www.pixolut.com/prenis PreNIS Project Page]
* [http://www.pixolut.com/prenis PreNIS Project Page]
* [http://www.sourceforge.com/projects/prenis PreNIS Source Forge Project]


[[Category:Development Environments]]
[[Category:Development Environments]]
[[Category:Related Software]]
[[Category:Related Software]]

Revision as of 13:02, 6 February 2007

Author: Joe Cincotta (talk, contrib)


PreNIS PreProcessor for NSIS

PreNIS Project Page

At Pixolüt we have been developing apps using .Net for a while. We generally use NSIS for packaging every kind of release. We found that we can reliably deploy server-based applications using NSIS too which can be a real time saver over silly and unreliable ftp deployment.

The real problem with server based deployments (and some normal apps too) is that the application contains hundreds of dependant files in many subdirectories and tracking which files are active and which are no longer in the project is a massive waste of time duplicating what is essentially already in the .Net project file.

Another thing which can be annoying when developing applications is updating version numbers between the assembly.cs and the NSIS script.

Wouldn't it be great to be able to use the .Net project files 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. There are also commands for inserting version information and other things in the final NSIS script.

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.

Update: PreNIS is now on SourceForge with all source code in SVN. See link below.

Update: PreNIS now has its own Knowledge Base. Contributions from use in the field is always welcome.

See also