none
VS2008 SP1 - Selecting .NET 3.5 SP1 prerequisite in setup project causes build error RRS feed

  • Question

  • VS2008 SP1 is installed and in my Setup project and if I select Properties=>Prerequisites and choose to "Download prerequisite from the same location as my application", I get the following error:

    "The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX20\aspnet.msp' in item '.NET Framework 3.5 SP1' can not be located on disk." Several similar errors follow with different files and directories in place of the "dotNetFX20\aspnet.msp" shown in the error above.

    I checked the readme at http://download.microsoft.com/download/A/2/8/A2807F78-C861-4B66-9B31-9205C3F22252/VS2008SP1Readme.htm#General Issues and it actually did mention a workaround to a similar problem but it also referenced the following dead link to get the dotnetfx35.exe file:
    http://go.microsoft.com/fwlink?LinkID=118080
    This link just takes me to microsoft.com.

    So I go hunting around for dotnetfx35.exe and come up with this link:
    http://download.microsoft.com/download/6/0/f/60fc5854-3cb8-4892-b6db-bd4f42510f28/dotnetfx35.exe

    However the files extracted from this dotnetfx35.exe have a different file structure than the one that was supposed to be downloaded from the dead link.

    So my main question is: How can I get .NET 3.5 SP1 included as prerequisite for offline install?

    Assuming the answer to that is "Perform the workaround illustrated in the Readme file." then my next question is where can I find the correct dotnetfx35.exe described in the workaround?

    Thanks.
    • Edited by JS_PLI Wednesday, August 27, 2008 11:20 PM typo
    Wednesday, August 13, 2008 6:53 PM

Answers

  • I had the same problem.  I got dotnetfx35.exe from http://download.microsoft.com/download/2/0/e/20e90413-712f-438c-988e-fdaa79a8ac3d/dotnetfx35.exe and followed the steps described in http://download.microsoft.com/download/A/2/8/A2807F78-C861-4B66-9B31-9205C3F22252/VS2008SP1Readme.htm#General%20Issues and everything worked fine.  One caveat to this is after you finish those steps if you have your VS open, close it and open again, since it will not pick up changes that you did.

    Sincerely,
    Vlad.NET
    • Marked as answer by Figo Fei Tuesday, August 19, 2008 3:16 AM
    Thursday, August 14, 2008 3:20 PM
  •  

    Hello All,

     

    Let me shed some light on this issue.

    We are still investigating why the Public Key Tokens of the actual files are different than what we have in the product.xml files.  Needless to say, something slipped by despite our testing.  You have my apologies for that.

     

    The good news is that the bootstrapper works quite well in this situation.  When we build, we compare the digital signature of the file on disk to the PublicKeyToken listed in the product.xml or package.xml.  If they are different, then we use the value of the actual file on disk, since this is what will be copied and/or posted in a "Same Location as my Application" scenario.  This way, the bootstrapper works correctly. 

     

    We do show a build warning, to alert the developer / builder that something is different than was expected.  This has value in the "Download from the Component Vendor's Web Site" scenario because if the file being downloaded from the Component vendor is the same as is on disk, then the download will fail the certificate test and won't install.  Fortunately, in this case, in that scenario only the dotnetfx35setup.exe file is actually downloaded from Microsoft, and that key is correct.

     

    If you wish to get rid of the build warnings, you can update your PublicKey in the Product.XML with the following value:

    3082010A0282010100A2DB0A8DCFC2C1499BCDAA3A34AD23596BDB6CBE2122B794C8EAAEBFC6D526C232118BBCDA5D2CFB36561E152BAE8F0DDD14A36E284C7F163F41AC8D40B146880DD98194AD9706D05744765CEAF1FC0EE27F74A333CB74E5EFE361A17E03B745FFD53E12D5B0CA5E0DD07BF2B7130DFC606A2885758CB7ADBC85E817B490BEF516B6625DED11DF3AEE215B8BAF8073C345E3958977609BE7AD77C1378D33142F13DB62C9AE1AA94F9867ADD420393071E08D6746E2C61CF40D5074412FE805246A216B49B092C4B239C742A56D5C184AAB8FD78E833E780A47D8A4B28423C3E2F27B66B14A74BD26414B9C6114604E30C882F3D00B707CEE554D77D2085576810203010001  

    Use this for both of the XPSEPSC* files.

     I hope this helps to clarify things, and we are going to continue to follow-up. Thank you for reporting this, it will help us keep more people from running into this.

     Sincerely,

     

    David Guyer
    Program Manager - Setup Projects
    Visual Studio


    David Guyer - Deployment Technologies Group QA
    • Proposed as answer by Martin Paternoster Thursday, August 21, 2008 6:42 PM
    • Marked as answer by JS_PLI Wednesday, August 27, 2008 9:34 PM
    Thursday, August 21, 2008 5:26 PM

All replies

  • I had the same problem.  I got dotnetfx35.exe from http://download.microsoft.com/download/2/0/e/20e90413-712f-438c-988e-fdaa79a8ac3d/dotnetfx35.exe and followed the steps described in http://download.microsoft.com/download/A/2/8/A2807F78-C861-4B66-9B31-9205C3F22252/VS2008SP1Readme.htm#General%20Issues and everything worked fine.  One caveat to this is after you finish those steps if you have your VS open, close it and open again, since it will not pick up changes that you did.

    Sincerely,
    Vlad.NET
    • Marked as answer by Figo Fei Tuesday, August 19, 2008 3:16 AM
    Thursday, August 14, 2008 3:20 PM
  • I had the same problem as well, and then found this post. I followed the steps and downloaded from the location Vlad posted, which seems to be the official location for the full .NET 3.5 SP1 full install (linked to from the bottom of this page: http://www.microsoft.com/downloads/details.aspx?FamilyId=AB99342F-5D1A-413D-8319-81DA479AB0D7&displaylang=en)

    After completing the steps, the setup builds fine in VS2008 - except that there are 2 warnings in the build output: 

    WARNING: The value of the 'PublicKey' attribute in '.NET Framework 3.5 SP1' does not match that of file 'C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFX35SP1\dotNetFX30\XPSEPSC-x86-en-US.exe'.

    WARNING: The value of the 'PublicKey' attribute in '.NET Framework 3.5 SP1' does not match that of file 'C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFX35SP1\dotNetFX30\XPSEPSC-amd64-en-US.exe'.

    Hopefully the 3.5 SP1 package is the correct one, however it's not matching up exactly to the public keys in the Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFX35SP1\product.xml file, which got installed during the VS2008 SP1 install.

    Is this anything to be concerned about? Why is there a discrepancy here?


    Pete Beech
    Monday, August 18, 2008 12:38 PM
  • Thanks Vlad.  The link you posted for dotnetfx35.exe does seem to contain the files needed for the workaround.

    I am experiencing the same warning messages that Pete has encountered after a build and that does worry me that the .NET 3.5 SP1 that I installed with VS2008 SP1 is a little different from the .NET 3.5 SP1 I downloaded from the link given above.

    I would be interested in finding out if anyone knows if there is yet another incarnation of dotnetfx35.exe that contains the expected public keys.
    Monday, August 18, 2008 7:57 PM
  • This is a glaring oversight in Microsoft's QA process.

    If these warnings are expected, or if there are some corrected values for the certificates, they should have been discovered and included in the Readme !!!!

    Great ..............
    Thursday, August 21, 2008 3:20 PM
  •  

    Hello All,

     

    Let me shed some light on this issue.

    We are still investigating why the Public Key Tokens of the actual files are different than what we have in the product.xml files.  Needless to say, something slipped by despite our testing.  You have my apologies for that.

     

    The good news is that the bootstrapper works quite well in this situation.  When we build, we compare the digital signature of the file on disk to the PublicKeyToken listed in the product.xml or package.xml.  If they are different, then we use the value of the actual file on disk, since this is what will be copied and/or posted in a "Same Location as my Application" scenario.  This way, the bootstrapper works correctly. 

     

    We do show a build warning, to alert the developer / builder that something is different than was expected.  This has value in the "Download from the Component Vendor's Web Site" scenario because if the file being downloaded from the Component vendor is the same as is on disk, then the download will fail the certificate test and won't install.  Fortunately, in this case, in that scenario only the dotnetfx35setup.exe file is actually downloaded from Microsoft, and that key is correct.

     

    If you wish to get rid of the build warnings, you can update your PublicKey in the Product.XML with the following value:

    3082010A0282010100A2DB0A8DCFC2C1499BCDAA3A34AD23596BDB6CBE2122B794C8EAAEBFC6D526C232118BBCDA5D2CFB36561E152BAE8F0DDD14A36E284C7F163F41AC8D40B146880DD98194AD9706D05744765CEAF1FC0EE27F74A333CB74E5EFE361A17E03B745FFD53E12D5B0CA5E0DD07BF2B7130DFC606A2885758CB7ADBC85E817B490BEF516B6625DED11DF3AEE215B8BAF8073C345E3958977609BE7AD77C1378D33142F13DB62C9AE1AA94F9867ADD420393071E08D6746E2C61CF40D5074412FE805246A216B49B092C4B239C742A56D5C184AAB8FD78E833E780A47D8A4B28423C3E2F27B66B14A74BD26414B9C6114604E30C882F3D00B707CEE554D77D2085576810203010001  

    Use this for both of the XPSEPSC* files.

     I hope this helps to clarify things, and we are going to continue to follow-up. Thank you for reporting this, it will help us keep more people from running into this.

     Sincerely,

     

    David Guyer
    Program Manager - Setup Projects
    Visual Studio


    David Guyer - Deployment Technologies Group QA
    • Proposed as answer by Martin Paternoster Thursday, August 21, 2008 6:42 PM
    • Marked as answer by JS_PLI Wednesday, August 27, 2008 9:34 PM
    Thursday, August 21, 2008 5:26 PM
  •  

    Another update... the online Readme has been updated to reflect updating the Product.XML with these new certificate keys, and the link to DotNetFx.exe has been fixed so everyone will download and extract the correct file.

     

    Thank you all for your patience and discussion on this topic, and I apologize for the inconveniences this has caused.  I think we've got it all straightened out. 

     

    I'd welcome feedback on the working process... is HomeSite (Component Vendor's Website) functionality in the box OK as long as you can put the files on disk (without updating the Product.XML, that's something I don't want to have to include in a readme ever again)?

     

    David Guyer

    Program Manager - Setup Projects

    Visual Studio


    David Guyer - Deployment Technologies Group QA
    Monday, August 25, 2008 5:12 PM
  • I've followed all the steps here and I can now compile.  However, I am getting a warning that reads:

    "Warning 1 Could not find prerequisite '.NET Framework 3.5 SP1' in path 'C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bootstrapper\"


    Any help is appreciated.
    • Proposed as answer by Reddy, Jeff Wednesday, August 27, 2008 9:35 PM
    • Unproposed as answer by JS_PLI Wednesday, August 27, 2008 10:16 PM
    Monday, August 25, 2008 6:04 PM
  • Golfnut,

    Let me check the simple things first...

    Firstly, do you have Service Pack 1 for VS 2008 installed?

    Secondly, is there a chance you mistyped one of the changes to the Product.XML file, perhaps making that file invalid?  Perhaps you can try opening up the file in the Visual Studio XML editor and validating it. 

    The error indicates that either the file isn't on disk, or it can't load the file.

    I hope this helps...

    David Guyer - Deployment Technologies Group QA
    • Proposed as answer by nick.negulescu Friday, January 30, 2009 10:18 PM
    Tuesday, August 26, 2008 12:44 AM
  •  I do have VS 2008 SP1 installed.  I restarted my computer and reloaded the project, did a clean and then build and the message never showed up again. 
    Thanks
    Tuesday, August 26, 2008 1:08 PM
  • David,

    I followed all the steps in this post and still had the issue of "Could not find Prerequisite"...

    It turns out that the solution found here http://download.microsoft.com/download/A/2/8/A2807F78-C861-4B66-9B31-9205C3F22252/VS2008SP1Readme.htm#General%20Issues has the following minor error which prevents all the above from working...

    In step 3 of

    Update the Package Data
    1. Open the [Program Files]\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFx35SP1 folder or %ProgramFiles(x86)%\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFx35SP1 on x64 operating systems
    2. Edit the Product.xml file in Notepad.
    3. Paste the following into the < PackageFiles > element:
      < PackageFile Name="TOOLS\clwireg.exe" />
      < PackageFile Name="TOOLS\clwireg_x64.exe" />
      < PackageFile Name="TOOLS\clwireg_ia64.exe" />
    NOTICE: There are spaces between < and PackageFile. This makes the xml incorrectly formatted in Products.xml (tested by just double clicking to open in IE). As soon as I removed these spaces it all worked OK, the message was gone.


    • Proposed as answer by GO3 Friday, September 12, 2008 7:29 AM
    Wednesday, September 10, 2008 11:43 AM
  • well done man! tnx
    Friday, September 12, 2008 7:30 AM
  • I followed the steps (figured out the incorrect XML space), and even though the .Net Framework 3.5 SP1 now shows in the dependency list, and the setup project compiles without complaint, the actual compiled Setup.exe runs incorrectly.  I asked it to install the framework from the local machine, but the setup program ALWAYS uses the Internet-download.  Is Microsoft fixing this bug yet?
    • Edited by Lowkus Friday, September 26, 2008 9:18 AM
    Friday, September 26, 2008 9:16 AM
  • Lowkus,

    Let's take a look at a few things... if it's always internet downloading, then there's probably something configured incorrectly.

    Firstly, how are you building the bootstrapper?  Have you selected "Download prerequisistes from the same site as my application", or "Download prerequisites from the Component Vendor's website"?  If it's the latter, then you are running it for internet download.

    If that's not it, try taking a look at the bootstrapper log.  It would be under %temp%\vsd?????, named install.log.  It's fairly verbose.  If it looks like it's still downloading, please paste the relevant sections of the log here.


    David Guyer - Deployment Technologies Group PM
    Tuesday, September 30, 2008 3:29 AM
  • Hello

    I get the following error messages when I try to publish and have not selected download from vendors website.

    I never had a problem when I was using 3.5. Only when I upgraded to 3.5 service pack 1.

    The error messages I am getting are:
    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\TOOLS\clwireg.exe' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information.

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\TOOLS\clwireg_x64.exe' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information.

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\TOOLS\clwireg_ia64.exe' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information.

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetMSP\x86\NetFX2.0-KB948609-v6001-x86.msu' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information.

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetMSP\x86\NetFX3.0-KB948610-v6001-x86.msu' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information.

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetMSP\x64\NetFX2.0-KB948609-v6001-x64.msu' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information.

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetMSP\x64\NetFX3.0-KB948610-v6001-x64.msu' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information.

    I have followed the steps in the following:
    http://download.microsoft.com/download/A/2/8/A2807F78-C861-4B66-9B31-9205C3F22252/VS2008SP1Readme.htm#General%20Issues
    parts:
    Update the Package Data
    Download and Extract the Core Installation Files

    C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFX35SP1
    I have the following folders and files:
    dotNetFX20
    dotNetFX30
    dotNetFX35
    dotNetMSP
    en
    dotNetFx35setup
    product

    Many thanks for any advice,

    Steve
    • Edited by steve1_rm Wednesday, October 1, 2008 12:47 PM Format text
    • Proposed as answer by Kurtis01 Wednesday, June 8, 2011 7:41 PM
    Wednesday, October 1, 2008 5:16 AM
  • Interesting.  This is one of those that I couple probably fix in 5 min if I could see/use your machine, but will be a bit of a challenge via forums !

    It sounds like you've done the right steps, yet somehow the files needed are not on your disk.  Can you double-check if the files the build system says aren't there, are there or not?  I wonder if maybe when you copied/moved folders around if only the folders got moved, and not all their contents... or maybe the files were moved, but not the sub-folders.

    Let me know what you find out...


    David Guyer - Deployment Technologies Group PM
    • Proposed as answer by Raunak Mohanty Wednesday, October 12, 2011 11:45 AM
    • Unproposed as answer by Raunak Mohanty Wednesday, October 12, 2011 11:45 AM
    Wednesday, October 1, 2008 4:44 PM
  • Haven't we already seen this kind of a problem ... here ...

    http://forums.microsoft.com/Forums/ShowPost.aspx?PostID=1190875&SiteID=1

    Isn't it time to do something so we don't have the same kind of issues with Visual Studio 10 SP1, or Visual Studio 2008 SP2, whichever should come first?  Bootstrappers are a rather important piece of VS IMO.
    Wednesday, October 1, 2008 8:43 PM
  • Hello David,

    I have checked and do not have the files.

    I am now getting the following error messages:
    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1
    \TOOLS\clwireg.exe' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information.

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1
    \TOOLS\clwireg_x64.exe' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information.

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1
    \TOOLS\clwireg_ia64.exe' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information.

    I have not movied any files or deleted any.

    The process I used for instaling the Visual Studio SP 1 was downloading the dotnetfx35setup. And installing visuaul

    studio service pack 1.

    However, I downloaded the dotnetfx35.exe from this website. http://go.microsoft.com/fwlink?LinkID=118080

    However, when I use the extraction tool (dotNetFx35.exe /x:.) to extract the contents to the WCU folder, I do not get

    the tools folder i.e.
    <PackageFile Name="TOOLS\clwireg.exe" />
    <PackageFile Name="TOOLS\clwireg_x64.exe" />
    <PackageFile Name="TOOLS\clwireg_ia64.exe" />
    So it is looking for them in this folder that does not exist on my computer.


    "There should be 5 folders under the WCU folder, and each of these should now appear in the DotNetFx35SP1 folder. The

    folder structure should resemble the following:"
    o DotNetFx35SP1 (folder)
        * dotNetFX20 (folder
        * dotNetFX30 (folder)
        * dotNetFX35 (folder)
        * dotNetMSP (folder)
        * TOOLS folder)
        * en (or some other localized folder)
        * dotNetFx35setup.exe (file)

    So after I have performed step 4 and 5 in my WCU I have the following files:

    In my DotNetFX35sp1 I have the following:
    dotNetFX30
    dotNetFX35
    dotNetMSP
    en
    dotNetFx35setup.exe
    product.xml

    As you can see I don't have any tools folder.

    I downloaded another dotnetfx35.exe from the http://go.microsoft.com/fwlink?LinkID=118080. And performed the same

    steps.

    I have also closed visual studio and re-opened. This didn't solve the problem.

    Many thanks for any more advice in helping me solve this problem.
    Thursday, October 2, 2008 8:22 AM
  • David Guyer MSFT said:

    Lowkus,

    Let's take a look at a few things... if it's always internet downloading, then there's probably something configured incorrectly.

    Firstly, how are you building the bootstrapper?  Have you selected "Download prerequisistes from the same site as my application", or "Download prerequisites from the Component Vendor's website"?  If it's the latter, then you are running it for internet download.

    If that's not it, try taking a look at the bootstrapper log.  It would be under %temp%\vsd?????, named install.log.  It's fairly verbose.  If it looks like it's still downloading, please paste the relevant sections of the log here.


    David Guyer - Deployment Technologies Group PM


    I'm building the bootstrapper using a Windows Installer project, created using VS 2008 SP1 via the project menu setup wizard.

    In the setup properties page, under prerequisites, I set it to "Download Prerequisites from the same location as my application".

    When I compile a one-click setup using these settings, the one-click installation runs the local install of the framework 3.5 SP1 installation.  But I can't use the one-click install for this particular project, I have to use the Windows Installer type setup.

    The files created by the deployment project ("Setup1") include the following:
    setup.exe
    Setup1.msi
    \DotNetFX35SP1\dotNetFX20 (files are in this directory)
    \DotNetFX35SP1\dotNetFX30 (
    files and subdirectories are in this directory)
    \DotNetFX35SP1\dotNetFX35\x64\netfx35_x64.exe
    \DotNetFX35SP1\dotNetFX35\x86\netfx35_x86.exe
    \DotNetFX35SP1\dotNetMSP (
    files and subdirectories are in this directory)
    \DotNetFX35SP1\TOOLS (
    files are in this directory)
    \DotNetFX35SP1\dotNetFx35setup.exe
    \WindowsInstaller3_1\WindowsInstaller-KB893803-v2-x86.exe


    The install.log file shows the following...
    The following properties have been set:
    Property: [AdminUser] = true {boolean}
    Property: [ProcessorArchitecture] = Intel {string}
    Property: [VersionNT] = 6.0.1 {version}
    Running checks for package '.NET Framework 3.5 SP1', phase BuildList
    Reading value 'SP' of registry key 'HKLM\Software\Microsoft\NET Framework Setup\NDP\v3.5'
    Read integer value 1
    Setting value '1 {int}' for property 'DotNet35SP'
    The following properties have been set for package '.NET Framework 3.5 SP1':
    Property: [DotNet35SP] = 1 {int}
    Running checks for command 'DotNetFX35SP1\dotNetFx35setup.exe'
    Result of running operator 'ValueGreaterThanEqualTo' on property 'DotNet35SP' and value '1': true
    Result of checks for command 'DotNetFX35SP1\dotNetFx35setup.exe' is 'Bypass'
    '.NET Framework 3.5 SP1' RunCheck result: No Install Needed
    Launching Application.
    Application appears to be an application manifest
    Launching application manifest via dfshim

    The exact intro behavior of the compiled project is:
    1) A message box titled "Windows Installer" opens, showing the text "Preparing to install..."
    2) The message box closes, and then a new message box opens that reads: "This setup requires the .NET Framework version 3.5.  Please install the .NET Framework and run this setup again.  The .NET Framework can be obtained from the web.  Would you like to do this now?"
    3a) Clicking 'NO' will stop the setup project.
    3b) Clicking 'YES' will cause the program to close the message box, and then the setup program makes an attempt to communicate outside the firewall.  Specifically, "msiexec.exe" attempts to access "http://go.microsoft.com/fwlink/?LinkID=76617".
    4a) Denying the program's attempt to call out to the Internet causes the setup program to silently shut down.
    4b) Allowing the program's attempt to call out to the Internet causes the web browser to open showing the .NET Framework Downloads page.
    Thursday, October 2, 2008 9:12 PM
  • Hello,

    I found the answer to my problem.

    I again downloaded the dotnetfx35 from this website: http://go.microsoft.com/fwlink?LinkID=118080

    I then used the extraction tool. dotnetfx35 /x:.

    And all the files that were missing were there under the dotnetframework folder.

    I think my download of the dotnetfx35 must have been corrupted, the second time I downloaded it. All the files where there.

    If anyone else wants any information about this. Then let me know.

    Regards,

    Steve
    • Proposed as answer by steve1_rm Friday, October 3, 2008 2:49 AM
    Friday, October 3, 2008 2:49 AM
  • Steve,

    I'm glad it worked for you.  I had tried it out myself and couldn't get the problem to reproduce.
    David Guyer - Deployment Technologies Group PM
    Friday, October 3, 2008 4:44 AM
  • Lowkus,

    Okay, the bootstrapper isn't showing that UI, it's the actual setup.msi, it's the .NET Frameworks Launch Condition that's doing that.

    The bootstrapper log seems to be indicating that the detection registry key is set as expected, so at this point, I don't fully understand why the launch condition is blocking, it would seem it should allow the install since the check is for NetFx 3.5, and the boostrapper is detecting/installing 3.5 SP1.

    However, we might be able to work around this problem by changing the version of the .NET Frameworks launch condition. To do this:
      Open the Launch Conditions Editor
      Select the .NET Frameworks launch condition
      Set the Version property to 2.0.50727

    Rebuild and try again.  This should be safe if you are always using the bootstrapper to install your application, since the boostrapper effectively does the 3.5 check.

    I hope this helps.

    David Guyer - Deployment Technologies Group PM
    Friday, October 3, 2008 4:51 AM
  • I also had the problem.

    I followed all tthe steps previously mentioned.

    I still had the warning "prerequisites could not ..."

    The solution was; I removed the spaces in the Product.xml file right before  PackageFile xml tags.

    It is Ok now.
    behappy
    Tuesday, October 7, 2008 10:03 AM
  • To save everyone time here, the issue and solution are fully described in the 'Visual Studio 2008 Service Pack 1 (SP1) Readme'


    Here is the excerpt from the readme:

    2.3.1.1 Enable Samesite for the .NET Framework 3.5 SP1 bootstrapper package

    If the .NET Framework 3.5 SP1 bootstrapper package is selected in the Prerequisite dialog box for a Setup project or in ClickOnce publishing, and also the "Download prerequisites from the same location as my application" option is selected, the following build error is shown: 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'dotNetFx35setup.exe' in item 'Microsoft.Net.Framework.3.5.SP1' cannot be located on disk.

    To resolve this issue:

    Update the Package Data
    1. Open the [Program Files]\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFx35SP1 folder or %ProgramFiles(x86)%\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFx35SP1 on x64 operating systems
    2. Edit the Product.xml file in Notepad.
    3. Paste the following into the < PackageFiles > element:
      < PackageFile Name="TOOLS\clwireg.exe" />
      < PackageFile Name="TOOLS\clwireg_x64.exe" />
      < PackageFile Name="TOOLS\clwireg_ia64.exe" />
    4. Find the element for < PackageFile Name="dotNetFX30\XPSEPSC-x86-en-US.exe" and change the PublicKey value to: 3082010A0282010100A2DB0A8DCFC2C1499BCDAA3A34AD23596BDB6CBE2122B794C8EAAEBFC6D526C232118BBCDA5D2CFB36561E152BAE8F0DDD14A36E284C7F163F41AC8D40B146880DD98194AD9706D05744765CEAF1FC0EE27F74A333CB74E5EFE361A17E03B745FFD53E12D5B0CA5E0DD07BF2B7130DFC606A2885758CB7ADBC85E817B490BEF516B6625DED11DF3AEE215B8BAF8073C345E3958977609BE7AD77C1378D33142F13DB62C9AE1AA94F9867ADD420393071E08D6746E2C61CF40D5074412FE805246A216B49B092C4B239C742A56D5C184AAB8FD78E833E780A47D8A4B28423C3E2F27B66B14A74BD26414B9C6114604E30C882F3D00B707CEE554D77D2085576810203010001
    5. Find the element for < PackageFile Name="dotNetFX30\XPSEPSC-amd64-en-US.exe" and change the PublicKey value to the same as in step 4 above
    6. Save the product.xml file  
    Download and Extract the Core Installation Files
    1. Navigate to the following URL: http://go.microsoft.com/fwlink?LinkID=118080
    2. Download the dotNetFx35.exe file to your local disk.
    3. Open a Command Prompt window and change to the directory to which you downloaded dotNetFx35.exe.
    4. At the command prompt, type:
      dotNetFx35.exe /x:.
      This will extract the Framework files to a folder named “WCU” in the current directory.
    5. Copy the contents of the WCU\dotNetFramework folder and paste them in the %Program Files%\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFx35SP1 folder (%ProgramFiles(x86)%\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFx35SP1 on x64 operating systems). Note: Do not copy the WCU\dotNetFramework folder itself. There should be 5 folders under the WCU folder, and each of these should now appear in the DotNetFx35SP1 folder. The folder structure should resemble the following:
      o DotNetFx35SP1 (folder)
      • dotNetFX20 (folder
      • dotNetFX30 (folder)
      • dotNetFX35 (folder)
      • dotNetMSP (folder)
      • TOOLS folder)
      • en (or some other localized folder)
      • dotNetFx35setup.exe (file)

        You may now delete the files and folders you downloaded and extracted in steps 2 and 4.

    Note:  if you are working with langauges, please refer back to the original readme file

    Perter

    Tuesday, October 7, 2008 6:23 PM
  • We are still using Visual Studio 2005.  We have a third party tool that does not support Visual Studio 2008.   Can anyone tell me if there is a way to get dotnetfx35 or dotnetfx35sp1 packages to install with a Visual Studio 2005 created bootstrapper?   I seem to be getting the same type of errors mentioned in the responses above with the main problem that we can not be connected to the internet and the install is not working from the local copies.    I have tried to update the package.xml as descibed but it has not changed my errors.

    Will the dotnetfx35 package work with a Visual Studio 2005 bootstrapper? 
    RStyer
    Monday, October 20, 2008 12:47 PM
  • You can use the dotNetFx35SP1 package (or the dotNetFx35) package with VS 2005 with one exception, I don't think you can effectively use it with the "download prerequisites from the comoponent vendors web site".  You'll probably need to use the "download prerequisites from the same site as my application" option.

    We added a new feature in VS 2008 to optimize the "component vendors web site" option, CopyAllPackageFiles="IfNotHomesite".  So, the VS 2005 bootstrapper doesn't know about that option, and will fall back to "true", which will attempt to download all package files.  Since there aren't Homesite URL's for all the files, they won't be downloaded.  I can't remember if it fails at build time, or at run time, or falls back to the "same site" experience for all files except one, effectively not being a Homesite/Component Vendor's web site option.

    Long story short, it'll work with "download prerequisites from the same site as my application" :-)

    David Guyer - Deployment Technologies Group PM
    Tuesday, October 21, 2008 4:38 AM
  • David,

    Thank you for the hint on CopyAllPackageFiles="IfNotHomeSite".  I was successful in getting it to work using Visual Studio 2005.  This is a summary of my experience:

    With the CopyAllPackageFiles="IfNotHomesite" (the default setting in the product.xml for Visual Studio 2008 SP1), Visual Studio 2005 fails at build time.

    With the CopyAllPackageFiles="false", Visual Studio 2005 builds okay but the at run time it still fails trying to access something over the internet.

    With the CopyAllPackageFiles="true", Visual Studio 2005 builds okay and the installer installs the dotnetfx35sp1 without accessing the internet.


    So the key is CopyAllPackageFiles="true" to get it to work with Visual Studio 2005 when you use the "download prerequisites from the same site as my application".  I have not tried the other download settings.  It does seem to require a reboot which it doesn't if I install outside of the bootstrapper but I can live with that.

     


    RStyer
    Wednesday, October 22, 2008 12:12 PM
  • I'm quite pleased it's working for you.

    I wouldn't expect the "Component Vendor's Website" option to work in VS2005, but what you described sounds like what I would expect.

    Enjoy!

    David

    David Guyer - Deployment Technologies Group PM
    Thursday, October 23, 2008 3:32 PM
  • I am having trouble getting this approach to work.  It seems that the build works great, but when I run the MSI it still goes to the internet to download the SP1 installer, instead of just getting it from the directory.  Does anyone know why this would happen?
    Tuesday, November 18, 2008 10:14 PM
  • Hello David,

    you asked for feedback:

    1: Thank you for that contribution. It finally solved my problems I had with the deployment issues. Some months ago, I lost a lot of time with that stuff.

    2: I still face the Warning 'The value of the 'PublicKey' attribute in 'Windows Installer 3.1' doesn't match that of file .... WindowsInstaller-KB893803-v2-x86.exe.'

    Can anybody tell me how to get rid of that warning?

    Thanks, and best regards,

    Daniel

    Monday, December 1, 2008 10:03 AM
  • David,

    I have the exact same problem as Lowkus - his details about always going to the web for the framework, even though i chose download from application are the same.

    I just tried your suggested workaround with the Launch Condition Editor. The result is it does not go to the web, but just installs the program - and does not install the framework 3.5.

    Any ideas on this?

    Also, just as a sidenote - I have to build the setup project multiple times - i keep getting permission errors on 'not able to delete output file', or 'cant create temp file - access denied'. I try to delete those manually and there is a process preventing me from doing so. CLosing and re-opening VS a couple times and rebuilding eventually is successful. I know my details are vague on this one, but i was just curious if anyone had had similar problems.

    Thanks.
    Thursday, December 11, 2008 2:16 PM
  • I've been attempting all the things in this thread, off and on, for a couple of weeks. (My program works fine after deployment, it's just anoying to have any errors during the build.) My problem was that I couldn't find any package.xml or a product.xml files anywhere on my system. DUH! I finally figured out that I needed to use the name of MY project, not package or product!

    So, now that I've figured that out, I have looked at all my .xml files and don't find the referenced section. Here's an example:

    <?xml version="1.0"?>
    <doc>
    <assembly>
    <name>
    ProjectName
    </name>
    </assembly>
    <members>

    </members>
    </doc>

    So, there is no < PackageFiles > section. Should I insert it manually? If so, where does it go. What is it's parent?

    Paul
    Tuesday, December 30, 2008 10:30 PM
  •  1.) When I try to create a installable for my application, I choose, "Download Prerequisites from the same location as my application" yet it stills goes to the web looking for .NET 3.5?

    Anyone else experience this.

    2.) Also, after .NET 3.5 installed on the target computer, it didn't continue with the installation of my app, I have to forcefully restart it in order to run it.

    Any insight on this would be appreciated.
    John Grove - TFD Group, Senior Software Engineer, EI Division, http://www.tfdg.com
    Thursday, January 22, 2009 12:13 AM
  • Actually, I figured this out. I was clicking on the msi rather then the setup. Clicking directly on the setup for some reason looked for the prerequisites on the web, but if setup.exe was called first, it then looked for prerequisites locally. Whew!!

    I will have an autorun.inf run the setup, so all should be well.
    John Grove - TFD Group, Senior Software Engineer, EI Division, http://www.tfdg.com
    Thursday, January 22, 2009 12:29 AM
  • I have done what you said.
    And there are two files I am still missing, dotnetfx35langpack_x64zh-CHT.exe and dotnetfx35langpack_x86zh-CHT.exe.
    Is there a dontnetfxSP1-CHT I can download? or could I set my install project to eng. so that I do not need to look for these two files?
    Thursday, May 21, 2009 10:54 AM
  • In VS2008, when you publish the one click deployment, you have 3 choices:
    1. download prerequisites from component's web site
    2. download prerequisites from same location as my application
    3. download prerequisites from the following location

    Choosing item 1 naturally prevent the IDE from pushing the required prerequisites to the published location.   Good job here.
    Choosing item 2 naturally tells the IDE to also push the required prerequisites to the published location.  No problem here. 

    When choosing item 3, obviously, I expect the IDE to behave the same as item 1.  However, it is behaving like item 2.  That is, it is pushing the required prerequisites to the published location.   This is undesirable because we don't want to push 230MB worth of Framework stuff to my publish location for every application I am publishing.  Is there a workaround that will allow my one click published application to download prerequisites from another location and prevent the IDE from pushing them to the published location?
    Thursday, June 18, 2009 6:54 PM
  • Hi,

    When you say the "published location", did you mean the location of the setup build output or the URL that you specified under "download prerequisites from the following location"?

    When you select the 3rd option, the IDE will put the bootstrapper package payload at the URL that you specified at build time and will download those prerequisites from the specified URL during install time. So using this option will enable your clickonce application to download prereq from another location and not include those prereq payload in the setup.exe itself. Is that what you're looking for?

    Candy
    Monday, June 22, 2009 9:05 PM
  • Hi everyone,

    I've read most of the posts above mine, but I think I'll just post my problem for a direct solution, it is however similar to steve1_rm's problem posted on October 1, 2008 5:16 AM.

    I can't publish my project when I select the second option, which is:

    * Download prerequisities from same location as my application.

    What I'm trying to achieve is that, when the setup is created the Windows Installer 3.1 and .Net Framework 3.5 SP1 are available in the same folder the setup is in, so that if the foreign computer to have the application installed on doesn't have them already installed, it can be done without going online to do so.

    (I guess the second option means this ??)

    But I keep getting these errors (about 56 of them), when I publish it with the second option selected.

    -------------------------------------------------------------------------------------------------------------------------
    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'WindowsInstaller3_1\WindowsInstaller-KB893803-v2-x86.exe' in item 'Windows Installer 3.1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX20\aspnet.msp' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX20\aspnet_64.msp' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX20\clr.msp' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX20\clr_64.msp' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX20\crt.msp' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information.

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX20\crt_64.msp' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX20\dw.msp' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX20\dw_64.msp' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX20\netfx20a_x64.msi' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX20\netfx20a_x86.msi' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX20\netfx_ca.msp' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX20\netfx_core.msp' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX20\netfx_core_64.msp' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX20\netfx_other.msp' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX20\netfx_other_64.msp' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX20\prexp.msp' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information.

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX20\winforms.msp' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX20\winforms_64.msp' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information.

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX30\x86\msxml6.msi' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX30\x64\msxml6.msi' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX30\NetFX30a_x64.msi' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX30\NetFX30a_x86.msi' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX30\RGB9RAST_x64.msi' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX30\RGB9RAST_x86.msi' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX30\WCF.msp' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX30\WCF_64.msp' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information.
     
    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX30\WCS.msp' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information.

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX30\WCS_64.msp' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information.

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX30\WF.msp' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information.

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX30\WF_32.msp' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information.

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX30\WF_64.msp' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX30\WIC_x64_enu.exe' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX30\WIC_x86_enu.exe' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX30\WPF1.msp' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information.

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX30\WPF1_64.msp' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX30\WPF2.msp' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX30\WPF2_32.msp' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX30\WPF2_64.msp' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX30\WPF_Other.msp' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX30\WPF_Other_32.msp' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX30\WPF_Other_64.msp' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX30\XPS.msp' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX30\XPSEPSC-x86-en-US.exe' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX30\XPSEPSC-amd64-en-US.exe' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX35\x86\netfx35_x86.exe' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFX35\x64\netfx35_x64.exe' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetMSP\x86\NetFX2.0-KB936704-v6000-x86_RTM_en.msu' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetMSP\x86\NetFX2.0-KB948609-v6001-x86.msu' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetMSP\x86\NetFX3.0-KB936705-v6000-x86_RTM_en.msu' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetMSP\x86\NetFX3.0-KB948610-v6001-x86.msu' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetMSP\x64\NetFX2.0-KB936704-v6000-x64_RTM_en.msu' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetMSP\x64\NetFX2.0-KB948609-v6001-x64.msu' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetMSP\x64\NetFX3.0-KB936705-v6000-x64_RTM_en.msu' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetMSP\x64\NetFX3.0-KB948610-v6001-x64.msu' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFx35setup.exe' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. 

     ----------------------------------------------------------------------------------------------------------------------------------------

    Its a long list of errors but kind of about the same thing I think.

    I'll appreciate any help directly for my problem.

    Thanks

    Thursday, July 16, 2009 6:38 AM
  • I ran into this issue also.  The following the instructions in VS2008SP1 Readme did indeed fix the problem.  But, I created my own problem,  I accidently deleted the en folder in DotNetFX35SP1 and kept getting:

    "Warning 1 Could not find prerequisite '.NET Framework 3.5 SP1' in path 'C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bootstrapper\"

    After restoring the en folder in
    C:\Program Files (x86)\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFX35SP1

    Everything was working fine.
    Friday, July 31, 2009 4:40 PM
  • Is Click Once an Alpha quality tool?
    I'm trying to deploy a customized Excel spreadsheet on a clients server on their Intranet.
    Standard prereqs of .NET 3.5 , Win Installer 3.1, and VSTO runtime.

    I have VS2008sp1 installed.

    First I find no way to have the spreadsheet installed in a folder and a shortcut added to the Start menu.
    Second, the .NET 3.5 framework fails to install from on my clients network from an a XP workstation and a Window Server 2003. (Manual installs work fine.)

    So from reading these posts, I'm supposed to follow some flawed workaround instructions in a ReadMe for VS2008 sp1. No readme that I can find installed on my computer. Windows update installed sp1.

    Click Once is really click many times, if it works at all.
    I woulld expect by this time to have at least a patch available to fix the problems  listed in the readme.
    And no way to install the spreadsheet file itself!!!!!!!!!!!! What use is that? Some of my users are barely computer literate and English is a second language. Everything needs to be very simple and easy for them to follow. No manual setup instructions are allowed.

    MSI installer is at least robust and it really is click once for the user.
    Thursday, December 24, 2009 6:42 PM
  • Even after doing this I had the issue. Erros got reduced from 56 to 9 and did not have the "Tools" folder as I was trying to extract from a older version of the .Net framework 3.5 which was around 200 MB. The latest one is around 237 MB, which you can download from microsoft site.

    Thanks,
    Manju
    manjunath
    Friday, January 8, 2010 1:34 PM
  • I have VS2005 and want to include the .net35 sp1 package. Is there any place where I can download what is in the:

    [Program Files]\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFx35SP1

    that's installed with VS2008?


    Thanks.

    Tuesday, January 12, 2010 9:55 PM
  • Yes,
    That the place that you need to copy DotNetFx35SP1.
    But...

    you must extract the file into directory and take the folder content from it.

    Sunday, January 17, 2010 10:40 AM
  • I have been reading this thread but I am concerned about one thing:

    I am running Windows 7 Ultimate 64-bit with VS2008, with all updates from Windows Update applied.

    When I look for %ProgramFiles(x86)%\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFx35SP1

    I only find %ProgramFiles(x86)%\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFx35
    (with another dotNetFX35 folder inside this folder.

    Does this mean there was a problem with installing .net 3.5 sp1? I am unable to apply the update package mentioned above as Windows 7 just tells me to enable / disable in windows components (it is there and the root option is enabled).

    What is missing?
    Thursday, February 25, 2010 5:13 PM
  • Are you on SP1 ?

    I'm running Vista 64-bit, have you tried this:

    2.3.1.1 Enable Samesite for the .NET Framework 3.5 SP1 bootstrapper package

    If the .NET Framework 3.5 SP1 bootstrapper package is selected in the Prerequisite dialog box for a Setup project or in ClickOnce publishing, and also the "Download prerequisites from the same location as my application" option is selected, the following build error is shown: 

    The install location for prerequisites has not been set to 'component vendor's web site' and the file 'dotNetFx35setup.exe' in item 'Microsoft.Net.Framework.3.5.SP1' cannot be located on disk.

    To resolve this issue:

    Update the Package Data

    1. Open the [Program Files]\Microsoft SDKs\Windows\v6.0A\Bootstrapper \Packages\DotNetFx35SP1 folder or %ProgramFiles (x86)%\Microsoft SDKs\Windows\v6.0A\Bootstrapper \Packages\DotNetFx35SP1 on x64 operating systems
    2. Edit the Product.xml file in Notepad.
    3. Paste the following into the < PackageFiles > element:
      <PackageFile Name="TOOLS\clwireg.exe"/>
      <PackageFile Name="TOOLS\clwireg_x64.exe"/>
      <PackageFile Name="TOOLS\clwireg_ia64.exe"/>
    4. Find the element for < PackageFile Name="dotNetFX30\XPSEPSC-x86-en-US.exe" and change the PublicKey value to: 3082010A0282010100A2DB0A8DCFC2C1499BCDAA3A34AD23596BDB6CBE2122B794C8EAAEBFC6D526C232118BBCDA5D2CFB36561E152BAE8F0DDD14A36E284C7F163F41AC8D40B146880DD98194AD9706D05744765CEAF1FC0EE27F74A333CB74E5EFE361A17E03B745FFD53E12D5B0CA5E0DD07BF2B7130DFC606A2885758CB7ADBC85E817B490BEF516B6625DED11DF3AEE215B8BAF8073C345E3958977609BE7AD77C1378D33142F13DB62C9AE1AA94F9867ADD420393071E08D6746E2C61CF40D5074412FE805246A216B49B092C4B239C742A56D5C184AAB8FD78E833E780A47D8A4B28423C3E2F27B66B14A74BD26414B9C6114604E30C882F3D00B707CEE554D77D2085576810203010001
    5. Find the element for < PackageFile Name="dotNetFX30\XPSEPSC-amd64-en-US.exe" and change the PublicKey value to the same as in step 4 above
    6. Save the product.xml file

     

    Download and Extract the Core Installation Files

    1. Navigate to the following URL: http://go.microsoft.com/fwlink?LinkID=118080
    2. Download the dotNetFx35.exe file to your local disk.
    3. Open a Command Prompt window and change to the directory to which you downloaded dotNetFx35.exe.
    4. At the command prompt, type:
      dotNetFx35.exe /x:.
      This will extract the Framework files to a folder named “WCU” in the current directory.
    5. Copy the contents of the WCU\dotNetFramework folder and paste them in the %Program Files%\Microsoft SDKs\Windows\v6.0A\Bootstrapper \Packages\DotNetFx35SP1 folder (%ProgramFiles (x86)% \Microsoft SDKs\Windows\v6.0A\Bootstrapper \Packages\DotNetFx35SP1 on x64 operating systems). Note: Do not copy the WCU\dotNetFramework folder itself. There should be 5 folders under the WCU folder, and each of these should now appear in the DotNetFx35SP1 folder. The folder structure should resemble the following:
      o DotNetFx35SP1 (folder)
      • dotNetFX20 (folder
      • dotNetFX30 (folder)
      • dotNetFX35 (folder)
      • dotNetMSP (folder)
      • TOOLS folder)
      • en (or some other localized folder)
      • dotNetFx35setup.exe (file)


    You may now delete the files and folders you downloaded and extracted in steps 2 and 4.
    Thursday, February 25, 2010 9:44 PM
  • Well I finally got round to trying this.

    There is a problem, as I stated before - there is no DotNetFx35SP1 folder in the Packages folder, so I tried 2 things:
    1) Created a DotNetFX35SP1 folder as a copy of DotNetFX35 and updated it as per your notes (note all my folders have FX not Fx in them).
    2) Updated DotNetFX35 as per your instructions.

    Guess what, no change!
    Monday, March 15, 2010 12:24 PM
  • I think those files are installed with service pack 1 for VS 2008.  Maybe try reinstalling the service pack?
    Tuesday, March 16, 2010 5:57 AM
  • Hi David,

    I have the same problem as Steve_rm when trying to publish with" download prerequisites from the same location as my application". With all the error messages listed by Stripes3.

    However I am running VB2008 express on Windows 7 64bit (I know that I have to change the build to X86), does your solution work for VB2008 express ie. same file download an instruction steps ?

    Thanks in advance, NewDax

    • Proposed as answer by NewDAX Monday, April 5, 2010 1:12 PM
    Tuesday, March 30, 2010 1:00 PM
  • I had this problem some time ago. I followed the instructions in the readme file, and it all seemed to work OK. However we have just had a user in Germany report that the framework installation has failed. I have checked the Packages folder on my PC, and it looks like I didn't download all of the foreign languiage support files. I have now done this, and I have rebuilt my setup project, but the DotNetFX35SP1 folder created in the output folder doesn't look any different, so I assume it is still not including the foreign lanuage files. I have managed to work around the problem for this user by giving them the location to download the full package, but I need to get this worknig for future customers. Any suggestions?
    Tuesday, March 30, 2010 4:00 PM
  • Hi,

    I tried the solution given earlier( by David ) on my VB2008 Express .

    It worked OK except that it still left one problem, an error saying that WindowsInstaller3.1 file could not be found. I'm not sure if this is because I missed something or if it's due to my particular installation. Anyway I found the file (WindowsInstaller-KB893803-v2-x86) on the the .ISO cd that I used to download VB Express. I copied it to the WindowsInstaller3_1 folder which already existed Program Files(x86)\Microsoft SDK\Windows\v6.0a\Bootstrapper\Packages. Publishing then worked fine with the " download prerequisites from the same location as my application" selected.

    Monday, April 5, 2010 1:27 PM
  •  

    I am using the Visual Studio 2008 .NET SP1 with the Framework 3.5 sp1.

    When starting a new project and selecting the Framework version at the top as 3.5, after the project is built by the compiler it references the Framework 2.0 library .dlls.

    Should it not point to the "C:\Windows\Microsoft.NET\Framework\v3.5" directory files?

    *Note:  I have also installed the Framework 4 and it does not show up on the list. ???

    The software seems to already have the service pack 1 installed as it shows 'Framework 3.5 SP1'.

    Any help in configuring the Visual Studio 2008 would be helpful.  Maybe a configuration file holds the default framework reference.

    Also does Microsoft have a trade-in-software package program for the current version (Visual Studio 2010) if a reasonable workaround is not available?

    Thanks,

    Mark James Kelley (Balvinder Singh)

    markjameskelley@msn.com

     

     

    Wednesday, May 26, 2010 12:20 AM
  • Hi,

    The different versions of the framework share files. The target is still 3.5 but you will not see 3.5 specific references unless you use 3.5 specific APIs.

    Framework 4 is not supported on VS2008 so you won't see it on the configuration list even it's installed.

    Hope that helps.

     

    Wednesday, May 26, 2010 1:05 AM
  • I get the impression that in spite of all the fixes and work-arounds, VB.net 2008 will still not let you publish an Application? 

    I have an app that I need to publish, and like everyone else, I have tried all the work arounds and still get 57 errors that look like this.( I have location set to "download from same location as my application")

    Error 57 The install location for prerequisites has not been set to 'component vendor's web site' and the file 'DotNetFX35SP1\dotNetFx35setup.exe' in item '.NET Framework 3.5 SP1' can not be located on disk. See Help for more information. arTCPread

    What next? I am totally stuck here and not very happy about wasting all this time. at least with vb.net 2003, it worked. i am seriously thinking about re-coding my entire project to 2003 so I can at least get it to woirk on my customers computer. At the moment, my customers are losing faith because every time I send them an .exe, it doesnt work, even though it works on my PC.

    HELP!!!!

    Friday, June 11, 2010 7:19 AM
  • Does the instructions in this thread also apply to VS2010 and .NET 3.5 SP1?

     

    Tuesday, September 14, 2010 12:12 PM
  • Does the instructions in this thread also apply to VS2010 and .NET 3.5 SP1?

     


    No, I don't think so; for me the problem was, that the files under "C:\Program Files (x86)\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFX35SP1\" did exist, but the files under "C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Packages\DotNetFX35SP1\" were not there.

    I copied the files and it worked.

    Ciao!
      Stefan

     

    Monday, January 10, 2011 4:00 PM
  • Hello I realize this thread is 2 years old and ivolves VS2008 however you may want to inestigate why the same problem is occuring in Visual Studio 2010??? Also investigate how past solved problems are not integrated into future developement.
    Tuesday, February 8, 2011 4:16 PM
  • this is silly

    I have multiple projects which deploy fine with 3.5 sp1 but one that gives the error Warning 1 Could not find prerequisite '.NET Framework 3.5 SP1' in path 'C:\Program Files (x86)\Microsoft SDKs\Windows\v6.0A\Bootstrapper\'

    So this is not a global problem but somehow linked to the project itself. 

     

    How should I update the projekt?



    Wednesday, March 2, 2011 2:05 PM
  • Hi Smugly,
    I have the same warning on Windows 7 64bit:
    "Warning 1 Could not find prerequisite '.NET Framework 3.5 SP1' in path 'C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bootstrapper\"
    There are no spaces in my XML file like yours and I cannot find a way to get this warning to go away.
    I also have a yellow icon with a question mark next to it in the preequisites for the setup project for
    .NET 3.5 SP1.
    All features for .NET 3.5.1 under Windows 7's programs an features are checked.
    Any Ideas?
    Thanks
    David,

    I followed all the steps in this post and still had the issue of "Could not find Prerequisite"...

    It turns out that the solution found here http://download.microsoft.com/download/A/2/8/A2807F78-C861-4B66-9B31-9205C3F22252/VS2008SP1Readme.htm#General%20Issues has the following minor error which prevents all the above from working...

    In step 3 of

    Update the Package Data
    1. Open the [Program Files]\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFx35SP1 folder or %ProgramFiles(x86)%\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFx35SP1 on x64 operating systems
    2. Edit the Product.xml file in Notepad.
    3. Paste the following into the < PackageFiles > element:
      < PackageFile Name="TOOLS\clwireg.exe" />
      < PackageFile Name="TOOLS\clwireg_x64.exe" />
      < PackageFile Name="TOOLS\clwireg_ia64.exe" />
    NOTICE: There are spaces between < and PackageFile. This makes the xml incorrectly formatted in Products.xml (tested by just double clicking to open in IE). As soon as I removed these spaces it all worked OK, the message was gone.



    Friday, March 25, 2011 1:53 PM
  • steve1_m and Dave Guyer thanks for pointing me in the right direction. I did try Dave suggestion about the product key being wrong, however, that did not work. Steve1_m observation I thank was more accurate, at least for the issue I was having. It looks like the DotNetFX35SP1 packaged with Visual Studio 2010 is incomplete. I fixed mine by copying the [Program Files]\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFx35SP1 to [Program Files]\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Packages\DotNetFx35SP1 (Although, I did have VS 2008 installed.


    Kurt
    Wednesday, June 8, 2011 7:47 PM
  • Hi David Guyer sir,

                        I followed all the steps in this location http://download.microsoft.com/download/A/2/8/A2807F78-C861-4B66-9B31-9205C3F22252/VS2008SP1Readme.htm#General%20Issues.

    I added the prerequisites of .NetFramework3.5 SP1 and built it. Build succeeded. But while installing the setup file, It never asked for installing the DotNet3.5 Sp1. I don't know where i have done mistake.

    How to make conditions for Installing in Windows 7 only. For that i need to make changes in product.xml. But i need some guidance for that.

     

    Please help me to complete this task...

    I'm waiting for the help...

    Thank you...

     

     

     




    • Proposed as answer by BornAgainDavid Wednesday, July 6, 2011 2:38 PM
    • Edited by BornAgainDavid Thursday, July 7, 2011 5:04 AM Urgent of need
    Wednesday, July 6, 2011 2:37 PM
  • I tried all above steps mentioned in http://download.microsoft.com/download/A/2/8/A2807F78-C861-4B66-9B31-9205C3F22252/VS2008SP1Readme.htm but it didnt work. Finally I figured it out. Very simple in Step 5 replace "v6.0A" with "v7.0A". I think this is because I use Windows 7, IIS 7 and Visual Studio 2010. For example

     5.  Copy the contents of the WCU\dotNetFramework folder and paste them in the %Program Files%\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFx35SP1 folder (%ProgramFiles(x86)%\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFx35SP1 on x64 operating systems). Note: Do not copy the WCU\dotNetFramework folder itself. There should be 5 folders under the WCU folder, and each of these should now appear in the DotNetFx35SP1 folder. The folder structure should resemble the following:

    should be read as

    5. Copy the contents of the WCU\dotNetFramework folder and paste them in the %Program Files%\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Packages\DotNetFx35SP1 folder (%ProgramFiles(x86)%\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Packages\DotNetFx35SP1 on x64 operating systems). Note: Do not copy the WCU\dotNetFramework folder itself. There should be 5 folders under the WCU folder, and each of these should now appear in the DotNetFx35SP1 folder. The folder structure should resemble the following:

    observe how I changed the 6.0A to 7.0A. I think this is because I use Windows 7, IIS 7 and Visual Studio 2010. Hope this helps others.

    David

    http://www.PrintersRose.com

    • Proposed as answer by KingPopper Monday, May 28, 2012 12:46 AM
    Monday, July 25, 2011 1:41 PM