.NET "Footprint" on Client Machines

  • Thread starter Thread starter Felipe
  • Start date Start date
F

Felipe

What comprises the [entire footprint] on computers hosting non trivial.NET
Windows Forms applications?

Specifically, suppose I have developed a .NET 2.0 Windows Forms client and
I've included a bunch of 3rd party controls - say, from Infragistics. What
do I need to tell our "desktop image" group they will need to include in
their standard client PC images (Windows XP Pro) in order to support my
application..

My understanding is that this is the footprint (please tell me if I'm wrong
or if I'm missing anything):

1. CLR (.NET Framework 2.0, itself)

2. Some "Application Folder" in which I have my application's .exe and any
supporting 4rd party .dlls and config files and other supporting files
unique to my application

3. Desktop Icon or other Start Menu shortcuts users can use to launch the
application.

That's it, AFAIK. Please advise if I've missed anything.

Thanks!
 
Number 3 is not mandatory.

--
HTH,

Kevin Spencer
Microsoft MVP
Professional Numbskull

Hard work is a medication for which
there is no placebo.
 
Back
Top