We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy.
Unfortunately, activation email could not send to your email. Please try again.

Upgrade causes The tag 'ComboBoxAdv' does not exist in XML namespace 'http://schemas.syncfusion.com/wpf'.

Thread ID:

Created:

Updated:

Platform:

Replies:

124349 Jun 2,2016 07:55 AM Jun 3,2016 01:33 AM WPF 2
loading
Tags: ComboBoxAdv
Dhimant Patel
Asked On June 2, 2016 07:55 AM

Hi All,
I upgraded to the latest version of syncfusion 14.1460.0.46.
After that even a brand new WPF project (which builds successfully), now shows above error right after dropping a control from Toolbox.

Here is the complete xaml:
-------------------------------------------------------------------------------------------
<Window xmlns:syncfusion="http://schemas.syncfusion.com/wpf"  x:Class="WpfApplication3.MainWindow"
        xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
        xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
        xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
        xmlns:local="clr-namespace:WpfApplication3"
        mc:Ignorable="d"
        Title="MainWindow" Height="350" Width="525">
    <Grid>
        <syncfusion:ComboBoxAdv />
    </Grid>
</Window>
-------------------------------------------------------------------------------------------------------
Target framework is set to ".Net Framework 4.5.2" in the project properties.
Dragging and droppoing of ComboBoxAdv control adds "Syncfusion.Shared.WPF" assembly in the References, with path "C:\Program Files (x86)\Syncfusion\Essential Studio\14.1.0.46\Assemblies\4.6\Syncfusion.Shared.WPF.dll".

Any suggestions on how to painlessly upgrade the software and projects?

Thanks in advance!
-DP.


Dhimant Patel
Replied On June 2, 2016 08:22 AM

Ok, found the solution, that will become my #1 rule after any sort of upgrade on base frameworks.

The reason was all projects were targeting the then latest .Net framework "4.5.2", in the project properties.

So the rule becomes, after upgrade, just hit to the project properties and change the target framework to the latest available.

Had I paid enough attentions to "Warnings", it actually tells the problem very clearly.

Happy programming!




Jegan Raj M [Syncfusion]
Replied On June 3, 2016 01:33 AM

Hi Dhimant,

Yes, Framework version is the problem and you have solved this. Thanks for your update. Please log new ticket if you have any other queries.

Regards,
Jegan Raj M

CONFIRMATION

This post will be permanently deleted. Are you sure you want to continue?

Sorry, An error occured while processing your request. Please try again later.

You are using an outdated version of Internet Explorer that may not display all features of this and other websites. Upgrade to Internet Explorer 8 or newer for a better experience.

;