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.
Related
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 use ResXFileCodeGeneratorEx for generating ids. This was working till the time I used Visual Studio 2010 IDE but it is not working for Visual Studio 2017.
Please help for the same.
Extension for Visual Studio 2019 can be found here
Extension for Visual Studio 2017 can be found here
The deleted answer to this question pointed to the location of a newly built ResXFileCodeGeneratorEx but was deleted because it only contained a single link and no context. I'm not the original answerer, but figured that it may still be valuable to have this information:
It seems to have been renamed to ResXCodeFileGeneratorEx, and if you search through the menu in Visual Studio under Tools > Extension and Updates, you need to search for "Extended Strongly Typed Resource Generator".
However, the internal name is still the same, so the Custom Tool action should remain ResXFileCodeGeneratorEx.
I'm not aware whether or not it works on Visual Studio 2019, but since the original source is still around, it oughtn't be too hard to resolve that yourself if you need it.
To install it, simply doubleclick the VSIX file, it will popup with the VS Version Instance Selector, where you can select to which of your VS 2017 instances (pro, community, preview) you want to install the extension to.
Reporting template Component (RDLC) not exists to as New Item in Visual Studio 2017 Enterprise.
How to resolve this?
I have tried by installing SQL Server Data Tools.
Previously it works for me in Visual Studio 2015.
There is a bug in the extension Microsoft Rdlc Report Designer for Visual Studio that the ReportViewer shows up as a non-visual component.
Instead use the NuGet Package Microsoft.ReportingServices.ReportViewerControl.WinForms for each project that will use the ReportViewer. Part of the solution involves removing the ReportViewer from the toolbox after use and restarting Visual Studio before opening the next project/solution.
Please see this answer to a similar question for step by step details.
The RDLC editor for VS2017 is only available as a VSIX installer from the marketplace: Download
I have just used VS2015 to add the new item. All other stuff seems to be fine in VS2017 (bearing in mind that you installed the VSIX extension)
I suppose since I installed Visual Studio 2012, I cannot create C++ project in Visual Studio 2010. But, I am not sure new installation of VS 2012 is related to this problem.
The problem I am really struggling is that neither hint message nor notification are shown when I try to create a new C++ project.
I have tried several ways from google even include stackoverflow, but failed.
Is there anyone who knows any solutions or has any workarounds?
1) I wouldn't be at all surprised if installing MSVS 2012 is the culprit. VMs are Good :)
2) You should definitely look at the Windows event log (if you haven't already)
3) You can also run MSVS 2010 with logging as follows:
http://msdn.microsoft.com/en-us/library/ms241272%28VS.80%29.aspx
Devenv.exe /log "C:\My Files\MyLog.txt"
i faced the same problem in "microsoft visual studio express 2012 for window desktop" and now it's perfectly working after having gone through repair option.
If you have another version (or express edition) of visual studio installed on the same PC that is previously used to create console applications, that might be the issue. I had the same issue and I had Visual C++ 2008 on the same computer and I could either use the visual C++ for console applications or uninstall it completely. Hope this helps!