Installer project question

  • Thread starter Thread starter Bryan Dickerson
  • Start date Start date
B

Bryan Dickerson

Why does the .Net installer want to put some of the Framework DLLs in my
application directory? How can I stop it from doing so when the Framework
is already installed on the machine?

TIA!
 
Most likely, there is a problem with how dependencies are detected for your project. Select your project, bring up the
Properties Window (hit F4), and select the SearchPath property. Bring up the picker, and make sure that "Include
standard seaarch paths" is selected.
 
IIRC?

Phil Wilson said:
IIRC, it does this if you use Add File rather than Add Assembly.
--
Phil Wilson [MVP Windows Installer]
----
Bryan Dickerson said:
Why does the .Net installer want to put some of the Framework DLLs in my
application directory? How can I stop it from doing so when the Framework
is already installed on the machine?

TIA!
Click to expand...
Click to expand...
 
I did that and the "Include standard search paths" box is checked. But I
also found that for some reason the "dotnetfxredist_x86.msm" file was
excluded from the setup package. Sounds like this might cause it too. Is
including that file the way to make sure the machine has the dot net
framework on it before the app is installed?

Mike Wade said:
Most likely, there is a problem with how dependencies are detected for
Click to expand...
your project. Select your project, bring up the
Properties Window (hit F4), and select the SearchPath property. Bring up
Click to expand...
the picker, and make sure that "Include
 
Back
Top