I am trying to edit some storyboards I created in visual studio community 2017 for Mac.
The problem is that I keep getting an error.
I'm sure I have some declarations wrong, the problem is that I can't see the full error
When I press open with-> Xcode Interface Builder, I get an error on the top of the screen and can't see the rest of it.
This is what I see:
Is there anyway to see the full error or something more specific than an one line message?
Related
Visual Studio 2019 Community 16.8.4 crashes when drag and drop Document Tab.
I have re-installed VS 2019 Community and it does not fix the problem. I have been using 2019 Community for a year now with no problem. Not sure if it is related to 16.8.4 or not.
Has anyone else had this problem? If so have you figured out how to fix it?
[Workaround]
Edit %InstallRoot%\Common7\IDE\devenv.exe.config and %LocalAppData%\Microsoft\VisualStudio\16.0_xxx\devenv.exe.config and append the following text to the AppContextSwitchOverrides element’s value attribute:
;Switch.System.Windows.Interop.MouseInput.OptOutOfMoveToChromedWindowFix=true;Switch.System.Windows.Interop.MouseInput.DoNotOptOutOfMoveToChromedWindowFix=true
After restarting VS, you should be able to drag your VS windows around without crashing.
https://developercommunity2.visualstudio.com/t/Unexpected-VS-crash-when-docking-or-spli/1323017#T-N1330689
Indeed fixed in 16.8.5 as specified here: https://developercommunity2.visualstudio.com/t/Unexpected-VS-crash-when-docking-or-spli/1323017
It's just started doing it today, been fine on this version up to this point. It only seems to be the docking so I have Visual Studio on the left hand side of the screen then I'm floating editor windows on the right. Seems to be OK like that.
I have VS2015 and the updates that are supposedly causing the crash weren't installed. Instead I got KB5001028 and KB4601056 installed on the 15th and docking any windows in Visual Studio crashed immediately. Removing those updates fixed the crashing partially. Now I'll get random crashes when docking and immediately switching windows, but not always.
Updating visual studio 2017 to its latest minor version, fixed issue for me.
For those who can't find a solution shall try this.
For me, none of the solutions worked. I've updated to latest version and even tried all windows updates recommended.
Finally I figured it out that it was due to eXtra Buttons application. Once the eXtra Buttons is closed, everything was back to normal. Please share if this fix works.
Environment:
Windows 10 2004
Visual Studio Enterprise 2019 16.7.6
TFS 2018.2 on Windows 2019 Server
I have a VS 2019 solution containing 14 C# projects. All of the projects are in TFS. For some reason one project is not showing in Solution Explorer as being in TFS (no lock icon). At one time it did show, sometime in the last month the lock disappeared. If I use Source Control Explorer in VS2019, I can navigate to the project and perform TDS operations on it.
If right click on the project on go to Source Control -> Add to Source Control I get an error window that simply says "Unspecified Error". Is there someplace I can look to find the error?
If there is any additional information I can provide, please let me know.
Thank you,
Eric
Thanks, G-P The link at VS2013 or VS2015 shows "unspecified error" fixed the issue. I should have widened my search to older versions. Another life lesson.
Thanks again,
Eric.
I have an IOS app-project developed using Xamarin for Visual Studio 2013 which I haven't opened for about a year. Now I have to make some changes to the app and after some problems compiling the project I installed all available updates for Xamarin and Visual Studio 2013, but that only made things worse so I decided to install Visual Studio 2015 and update the Mac and Xcode to the latest version.
Installing VS2015 seemed to solve all my previous problems and I can now compile the project and run it fine (in VS2015), but when I open the storyboard (there is only one in the project) I get a yellow warning bar at the top that says Custom components are not being rendered because problems were detected.
I have no idea why this message appears since I only use standard components (or maybe "components" means something else than those in the Toolbox?). Does anyone know what the reason for this message is, how can I troubleshoot and get rid of it?
I should add that I'm not an experienced IOS developer.
I cannot see the story board in Visual Studio 2013, when I open it it tells me
There was a problem rendering this document.
Also in the errors list I have the following:
The clocks on the Build Host and this Machine are out of Sync. Please make sure they are within 3 minutes (UTC) of each other.
Failed to retrieve SDK status from server Xamarin.iOS Extension.
Also the output from the MAC server log tells me:
Error sending iOS designer payload
What can be wrong here?
I was also having a similar problem where I couldn't open the story board in Visual Studio 2012 or 2013 (I didn't have any errors in my error list, just the error when displaying the designer). My setup is dev work in Windows 7 with Visual Studio 2012/2013 with a Mac acting as a Build Host. I had just updated my Xamarin version from 3.0.54 to version 3.3.47 (it had been a little while) and I had created a little prototype app a couple days ago with no problems, so I figured I had killed something with the update.
In my case, the solution was checking for updates in Xamarin Studio on the Mac, where it found several that needed updated. After installing the updates on the Mac side, I was able to display my story board in both Visual Studio 2012/2013 without issues... so I chalked it up to version mismatch issues between the Build Host and my dev environment in Windows.
I am using Visual Studio 2003 and I having a strange problem. I have a solution file in which several projects are added. However, due to some corruption, i cannot see the properties of one project. It gives a message box saying "unspecified error" when i try to check the properties of that project. The delete option of the project is also disabled. Can anyone knows what exactly went wrong ? Any help will be highly appreciated.