I have a VSTO for Excel project with a custom ribbon tab. The solution builds without errors. I can run the solution. It launches Excel and displays the custom ribbon tab and task pane without any issue.
When I try to open the designer for the custom ribbon tab in Visual Studio 2019, I get the following error:
Could not find type 'Microsoft.Office.Tools.Ribbon.RibbonTab'. Please
make sure the assembly that contains this type is referenced. If this
type is a part of a development project, make sure that the project
has been successfully built using the settings for your current
platform or Any CPU.
The solution builds and runs without any issues.
When I expand the error info, There is no stack trace or error line information available for this error.
The build settings are set to 'Any CPU'.
The assemblies that contain 'Microsoft.Office.Tools.Ribbon.RibbonTab' are included in the project references. These are Microsoft.Office.Tools.Common and Microsoft.Office.Tools.Common.v4.0.Utilities.
I have tried to Clean, Rebuild, and Restart Visual Studio 2019. This had no effect.
I could not find anything definitive when I Check Windows Forms Design-Time error list.
Would anyone know how to address this issue so that I can open the custom ribbon in the designer?
Is VSTO still supported by Microsoft? All documentation appears to be several years old.
This is a Visual Studio issue, not a C#/Build/DLL linkage issue.
Make sure your Visual Studio setup (do the Modify in the installer (#1) if already installed) has these two components checked:
Is VSTO still supported by Microsoft?
They are moving to an online office365 addin (my words) type VSTO. As to new features, not recently. One can still put in a Visual Studio support ticket if you have the right subscription.
I have never had any issues with ribbons, but sometimes the winforms res files in designer do not show and I use the JetBrains Rider editor to view those controls when VS fails.
I have created a COM DLL using the ATL project (Composite object) which basically has one tree control (which is a part of VS toolbox) within a dialog.
After registering it, I'm trying to insert it in a dialog based MFC/ATL application by using the standard approach of using "Insert ActiveX control" dialog of Visual Studio.
But the problem here is, even after its successful registration it is not getting listed in the "Insert ActiveX control" dialog. So I'm not able to insert it in the container dialog.
Alternatives that I've tried and that worked:
In a tool provided by Microsoft to test such controls i.e., "ActiveX control test container"(TSTCON32.exe), my COM DLL is getting listed properly and I'm able to use it.
Alternatives that I've tried and that not worked:
Un-registering the DLL and re-registering it back.
Rebooting the PC.
So, any help on this regard is warmly appreciated.
Couple more details:
Both ".idl" and ".rgs" file looks proper.
I will share my project if it is needed.
When you add an activeX control to your project, you must specify the ProgID in the ATL control wizard.
Here's the form in VS 2012 Update 5 for signing code. You get to it by right clicking a project, going to Properties and selecting the Signing tab. The form is only half displayed.
Suspecting this might be related to the fact I'm running this on a high DPI screen, I changed the resolution down. No difference. Also tried running VS in Windows 8 compatibility mode. No difference.
I could maybe edit the .csproj file directly but the schema link is broken. Thanks, Microsoft.
Anyone know a workaround? Have logged a bug in Connect.
I'm having real trouble when I try to use the IOS emulator from the visual studio. So I created a hello world app in VS using xamarin (latest stable version), I set the project as main project, and When I refresh the connexion with the mac, I can't select the device that should be shown in the selectList. The message is "No device attached" :
And if I try to use xamarin studio on the host mac, all is okay, the sample app builds on the iphone emulator:
Thanks to help me !
I know this question has already been answered, but i found it when i had a problem, and it did not help... but i did find the solution:
Under the debugging menu in VS2012, click on Configuration Manager
make sure that iPhone Simulator (or iPad, if you want) is set...
Default seems to be looking for a physical device...
hope this helps.
Are you sure the device is connected to the Mac and not the Windows machine? Have you tried debugging from that same device from Xamarin Studio on the Mac?
Had the same problem. Issue was when i loaded my solution, visual studio 2012 decided to choose a library project as the 'Startup project'.
Rt Clicked the ios project, chose 'Set as StartUp Project' and the device list was populated.
P.S: Visual Studio you should be old enough to figure this out by now.
When I ran into this problem, I had another instance of visual studio running which was connected to the Mac.
Apparently you can only have on VS instance connected at a time.
Check your server log in Visual Studio output window for some more clues:
Closing the other instance of Visual Studio allowed me to connect in the instance I wanted to debug in
I discovered something missing. For me, in Visual Studio 2013, for some reason they have removed Solution Platforms from the toolbar. This makes it impossible to switch from iPhone to iPhoneSimulator without opening Configuration Manager. So, to fix this.
Click TOOLS/Customize then select the 'Commands' tab then select the 'Toolbar:' radio button and click the dropdown to the right of it and select 'Standard' as the toolbar you're working on.
Now, click 'Add Command' and select 'Build' from the catagories on the left and then scroll down commands until you find 'Solution Platforms'. Select that one and click OK. Then click the 'Close' button. You will now see an additional dropdown next to the Solution Configurations dropdown on your Standard Toolbar.
This will allow you to easily switch from iPhoneSimulator and iPhone. Use iPhone when you want to plug in an actual device, and use iPhoneSimulator when you want to pick a simulated device.
Hope this helps somebody out. I too have spent lots of time trying to figure this one out when I went from a device and was trying to use the simulator instead.
Restarting of Visual Studio 2010 worked for me.
Different things worked for me (Windows 8.1 & Visual Studio 2013):
Restart Visual Studio
Set 'iPhoneSimulator' as platform (only working one)
In Properties - iOS Application change 'Deployment Target' version to some lower number (6.0 worked for me).
As well as checking you have the right startup project selected as per #Chamkila's answer, check that you haven't accidentally broken your project's Info.plist file by attempting to open it through Visual Studio.
I'm test-driving Visual Studio 11 beta and it appears I've hit a major snag.
Has anyone tried opening an actual production WPF project that contains WPF windows with User Controls? When I try to open a WPF Window or control that contains user controls, the design view displays a nice error message:
"Design view is unavailable for x64 and ARM target platforms because the document contains custom elements."
It appears to be a major wtf... since most developer machines these days are x64.
* UPDATE: *
Reproduced this in a new VS 2011 WPF project:
Add a xaml resourec file with styles (in the same project as the user control)
Reference this file in a user control using the tag
Immediately, the "Design view is unavailable for x64 and ARM target platforms..." pops up.
As soon as I remove the resource reference, the designer starts working again.
The "x64 or ARM" in the message refers to the current target configuration of the project, not to the machine on which Visual Studio is running. That is, if you change the target platform configuration of the project to x86 or Any CPU, you should not get this message.
You can change the target platform from the Standard Toolbar (select the "Add or Remove Buttons" item at the end of the toolbar, and select "Solution Platforms").
If your solution platform is x86 or Any CPU, please add a comment to this post and let me know. I'd be interested in investigating.
I resolved this by doing the following in Visual Studio:
Select the solution node within Solution Explorer.
Within the Properties pane, set "Active config" to an x86 processor type.
Display Properties for application project.
Select the Build tab on the navigation pane.
Ensure "Platform target" is set to x86.
After completing these steps:
Restart Expression Blend.
Observe the designer is now loaded with UI