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.

code generation for property 'VisuaStyle' failed

Thread ID:

Created:

Updated:

Platform:

Replies:

122096 Feb 16,2016 06:55 PM Nov 14,2017 04:26 AM Windows Forms 3
loading
Tags: EditControl
chri
Asked On February 16, 2016 06:55 PM

Hi,
I just installed Syncfusion and am looking forward to exploring it, but I seem to be having a problem.
Setup:
Vs 2015 community edition
Windows 10 Fast Track
Steps:
1. DOwnloaded and installedSYncfussion Essential Stufio 13.4.0.53
2. Created a Winforms project
3. Build and run =>OK
4. Drag a syncfusion EditControl onto the frm
5. Try to build and run -> Error:
Code generation for property 'VisualStyle' failed. "Type 'Syncfusion.Windows.Forms.Tools.Controls.StatusBar.VisualStyle' is not available in the target frameworl
I tried changing from the default Debug|AnyCPU to Debug|x86 and Debug|x86
The following syncfusion references are in the project:
Syncfusion.Edit.Windows
Syncfusion.Shared.Base
Syncfusion.Tools.Windows
All are set to Copy Local == true
The InitailizeComponent code for the form is:
privatevoidInitializeComponent()
{
Syncfusion.Windows.Forms.Edit.Implementation.Config.Configconfig3=newSyncfusion.Windows.Forms.Edit.Implementation.Config.Config();
this.editControl1=newSyncfusion.Windows.Forms.Edit.EditControl();
((System.ComponentModel.ISupportInitialize)(this.editControl1)).BeginInit();
this.SuspendLayout();
//
//editControl1
//
this.editControl1.CodeSnipptSize=newSystem.Drawing.Size(100,100);
this.editControl1.Configurator=config3;
this.editControl1.ContextChoiceForeColor=System.Drawing.SystemColors.InfoText;
this.editControl1.IndicatorMarginBackColor=System.Drawing.Color.Empty;
this.editControl1.LineNumbersFont=newSystem.Drawing.Font("MicrosoftSansSerif",8.25F,System.Drawing.FontStyle.Regular,System.Drawing.GraphicsUnit.Point,((byte)(204)));
this.editControl1.Location=newSystem.Drawing.Point(128,132);
this.editControl1.Name="editControl1";
this.editControl1.RenderRightToLeft=false;
this.editControl1.ScrollPosition=newSystem.Drawing.Point(0,0);
this.editControl1.Size=newSystem.Drawing.Size(528,360);
this.editControl1.StatusBarSettings.CoordsPanel.Width=150;
this.editControl1.StatusBarSettings.EncodingPanel.Width=100;
this.editControl1.StatusBarSettings.FileNamePanel.Width=100;
this.editControl1.StatusBarSettings.InsertPanel.Width=33;
this.editControl1.StatusBarSettings.StatusPanel.Width=70;
this.editControl1.StatusBarSettings.TextPanel.Width=214;
this.editControl1.TabIndex=0;
this.editControl1.Text="editControl1";
this.editControl1.UseXPStyleBorder=true;
this.editControl1.VisualColumn=13;
this.editControl1.Load+=newSystem.EventHandler(this.editControl1_Load);
//
//Form1
//
this.AutoScaleDimensions=newSystem.Drawing.SizeF(12F,25F);
this.AutoScaleMode=System.Windows.Forms.AutoScaleMode.Font;
this.ClientSize=newSystem.Drawing.Size(941,837);
this.Controls.Add(this.editControl1);
this.Name="Form1";
this.Text="Form1";
((System.ComponentModel.ISupportInitialize)(this.editControl1)).EndInit();
this.ResumeLayout(false);
 
}

Anybdoy have any ideas?  I uninstalled and reinstalled a couple of times with the same results.

Thanks,
WCM

Senthil Kumaran Rajan [Syncfusion]
Replied On February 17, 2016 04:57 AM

Hi Chri,

Thanks for contacting Syncfusion Support.

This reported behavior may occurs when application reference assembly version is not common. So Essential studio and Framework version of added assembly needs to be common and Specific version as False. Can you please below screen shot and ensure this?

                    

And follow below steps.

1.     Close the application.
2.     Delete Bin and Obj folders in application.
3.     Reopen the application.
4.     Rebuild your project.
5.     Check once again to see whether the project refers to the Syncfusion assemblies of installed version and try the same.
Can you check with the above solution and let us know whether the reported behavior is resolved? If not can you please confirm whether you have refereed the assemblies from GAC or any local reference and if more than on Syncfusion Essential studio setup is installed? That will be helpful for us to analyze and provide prompt solution as earlier as possible.

Regards,
Senthil

Nifal Munzir
Replied On November 12, 2017 11:56 PM

Hi Chri,

Thanks for contacting Syncfusion Support.

This reported behavior may occurs when application reference assembly version is not common. So Essential studio and Framework version of added assembly needs to be common and Specific version as False. Can you please below screen shot and ensure this?

                    

And follow below steps.

1.     Close the application.
2.     Delete Bin and Obj folders in application.
3.     Reopen the application.
4.     Rebuild your project.
5.     Check once again to see whether the project refers to the Syncfusion assemblies of installed version and try the same.
Can you check with the above solution and let us know whether the reported behavior is resolved? If not can you please confirm whether you have refereed the assemblies from GAC or any local reference and if more than on Syncfusion Essential studio setup is installed? That will be helpful for us to analyze and provide prompt solution as earlier as possible.

Regards,
Senthil

Hi!

as you said I checked the version and it is correct so what is the cause. for you reference i have attached the screenshot as well.



Mallika Kannan [Syncfusion]
Replied On November 14, 2017 04:26 AM

Hi Chri   
   
Thank you for your update.   
   
Please find the details in below,   
   
Query   
Comments   
as you said I checked the version and it is correct   
We are glad to hear that the reported problem solved at your end.     
   
what is the cause. for you reference i have attached the screenshot as well.   
Thus the reported “Code generation for property ” exception is not issue with control and this issue will occur only when the below cases,   
   
  1. Either Older Installed Essential Studio is not uninstalled properly or New Essential Studio is not installed properly.  
  1. One or more EssentialStudio is installed on same system.
  2. Application refers to the older version of assemblies even after upgrading to a higher version. 
  3. Visual Studio ToolBox is not configured properly.
   
So we suggested this solution.    
   
Please let us know if you need any other assistance.   
   
Regards,   
Mallika   



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.

;