InstantForum.NET v4.1.3New Boundary Support Forumhttp://www.nbtnet.newboundary.com/forum/support@newboundary.comWed, 08 Feb 2012 16:40:55 GMT20http://www.nbtnet.newboundary.com/forum/Topic814-20-1.aspx<P>In this case, a Package and an MSI would behave similarly. Or, more to the point, the Install on Demand functionality would not be any different if you used a Package or an MSI to install Office. When you are using either (with Install on Demand), access to the original source files are always going to be necessary.</P><P>The Package won't include anything that was specified as Install on Demand. It will simply create pointers to the source files that would be used at a later time, just as an MSI would do.</P>Mon, 07 Feb 2005 14:13:00 GMTNew Boundary Supporthttp://www.nbtnet.newboundary.com/forum/Topic814-20-1.aspxHi<br><br>I have a question regarding best practice when it comes to packaging software especially MS Office. I have deployed Office 2000 using prism to run a command on the client PC to install an MSI from a shared location. It seems to work fine but I am aware of the problems you can have later when a user tries to run something that has been specified to install on first use and the PC cannot find the original MSI. How does a package handle this ? If I package Office and specify some components to install on first use what happens when the user goes to run this component ? Am I better off using MSI's as I have been for Office 2000 and Outlook 2003 or should I package. I find the deployment kits that MS provide fairly useful.<br><br>Thanks in advance<br><br>GraemeFri, 04 Feb 2005 13:08:00 GMTGraeme