none
Regarding the .net framework's setup RRS feed

  • Question

  • As we know, now the .net 4.0's client profile only has more than 40M size.

    But the speed of setup is still slow, does Microsoft have plan to improve it?


    video edit
    Tuesday, June 21, 2011 4:01 PM

Answers

  • Hi Tony,

    Thanks for your post.

    Based on my experience, the installation speed of .NET Framework is depends on the hardware & software environment of the target machine, and what programs are running while installing .NET Framework. In order to help diagnose this issue, would you please provide these information?

    Additionally, another useful tool is the Process Monitor tool which can capture the access log.
    Filter on the process name dotNetFx40_Client_x86_x64.exe in the log so that you see only the related list. This should give you more information on what registry keys/ files are being accessed during the installation.

    If you have any concerns, please feel free to let me know.

    Best Regards,


    Andrew Wu [MSFT]
    MSDN Community Support | Feedback to us
    Get or Request Code Sample from Microsoft
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    • Marked as answer by Tony2008 Sunday, July 3, 2011 3:47 PM
    Wednesday, June 22, 2011 10:04 AM
    Moderator

All replies

  • I guess I don't understand your concern.

    As the installation occurs only once per computer, is installation speed really a concern? I could understand a speed concern if the lack of speed were associated with applications using the .NET Framework 4.0 Client Profile.

    Is your concern associated with an application you intend to distribute that requires the Client Profile as a prerequisite?

     

    Tuesday, June 21, 2011 5:37 PM
  • Yes, the installation occurs once, but somebody don't want to wait so long time.
    video edit
    Wednesday, June 22, 2011 12:08 AM
  • Hi Tony,

    Thanks for your post.

    Based on my experience, the installation speed of .NET Framework is depends on the hardware & software environment of the target machine, and what programs are running while installing .NET Framework. In order to help diagnose this issue, would you please provide these information?

    Additionally, another useful tool is the Process Monitor tool which can capture the access log.
    Filter on the process name dotNetFx40_Client_x86_x64.exe in the log so that you see only the related list. This should give you more information on what registry keys/ files are being accessed during the installation.

    If you have any concerns, please feel free to let me know.

    Best Regards,


    Andrew Wu [MSFT]
    MSDN Community Support | Feedback to us
    Get or Request Code Sample from Microsoft
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    • Marked as answer by Tony2008 Sunday, July 3, 2011 3:47 PM
    Wednesday, June 22, 2011 10:04 AM
    Moderator
  • Hi Tony,

    We have not heard from you in a couple of days. Would you mind letting me know the result of the suggestions?

    If you need further assistance, feel free to let me know. I will be more than happy to be of assistance.

    Best Regards,


    Andrew Wu [MSFT]
    MSDN Community Support | Feedback to us
    Get or Request Code Sample from Microsoft
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Friday, June 24, 2011 10:00 AM
    Moderator