- 
                Notifications
    
You must be signed in to change notification settings  - Fork 4.2k
 
Disable NuGet restore within Visual Studio #44523
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| 
           @sharwell The bug you're tagging in dotnet/arcade is already closed -- does that mean the underlying bug is fixed? If so, can we consume that fix? If not, do we have a bug on the appropriate team to investigate?  | 
    
| 
           @jasonmalinowski We don't use that version of arcade. Even if we did, arcade continues to deviate further from what Visual Studio does so today it still would not fix all cases. It appears that dotnet/arcade is generally incompatible with NuGet restore inside Visual Studio.  | 
    
          
 Why not? 
 Let's get the bugs filed then; we shouldn't be having to disable this long term.  | 
    
          
 
 Filed dotnet/arcade#5550  | 
    
          
 Do you meant that Roslyn is on 1.x reversion vs 5.x which is Arcade master? If so, any fix i Arcade master can (should) be ported to Arcade release/3.x branch (1.x version).  | 
    
| 
           Ping @tmat for review  | 
    
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to be clear this is a workaround and have a plan how to remove it.
The in-IDE restore operation does not produce bitwise identical results to the command line Restore.cmd script, which results in unavoidable performance degradations during daily developer scenarios such as branch switches and merges. This change disables the IDE restore operation, so all experiences rely on the Restore.cmd script for uniform behavior.
| 
           @tmat I believe I can work around this issue by disabling NuGet as a local IDE setting. We only need to merge this if one of the following two things occurs: 
  | 
    
| 
           Could you please share where to find the IDE setting that disables implicit NuGet restore?  | 
    
The in-IDE restore operation does not produce bitwise identical results to the command line Restore.cmd script, which results in unavoidable performance degradations during daily developer scenarios such as branch switches and merges. This change disables the IDE restore operation, so all experiences rely on the Restore.cmd script for uniform behavior.
Unblocks #44034
See dotnet/arcade#5172