Runtime dependency for an application built with wpftoolkit

Nov 8, 2008 at 4:01 AM
Hi,

Do we need .NET 3.5 SP1 (full package) only during the development (to make use of features such as DataGrid) OR do we need it also during runtime of the application developed using SP1? If we need it during runtime, then is there a runtime/redistributable version (compact) of .NET 3.5 SP1? Just at the users end (not developers end) it will be impractical to install .NET 3.5 SP1 full package as a) first of all, normal users during runtime don't need entire package b) full package size is so huge in size c) most importantly it takes so long (45 minutes or so) to install SP1 full package and installation is unstable at times.

Also in the development environment with .NET 3.5 SP1 & VS2008 SP1, compiler shows only the target of 3.5 and no target for 3.5 SP1. And if you run such compiled application in an environment that has .NET 3.5, application crashes.

Alternatively is there anyway to statically bind all wpftoolkit symbols during compile time into the main application so application doesn't have to rely on dll/SP1 during runtime. Basically though development process using wpftoolkit is smooth, I haven't found a way where deployment/runtime environment for normal users could be smooth. Please opine/help.

Thanks
Gomes