Comments on: Unattended : .Net Framework 3.5 SP1 Redistributable

By: admin

admin — Thu, 12 Nov 2009 14:26:43 +0000

Yes, when using MSI packages the logfile switch will be used. Take a look under the AppDeploy categorie. There you’ll find a lot of examples, good once are Adobe Acrobat Reader 9.1, Foxit Reader for Terminal Server & CutePDF Writer for Terminal Server.

Eric

By: Nan

Nan — Thu, 12 Nov 2009 12:01:34 +0000

Thanks for the clarification Eric. Can I also ask then – How do those other (i.e. ‘logfile’ and ’switches’) variables get utilised – does the MSI “know” to use them when it is invoked?

By: admin

admin — Thu, 12 Nov 2009 11:50:55 +0000

Hi Nan,

This is a generic script with a lot of variables that are not in use. E.g. the MST switch is only used when you need to apply a transforms file to your MSI package. The same with AppConfigPath where you would typically place custom registry files.

Eric

By: Upgrade to Citrix XenApp 5.0 Feature Pack 2 | citrix xenapp | xenserver | xendesktop | terminal server blog

Thu, 12 Nov 2009 11:41:51 +0000

[...] Microsoft .NET FrameWork 3.5 SP1 [...]

By: Nan

Nan — Thu, 12 Nov 2009 11:07:53 +0000

Sorry for being dumb, but I really don’t understand this script – Apart from AppSourcPath, what are the Appxxxx variables doing, and what should these values be set to? I can’t see any folders within the extracted source with similar names…

By: John

John — Thu, 24 Sep 2009 19:45:20 +0000

Actually there is an issue with SP1. .NET 3.5 is okay.

http://community.citrix.com/display/ocb/2009/07/27/.Net+3.5+SP1+and+Delivery+Center+servers

By: admin

admin — Fri, 19 Jun 2009 13:31:47 +0000

Hi Luke, I’m not aware of Citrix not supporting .NET 3.5. I have no issuses in my XenApp 5.0 – W2K3 x32 farm’s. The only thing I have noticed is the startup time is a bit slower, but I think this is an Micorsoft issue. Anyway the Citrix XenApp Publishing Extension 1.0 requires .NET 3.5 SP1

Eric

By: Luke

Luke — Fri, 19 Jun 2009 13:19:48 +0000

Citrix does not support nor recommend using .NET 3.5, so I’d be careful about deploying in your environment; we’ve seen issues with it here on our 4.5 farm.