Bloated .NET Framework 3.5 SP1 Dependencies

  • Thread starter Thread starter Krickster
  • Start date Start date
K

Krickster

I have a Winforms app to be deployed on WES (XPE FP 2007) using .NET
Framework 3.5 SP1. The app will replace the shell and have no need for
Telephony, terminal services or internet explorer (among a few other things).

To reduce the footprint, I followed the Aaron's instructions:
http://blogs.msdn.com/astebner/archive/2007/12/03/6646794.aspx

I also read that the Framework can use the Primitive component instead of
entire IE (if not needing the whole IE bundle):

"These dependent files have been made independent of the Internet Explorer
component and are now ‘Primitive’ components"
http://msdn.microsoft.com/en-us/library/ms932567.aspx

My question is if there is a way in TD to instruct it to use the Primitive
dependency INSTEAD of the full blown IE (and all of it's dependencies) when
running the check?

If there is no way to do this, can someone direct me to a list of
dependencies for IE so I can remove them from my image OR a list of .NET fw
3.5 sp1 dependencies that I can refer to and delete what I "think" my app
won't use?

Would be nice if there was a "skeleton" .NET Framework macro somewhere that
only had the barebones dependencies.

Thanks,
Ken
 
Ken,

Did you ever find out how to use the primitive component instead of the entire IE?

Thanks
Gem



Krickste wrote:

Bloated .NET Framework 3.5 SP1 Dependencies
06-Oct-08

I have a Winforms app to be deployed on WES (XPE FP 2007) using .NET
Framework 3.5 SP1. The app will replace the shell and have no need for
Telephony, terminal services or internet explorer (among a few other things)

To reduce the footprint, I followed the Aaron's instructions:
http://blogs.msdn.com/astebner/archive/2007/12/03/6646794.asp

I also read that the Framework can use the Primitive component instead of
entire IE (if not needing the whole IE bundle)

"These dependent files have been made independent of the Internet Explorer
component and are now ???Primitive??? components
http://msdn.microsoft.com/en-us/library/ms932567.asp

My question is if there is a way in TD to instruct it to use the Primitive
dependency INSTEAD of the full blown IE (and all of it's dependencies) when
running the check

If there is no way to do this, can someone direct me to a list of
dependencies for IE so I can remove them from my image OR a list of .NET fw
3.5 sp1 dependencies that I can refer to and delete what I "think" my app
won't use

Would be nice if there was a "skeleton" .NET Framework macro somewhere that
only had the barebones dependencies

Thanks
Ken

Previous Posts In This Thread:

On 06 October 2008 17:34
Krickste wrote:

Bloated .NET Framework 3.5 SP1 Dependencies
I have a Winforms app to be deployed on WES (XPE FP 2007) using .NET
Framework 3.5 SP1. The app will replace the shell and have no need for
Telephony, terminal services or internet explorer (among a few other things)

To reduce the footprint, I followed the Aaron's instructions:
http://blogs.msdn.com/astebner/archive/2007/12/03/6646794.asp

I also read that the Framework can use the Primitive component instead of
entire IE (if not needing the whole IE bundle)

"These dependent files have been made independent of the Internet Explorer
component and are now ???Primitive??? components
http://msdn.microsoft.com/en-us/library/ms932567.asp

My question is if there is a way in TD to instruct it to use the Primitive
dependency INSTEAD of the full blown IE (and all of it's dependencies) when
running the check

If there is no way to do this, can someone direct me to a list of
dependencies for IE so I can remove them from my image OR a list of .NET fw
3.5 sp1 dependencies that I can refer to and delete what I "think" my app
won't use

Would be nice if there was a "skeleton" .NET Framework macro somewhere that
only had the barebones dependencies

Thanks
Ken

EggHeadCafe - Software Developer Portal of Choice
WPF - XAML Change Binding Attributes At Runtime
http://www.eggheadcafe.com/tutorial...9c-71731557c486/wpf--xaml-change-binding.aspx
 
Ken,

Did you find a solution to a getting the framework to use the prmitive component instead of the entire IE?

Thanks
Gem



Krickste wrote:

Bloated .NET Framework 3.5 SP1 Dependencies
06-Oct-08

I have a Winforms app to be deployed on WES (XPE FP 2007) using .NET
Framework 3.5 SP1. The app will replace the shell and have no need for
Telephony, terminal services or internet explorer (among a few other things).

To reduce the footprint, I followed the Aaron's instructions:
http://blogs.msdn.com/astebner/archive/2007/12/03/6646794.aspx

I also read that the Framework can use the Primitive component instead of
entire IE (if not needing the whole IE bundle):

"These dependent files have been made independent of the Internet Explorer
component and are now ???Primitive??? components"
http://msdn.microsoft.com/en-us/library/ms932567.aspx

My question is if there is a way in TD to instruct it to use the Primitive
dependency INSTEAD of the full blown IE (and all of it's dependencies) when
running the check?

If there is no way to do this, can someone direct me to a list of
dependencies for IE so I can remove them from my image OR a list of .NET fw
3.5 sp1 dependencies that I can refer to and delete what I "think" my app
won't use?

Would be nice if there was a "skeleton" .NET Framework macro somewhere that
only had the barebones dependencies.

Thanks,
Ken

Previous Posts In This Thread:

On 06 October 2008 17:34
Krickste wrote:

Bloated .NET Framework 3.5 SP1 Dependencies
I have a Winforms app to be deployed on WES (XPE FP 2007) using .NET
Framework 3.5 SP1. The app will replace the shell and have no need for
Telephony, terminal services or internet explorer (among a few other things).

To reduce the footprint, I followed the Aaron's instructions:
http://blogs.msdn.com/astebner/archive/2007/12/03/6646794.aspx

I also read that the Framework can use the Primitive component instead of
entire IE (if not needing the whole IE bundle):

"These dependent files have been made independent of the Internet Explorer
component and are now ???Primitive??? components"
http://msdn.microsoft.com/en-us/library/ms932567.aspx

My question is if there is a way in TD to instruct it to use the Primitive
dependency INSTEAD of the full blown IE (and all of it's dependencies) when
running the check?

If there is no way to do this, can someone direct me to a list of
dependencies for IE so I can remove them from my image OR a list of .NET fw
3.5 sp1 dependencies that I can refer to and delete what I "think" my app
won't use?

Would be nice if there was a "skeleton" .NET Framework macro somewhere that
only had the barebones dependencies.

Thanks,
Ken

On 05 November 2009 12:20
Gemma O'Connor wrote:

..net bloated components
Ken,

Did you ever find out how to use the primitive component instead of the entire IE?

Thanks
Gem

EggHeadCafe - Software Developer Portal of Choice
How To Create a Custom IE8 Accelerator
http://www.eggheadcafe.com/tutorial...a-11c3e7cc2a61/how-to-create-a-custom-ie.aspx
 
Back
Top