PreNIS - Revision history

79.203.74.189: added umlauts

2012-03-30T17:32:11Z

added umlauts

â† Older revision		Revision as of 17:32, 30 March 2012
Line 5:		Line 5:
	[http://www.pixolut.com/prenis PreNIS Project Page]		[http://www.pixolut.com/prenis 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.		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.


Line 31:		Line 31:

	== 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://sourceforge.net/projects/prenis PreNIS Source Forge Project]		* [http://sourceforge.net/projects/prenis PreNIS Source Forge Project]

202.45.125.51: /* PreNIS PreProcessor for NSIS */

2007-11-29T00:35:11Z

PreNIS PreProcessor for NSIS

â† Older revision		Revision as of 00:35, 29 November 2007
Line 25:		Line 25:

	Update: Version 1.1 Released on 10/19/2007 at [http://www.sf.net/projects/prenis PreNIS project on SourceForge]. The latest release includes more powerful control over how scripts operate with including DLL files and also allow more freedom when writing scripts (not so fussy).		Update: Version 1.1 Released on 10/19/2007 at [http://www.sf.net/projects/prenis PreNIS project on SourceForge]. The latest release includes more powerful control over how scripts operate with including DLL files and also allow more freedom when writing scripts (not so fussy).

			Update: Version 1.2 Released on 11/27/2007 at [http://www.sf.net/projects/prenis PreNIS project on SourceForge]. Supports Visual Studio 2008.

			Update: There is now a set of [http://sourceforge.net/projects/nant nAnt] includes for using PreNIS in the build pipeline from Pixolut which can be found [http://blog.pixolut.com/2007/11/28/essential-nant-utilities-from-pixolut/ here]...

	== See also ==		== See also ==

202.45.125.51: /* See also */

2007-10-29T00:17:11Z

202.45.125.51: /* PreNIS PreProcessor for NSIS */

2007-10-19T08:40:50Z

PreNIS PreProcessor for NSIS

â† Older revision		Revision as of 08:40, 19 October 2007
Line 6:		Line 6:

	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.		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.		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.		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.		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. The latest version (1.3) supports Visual Studio 2003 project files and Visual Studio 2005 project files with C# or VB.Net.
			Read the docs on the home page for more info. The latest version (1.1) supports Visual Studio 2003 project files and Visual Studio 2005 project files with C# or VB.Net.


	Update: PreNIS is now on SourceForge with all source code in SVN. See link below.		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.		Update: PreNIS now has its own [http://www.pixolut.com/kb.aspx Knowledge Base]. Contributions from use in the field is always welcome.

			Update: Version 1.1 Released on 10/19/2007 at [http://www.sf.net/projects/prenis PreNIS project on SourceForge]. The latest release includes more powerful control over how scripts operate with including DLL files and also allow more freedom when writing scripts (not so fussy).

	== See also ==		== See also ==

Kichik: Reverted edits by 82.84.51.96 to last version by 202.45.125.51

2007-10-10T18:45:44Z

Reverted edits by 82.84.51.96 to last version by 202.45.125.51

â† Older revision		Revision as of 18:45, 10 October 2007
Line 21:		Line 21:
	== 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]~~(With Trojan)~~		* [http://www.pixolut.com/prenis PreNIS Project Page]
	* [http://www.sourceforge.com/projects/prenis PreNIS Source Forge Project]		* [http://www.sourceforge.com/projects/prenis PreNIS Source Forge Project]

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

82.84.51.96 at 08:09, 10 October 2007

2007-10-10T08:09:47Z

â† Older revision		Revision as of 08:09, 10 October 2007
Line 21:		Line 21:
	== 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](With Trojan)
	* [http://www.sourceforge.com/projects/prenis PreNIS Source Forge Project]		* [http://www.sourceforge.com/projects/prenis PreNIS Source Forge Project]

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

202.45.125.51: /* PreNIS PreProcessor for NSIS */

2007-08-23T07:08:37Z

PreNIS PreProcessor for NSIS

â† Older revision		Revision as of 07:08, 23 August 2007
Line 13:		Line 13:
	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.		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. The latest version (1.3) supports Visual Studio 2003 project files and Visual Studio 2005 project files with C# or VB.Net.

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

220.233.213.43: Updated project info and description clarification.

2007-02-06T13:02:17Z

Updated project info and description clarification.

â† Older revision		Revision as of 13:02, 6 February 2007
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]]

Pixolut at 06:58, 24 August 2006

2006-08-24T06:58:12Z

â† Older revision		Revision as of 06:58, 24 August 2006
Line 3:		Line 3:
	== PreNIS PreProcessor for NSIS ==		== PreNIS PreProcessor for NSIS ==

	[http://www.pixolut.com~~/blog/2006/08~~/prenis~~-10-nsis-preprocessor-for-net.htm~~ PreNIS ~~Home~~ Page]		[http://www.pixolut.com/prenis PreNIS Project Page]

	We at PixolÃ¼t ~~ONLY~~ use NSIS for ~~deployments~~. We have .Net user applications and also server deployments ~~which~~ all use NSI scripts.		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/~~blog/PreNIS.zip Download~~ PreNIS]		* [http://www.pixolut.com/prenis PreNIS Project Page]

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

Pixolut: PreNIS .Net PreProcessor for NSIS

2006-08-09T03:00:09Z

PreNIS .Net PreProcessor for NSIS

New page

{{PageAuthor|Joe Cincotta}}

== PreNIS PreProcessor for NSIS ==

[http://www.pixolut.com/blog/2006/08/prenis-10-nsis-preprocessor-for-net.htm PreNIS Home Page]

We at PixolÃ¼t ONLY use NSIS for deployments. We have .Net user applications and also server deployments which all 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.

== See also ==
* [http://www.pixolut.com PixolÃ¼t Industries Website]
* [http://www.pixolut.com/blog/PreNIS.zip Download PreNIS]

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

â† Older revision		Revision as of 00:17, 29 October 2007
Line 29:		Line 29:
	* [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]		* [http://sourceforge.net/projects/prenis PreNIS Source Forge Project]

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