Microsoft Visual Studio 2012 Unspecified Error
Contents |
SQL Server 2014 Express resources Windows Server 2012 resources Programs MSDN subscriptions Overview Benefits Administrators Students Microsoft Imagine Microsoft Student Partners ISV Startups TechRewards Events Community Magazine Forums Blogs Channel 9 Documentation APIs and reference Dev centers Samples Retired content We’re visual studio 2015 unspecified error sorry. The content you requested has been removed. You’ll be auto redirected in 1
Unspecified Error Exception From Hresult Visual Studio
second. Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered change source control by: unspecified error on open solution in visual studio 2012 Archived Forums V > Visual C# IDE Question 0 Sign in to vote When I try to open solution in Visual Studio 2012 RTM I
Microsoft Visual Studio 2015 Unspecified Error
see 'Unspecified error' message on some projects initializing. How can I see more info about this error? Thursday, June 28, 2012 6:50 PM Answers 2 Sign in to vote I managed to find a solution that works for us. Having tried safe mode, and attaching another VS instance to debug - and getting nowhere, it occurred to me the only difference between my main solution that errors, and other hresult = 0x80004005 - e_fail that don't is source control (TFS 11 in this case). So, I unbound the projects (select solution file, then File -> Source Control -> Advanced -> Change Source Control), and then rebound them. They now appear to be complete fine. I don't know if this was an ordering thing (TFS/ VS Beta to RC, and then RTM), or it was just a bad upgrade but it now seems fine. Thanks, Kieron Proposed as answer by b33rdy Monday, August 20, 2012 1:21 PM Marked as answer by Mukminoff Wednesday, August 22, 2012 8:44 AM Monday, August 20, 2012 11:43 AM 0 Sign in to vote Some project types are no longer supported so you can get this message. This includes setup projects and any database projects not created using SSDT. It will also include any project types that ship outside VS as they most likely don't recognize VS2012 as it hasn't been released yet. Additionally when you open the solution the first time you'll get an upgrade log. You should look at the log to see what errors were generated. Michael Taylor - 6/3/2012 http://msmvps.com/blogs/p3net Proposed as answer by Jason Dot WangMicrosoft contingent staff, Moderator Wednesday, July 04, 2012 2:47 AM Marked as answer by Jaso
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and
Visual Studio 2015 Change Source Control
policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a https://social.msdn.microsoft.com/Forums/en-US/d2312f94-a547-4bda-abae-e8c0fe407c9e/unspecified-error-on-open-solution-in-visual-studio-2012?forum=csharpide minute: Sign up VS2013 or VS2015 shows “unspecified error” up vote 12 down vote favorite 2 When I open my worked solution (after merge from other branch) VS2013 shows error message "unspecified error" and I cannot close the window (the error's dialog jumps each time when I close it). VS2012 opens the solution without error messages. I suspect issue related to http://stackoverflow.com/questions/28926888/vs2013-or-vs2015-shows-unspecified-error TFS configuration. How can I found actual reason of the error? visual-studio-2013 tfs visual-studio-2015 share|improve this question edited Dec 21 '15 at 8:40 Richard 72.8k13113185 asked Mar 8 '15 at 13:21 constructor 537420 I changed permissions on the folder & rebooted - this fixed it for me. –niico Oct 3 at 14:48 add a comment| 3 Answers 3 active oldest votes up vote 9 down vote accepted I still don't understand the actual reason for this error, but I found a workaround. According to "Change source control" window (VS) solution file (.sln) not connected to TFS When I connected the solution to TFS in VS2012 (with the help of this link), VS2013 opened the solution too without error message. share|improve this answer edited May 5 at 6:34 ParPar 3,36642536 answered Mar 9 '15 at 11:06 constructor 537420 add a comment| up vote 3 down vote I have searched a lot about its root cause but couldn't found any concrete information. For me, Deleting the solution's .suo file. resolve this problem. share|improve this answer answered Jul 7 at 10:42 Geeky Ninja 1,0411
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss http://stackoverflow.com/questions/15958143/what-does-vs-project-binding-do the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions http://weblogs.asp.net/jeffwids/unexpected-error-encountered-opening-visual-studio-project Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. visual studio Join them; it only takes a minute: Sign up What does VS project binding do? up vote 5 down vote favorite What does Visual Studio's unbind | bind operation do to projects in a solution.suo file? Microsoft provides instructions on How to: Bind or Unbind a Solution or Project, which happens to remedy the dreaded "Unspecified Error" that visual studio 2015 occurs at solution opening. This MSDN forum posting has a user stating they unbound and then re-bound their projects in order to solve that problem. As I was experiencing the same "Unspecified Error" problem, I did some additional digging and found that the solution.suo file was the only likely candidate that had changed after I had resolved the issue. I read this answer to an SO question about .suo files being effectively disposable and happened to be able to recreate the UE problem through a stale workspace I had laying around. So I went ahead and deleted the solution.suo file and opened the solution.sln file. Magically, my UE problem had gone away with that workspace too. That led me to conclude unbind | bind has some sort of effect on the .suo file, but because of the files binary, proprietary structure I wasn't able to identify what's going on. My Questions: 1. So what exactly does Visual Studio's unbind | bind operation do to projects in a solution.suo file? 2. Can anyone surmise what'
and received an error message: Followed by this error message: And then the Visual Studio project was not available in the solution. All the project said was “The project file cannot be loaded.” Not a very helpful error message. This is because the project was under Team Foundation Server (TFS) source control and I do not have the TFS edition of Visual Studio. To resolve this issue open the project files in notepad and remove the source control provider lines. Usually they look like this: