Are you setting up a new Proof of Concept 
I will in this blog show you how to install all the .NET Frameworks packages with one script and no need for Internet access later. The .NET Framework 3.5 SP1 also includes .NET 2.0 SP2 & .NET 3.0 SP2. This script only installs the English language pack.
- Download the .NET Framework 3.5 Service Pack 1 (Full package).
- Run dotnetfx35.exe /x to extract the files and put it in the Source catalog.
The unattended script looks like this :
[sourcecode language="plain"]
@echo off
REM Install dotNetFramework35SP1-30SP2-20SP2
REM ScriptFrameWork by Joe Shonk – www.theshonkproject.com
REM Customized by Trond Eirik Haavarstein – www.xenappblog.com
pushd %~dp0
cd ..
set AppSourcePath=Source
set AppConfigPath=Configuration
set AppInstallPath=Scripts
set AppHotfixesPath=Hotfixes
set LogFile="%temp%dotNetFramework35SP1-30SP2-20SP2.log"
set Switches=/qn ALLUSERS=1 REBOOT="ReallySuppress"
set MST=TRANSFORMS=
cls
echo.
echo Installing dotNetFramework35SP1-30SP2-20SP2
echo.
cd %AppSourcePath%
start /wait dotNetFx35setup.exe /q /norestart /lang:ENU
popd
endlocal
[/sourcecode]
{ 7 comments… read them below or add one }
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.
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
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
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…
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
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?
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
{ 1 trackback }