Visual Studio Errors? Look Here First.

Ribbon for WPF Forum

Posted 12 years ago by Actipro Software Support - Cleveland, OH, USA
Avatar
There are two types of errors that can occur in Visual Studio. If you are having any problems, please check out this posting first and if this doesn't help resolve the issue, please contact us immediately for further assistance.

We are including this information in Troubleshooting topics in the products as well in current or future builds.

Visual Studio Error When Opening the Sample Project

The following error will display if you don't have the Visual Studio 2005 Orcas extensions (or a newer VS 2005 Orcas release) installed when opening the control's sample project:
The project file ? cannot be opened. The project type is not supported by this installation.
If you have regular VS 2005 or VS 2005 with SP1, then you can download the Visual Studio 2005 extensions for .NET Framework 3.0 (WCF & WPF), November 2006 CTP from this page:
http://msdn2.microsoft.com/en-us/vstudio/aa700831.aspx

Install that and Visual Studio will be able to load the project.

Errors When Compiling XAML File in VS Cider Designer

Error messages might include these types of messages or others while a XAML file is open using the "Cider" designer:
Assembly '' was not found. The 'clr-namespace' URI refers to an assembly that is not referenced by the project.
The type 'sample:RibbonDemo' was not found. Verify that you are not missing an assembly reference.
If you are using the Orcas extensions in your VS installation, then this is a known issue. The problem is that Microsoft's November Orcas extensions only process built-in System WPF controls and do not handle third-party controls properly. This issue is fixed by Microsoft in actual Orcas beta builds and will be fixed for the final Visual Studio update due in late 2007.

The workaround is the close all your XAML files before compiling your project. This way, the Microsoft "Cider" code doesn't generate the errors.

To make editing XAML easier, we recommend that you open your XAML files that use our controls with the regular VS XML editor instead of the "Cider" editor. You still get the intellisense features and it loads XAML files quicker. To open a XAML file using the VS XML editor, right click on the file and choose Open With.... Then pick XML Editor in the dialog that appears. We also recommend setting it as the default for XAML files.


Actipro Software Support

Comments (1)

Posted 12 years ago by Actipro Software Support - Cleveland, OH, USA
Avatar
Some more information... the March CTP of Visual Studio Orcas does not throw incorrect errors and warnings like the November extensions do. Also the March CTP has Intellisense for third party controls like ours.


Actipro Software Support

The latest build of this product (v2019.1 build 0681) was released 1 month ago, which was after the last post in this thread.

Add Comment

Please log in to a validated account to post comments.