When perform schema diff for 2 databases with Visual Studio Pro 2017, I'm facing with issue about schema diff timeout because the database in server too large, so the result always display no differences detected.
With Visual Studio 2015, I can workaround by increasing the "QueryTimeoutSeconds" in regedit and it's working as normally. But when upgrade to Visual Studio 2017, I can't find anywhere have this value
Have anyone experiance with this issue and have any solution workaround?
My environment:
- SQL Server 2017 Developer
- Visual Studio 2017 Pro
- SSDT 15.1.61710.120
After more investigation, I found that in Visual Studio 2017, we can updating QueryTimeoutSeconds in regedit, but a little configuration because Visual Studio 2017 already hive the regedit.
First, please close all Visual Studio 2017 application, after that, open regedit application.
Choose HKEY_LOCAL_MACHINE, click File and choose Load Hive, and paste the link to address: %LOCALAPPDATA%\Microsoft\VisualStudio\, select 15.xxx and choose privateregistry.bin -> Click Open.
Input VS_2017_LoadHive in the appeared dialog and click OK.
Expand HKEY_LOCAL_MACHINE > VS_2017_LoadHive, and find QueryTimeoutSeconds key under SQLDB > Database, after that increased the value to 6000.
After that, select File and choose Unload Hive.
Open Visual Studio 2017 again and enjoy.
Related
I am unable to start a debugging session for the Office project in Visual Studio 2019 but it work fine from the same project in VS 2017. We have the enterprise version for both if that matters. This presents itself with the basic Office Excel Addin project type so is easy to reproduce.
Environment
Windows 10 Enterprise V 1809 Build 17763.1457
Visual Studio Enterprise 2019 V 16.7.5
Visual Studio Enterprise 2017 V 15.9.27
Office 365 ProPlus
Excel V 2002 (Build 12527.21104)
Steps to Reproduce issue
Start VS 2019
Select Create New Project
Select Excel Web Add-in as the project type
Select Next
Name the solution or leave as default
Select Create
Choose Add new functionalities to Excel
Select Finish
Build the solution
Right-Click on the project file for the addin (the one with the orange office logo) and select Debug -> Start a new Instance
This error message pops up.
The Output window shows "Excel exited with code -1"
I have added runtime logging to Excel which indicates the addin loaded successfully.
My Google-fu has failed me in finding a resolution. Has anyone seen this or have an idea how to get it to work in VS 2019?
This is a side effect of the fact that the JavaScript console was removed from VS 2019. You have to debug some other way
I have Visual Studio 2017 Community 15.7.2 installed. The build configuration drop down options disappear. I have been having Problems with the build configuration disappearing on my work machine (Visual Studio 2017 Enterprise 15.8.2) as well.
If I create a new project File -> New Project -> Web -> ASP.Net Web Application (.Net Framework).
The build configuration option shows up. Then if I click on a controller class e.g. HomeController.cs. The option clears out.
The option will show up again after changing "Show output from" under the Output window. If I bring up a .cs file again. The build option disappears:
Is this now a normal behavior in Visual Studio? I suspect a bug in Visual Studio and have been updating more often than usual in attempt to fix it.
The latest update to Visual Studio Community 2017 (15.8.4) did not fix the problem.
Go through each of the Tools -> Extensions and Updates and disable an extension and then restart Visual Studio. Start with ones that aren't created by Microsoft.
Repeat this until you have tried all the extensions.
I inherited a project that was created in Visual Studio 2015 with SQL Server Data Tools version 14.
I'm running VS 2017 version 15.6.0 with SQL Server Data Tools 15.1.61801.210
When I try to open the solution it just fails with the below error message. What do I need to do in order to "upgrade" the solution so I can work with it?
Unsupported
This version of Visual Studio is unable to open the following projects. The project types may not be installed or this version of Visual Studio may not support them.
For more information on enabling these project types or otherwise migrating your assets, please see the details in the "Migration Report" displayed after clicking OK.
- LabSOR, "C:\Users\GROSCH\Documents\LabSOR\ETL\LabSOR_SSIS\LabSOR\LabSOR.dtproj"
No changes required
These projects can be opened in Visual Studio 2015, Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1 without changing them.
- LabSOR, "C:\Users\GROSCH\Documents\LabSOR\ETL\LabSOR_SSIS\LabSOR.sln"
Ended up the SSDT integration elements hadn't installed. Once I did that I could right-click on the project in the solution explorer and reload it, and then it started working.
I have Visual Studio 2015 and Visual Studio 2017 on my machine. I cannot see Builds under Team Explorer in Visual Studio 2017. I can see it in Visual Studio 2015. I was connected to the same collection and project and had the same credentials.
Please make sure that you are connected to team foundation server.
Go to Source Control Explorer and try opening the solution again after connecting to TFS.
Thanks!
According to your description, the situation is very likely you are opening a local project in VS2017.
Suggest you double check your project source control binding. You could try to unbind and rebind it. How to do this please refer this link.
You could also connect some other projects and collections in VS2017 to narrow down if the issue is only with that specific project.
I've installed x64 version of remote debugging components for Visual Studio 2015 on my Surface Pro 3 with Intel Core i3 CPU and recently updated to Windows 10 Pro Insider Preview x64.
When I'm trying to debug remotely simple universal application from Visual Studio 2015 RC (development machine runs Windows 8.1 Pro) I'm having this error in the output window:
Error: Unable to connect to the Microsoft Visual Studio Remote Debugger named '192.168.1.2:4020 (hosthame)'. The remote debugger is older than this version of Visual Studio 2015 RC, and Visual Studio is no longer compatible with it. Please upgrade your remote debugger to match Visual Studio.
Also there are records of failed attempt to connect in the main (log) window of Remote Debugging Monitor.
So, is there any "more updated" version of remove debugger component for Visual Studio 2015 RC then the current one I'm using, which, btw, has version 14.0.22310.1 and was "built by: DP" (have no idea what does it mean)?
Or any thoughts about other ways to workaround this issue?
I'm looking into installing Visual Studio on the Surface directly, but would like to avoid it if possible.
OK, I'll google next time harder - Remote Tools for Visual Studio 2015 RC (this link is no longer available, please use the links bellow).
Update (2016-06-28)
Remote Tools for Visual Studio 2015 Update 3:
Download (this link is no longer available, please use the links bellow)
Update (2016-09-28)
x64 - Remote Tools for Visual Studio 2015 Update 3
x86 - Remote Tools for Visual Studio 2015 Update 3
ARM - Remote Tools for Visual Studio 2015
Sevenate, your latest link is for the 2013 and not the 2015. Your second link still works, people just have to go to:
Tools for Visual Studio 2015->Remote Tools for Visual Studio 2015 and download the one for Update 3. I hope this helps