Professional UI Solutions
Site Map   /  Register
 
  

Forum

Please Log In to post a new message or reply to an existing one. If you are not registered, please register.

NOTE: Some forums may be read-only if you are not currently subscribed to our technical support services.

Forums » Elegant Ribbon Tech Support » Upgrade from v3.6 to v3.7 issues. Collapse All
Subject Author Date
Paddy Jul 29, 2010 - 12:30 AM

I am not able to upgrade to the recent release successfully.  I get major errors when trying to run any program project after upgrade but not before upgrade.  I also got this same problem when upgrading from v3.1 to v3.6.  If I remove the upgrade and go back to the previous release, everything is perfectly fine.



When I run the installer, I am told "A previous version of the product is currently installed on this computer.  Press Yes to uninstall it or No to quit the installation."



If I click No, of course the installer quits.  If I click Yes, the previous release is removed and the new release is installed.  However, this is the problem I continuously have with your product.... My application is now COMPLETELY useless and has to be REWRITTEN.



I don’t have the time or the energy to rewrite the application from scratch with each upgrade.  I shouldn’t have to rewrite anything.  As a note, when I do any upgrade, VB.NET 2005 Pro is not running/launched when the upgrade is going through.



The error I get when launching my application project in VB.NET 2005 Pro on every single form is the following:

frmWorkLogEntryStart.vb [Design]


<html><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=UTF-8"><title></title><style>.ErrorStyle { font-family: tahoma; font-size: 11 pt; text-align: left}.DetailsStyle { font-family: tahoma; font-size: 10pt; text-align: left;text-indent: 0; word-spacing: 0; line-height: 100%; float: left; margin-top: 0; margin-bottom: 0}.StackStyleVisible { font-family: tahoma; font-size: 10pt; text-align: left; margin-left: 20; text-indent: 0}.StackStyleHidden { display:none; font-family: tahoma; font-size: 10pt; text-align: left; margin-left: 20; text-indent: 0}</style></head><body><DIV class="DetailsStyle" width="100%"><table border="0" width="100%" id="table1" height="100%" cellspacing="0" cellpadding="0"><tr><td height="40" bgcolor="#FF9999" width="8%" style="letter-spacing: 0" align="center"><img border="0" src="C:\Users\Paddy\AppData\Local\Temp\113E14F.tmp" width="35" height="35" alt="ErrorImage" ></td><td height="40" bgcolor="#FF9999" width="91%" style="vertical-align: top; letter-spacing: 0" align="left"><b><font size="2" face="Arial" fontsize="70%">One or more errors encountered while loading the designer. The errors are listed below. Some errors can be fixed by rebuilding your project, while others may require code changes.</font><font size="2" face="Arial"></font></b></td></tr><tr><td colspan="2" align="left" valign="top"><DIV id="div1" class="ErrorStyle" width="100%"><span style="font-weight: 600"><br>The designer cannot process the code at line 34: 

Me.pnlFormBackground.Dock = System.Windows.Forms.DockStyle.Fill


The code within the method ’InitializeComponent’ is generated by the designer and should not be manually modified.  Please remove any changes and try opening the designer again. </span><br><a href="" id="details0">Hide</a><font color="#0000FF">   &nbsp</font><a href="" id="task0">Edit</a><font color="#0000FF"></font></span></DIV> </td> </tr> <tr><td colspan="2" align="left" valign="top"><DIV id="div20" class="StackStyleVisible" width="100%"><br>   at Microsoft.VisualStudio.Design.Serialization.CodeDom.XML.CodeDomXmlProcessor.CreateQuoteExpression(XmlElementData xmlElement)<br>   at Microsoft.VisualStudio.Design.Serialization.CodeDom.XML.CodeDomXmlProcessor.XmlElementData.get_CodeDomElement()<br>   at Microsoft.VisualStudio.Design.Serialization.CodeDom.XML.CodeDomXmlProcessor.EndElement(String prefix, String name, String urn)<br>   at Microsoft.VisualStudio.Design.Serialization.CodeDom.XML.CodeDomXmlProcessor.Parse(XmlReader reader)<br>   at Microsoft.VisualStudio.Design.Serialization.CodeDom.XML.CodeDomXmlProcessor.ParseXml(String xmlStream, CodeStatementCollection statementCollection, String fileName, String methodName)<br>   at Microsoft.VisualStudio.Design.Serialization.CodeDom.VSCodeDomParser.OnMethodPopulateStatements(Object sender, EventArgs e)<br>   at System.CodeDom.CodeMemberMethod.get_Statements()<br>   at System.ComponentModel.Design.Serialization.TypeCodeDomSerializer.Deserialize(IDesignerSerializationManager manager, CodeTypeDeclaration declaration)<br>   at System.ComponentModel.Design.Serialization.CodeDomDesignerLoader.PerformLoad(IDesignerSerializationManager manager)<br>   at Microsoft.VisualStudio.Design.Serialization.CodeDom.VSCodeDomDesignerLoader.PerformLoad(IDesignerSerializationManager serializationManager)<br>   at Microsoft.VisualStudio.Design.Serialization.CodeDom.VSCodeDomDesignerLoader.DeferredLoadHandler.Microsoft.VisualStudio.TextManager.Interop.IVsTextBufferDataEvents.OnLoadCompleted(Int32 fReload)</DIV></td></tr></table></div></body></html>

frmWorkLogEntry.vb [Design]


<html><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=UTF-8"><title></title><style>.ErrorStyle { font-family: tahoma; font-size: 11 pt; text-align: left}.DetailsStyle { font-family: tahoma; font-size: 10pt; text-align: left;text-indent: 0; word-spacing: 0; line-height: 100%; float: left; margin-top: 0; margin-bottom: 0}.StackStyleVisible { font-family: tahoma; font-size: 10pt; text-align: left; margin-left: 20; text-indent: 0}.StackStyleHidden { display:none; font-family: tahoma; font-size: 10pt; text-align: left; margin-left: 20; text-indent: 0}</style></head><body><DIV class="DetailsStyle" width="100%"><table border="0" width="100%" id="table1" height="100%" cellspacing="0" cellpadding="0"><tr><td height="40" bgcolor="#FF9999" width="8%" style="letter-spacing: 0" align="center"><img border="0" src="C:\Users\Paddy\AppData\Local\Temp\223DDF3.tmp" width="35" height="35" alt="ErrorImage" ></td><td height="40" bgcolor="#FF9999" width="91%" style="vertical-align: top; letter-spacing: 0" align="left"><b><font size="2" face="Arial" fontsize="70%">One or more errors encountered while loading the designer. The errors are listed below. Some errors can be fixed by rebuilding your project, while others may require code changes.</font><font size="2" face="Arial"></font></b></td></tr><tr><td colspan="2" align="left" valign="top"><DIV id="div1" class="ErrorStyle" width="100%"><span style="font-weight: 600"><br>The designer cannot process the code at line 55: 

Me.pnlFormBackground.Dock = System.Windows.Forms.DockStyle.Fill


The code within the method ’InitializeComponent’ is generated by the designer and should not be manually modified.  Please remove any changes and try opening the designer again. </span><br><a href="" id="details0">Hide</a><font color="#0000FF">   &nbsp</font><a href="" id="task0">Edit</a><font color="#0000FF"></font></span></DIV> </td> </tr> <tr><td colspan="2" align="left" valign="top"><DIV id="div20" class="StackStyleVisible" width="100%"><br>   at Microsoft.VisualStudio.Design.Serialization.CodeDom.XML.CodeDomXmlProcessor.CreateQuoteExpression(XmlElementData xmlElement)<br>   at Microsoft.VisualStudio.Design.Serialization.CodeDom.XML.CodeDomXmlProcessor.XmlElementData.get_CodeDomElement()<br>   at Microsoft.VisualStudio.Design.Serialization.CodeDom.XML.CodeDomXmlProcessor.EndElement(String prefix, String name, String urn)<br>   at Microsoft.VisualStudio.Design.Serialization.CodeDom.XML.CodeDomXmlProcessor.Parse(XmlReader reader)<br>   at Microsoft.VisualStudio.Design.Serialization.CodeDom.XML.CodeDomXmlProcessor.ParseXml(String xmlStream, CodeStatementCollection statementCollection, String fileName, String methodName)<br>   at Microsoft.VisualStudio.Design.Serialization.CodeDom.VSCodeDomParser.OnMethodPopulateStatements(Object sender, EventArgs e)<br>   at System.CodeDom.CodeMemberMethod.get_Statements()<br>   at System.ComponentModel.Design.Serialization.TypeCodeDomSerializer.Deserialize(IDesignerSerializationManager manager, CodeTypeDeclaration declaration)<br>   at System.ComponentModel.Design.Serialization.CodeDomDesignerLoader.PerformLoad(IDesignerSerializationManager manager)<br>   at Microsoft.VisualStudio.Design.Serialization.CodeDom.VSCodeDomDesignerLoader.PerformLoad(IDesignerSerializationManager serializationManager)<br>   at Microsoft.VisualStudio.Design.Serialization.CodeDom.VSCodeDomDesignerLoader.DeferredLoadHandler.Microsoft.VisualStudio.TextManager.Interop.IVsTextBufferDataEvents.OnLoadCompleted(Int32 fReload)</DIV></td></tr></table></div></body></html>

frmUnhandledException.vb [Design]


<html><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=UTF-8"><title></title><style>.ErrorStyle { font-family: tahoma; font-size: 11 pt; text-align: left}.DetailsStyle { font-family: tahoma; font-size: 10pt; text-align: left;text-indent: 0; word-spacing: 0; line-height: 100%; float: left; margin-top: 0; margin-bottom: 0}.StackStyleVisible { font-family: tahoma; font-size: 10pt; text-align: left; margin-left: 20; text-indent: 0}.StackStyleHidden { display:none; font-family: tahoma; font-size: 10pt; text-align: left; margin-left: 20; text-indent: 0}</style></head><body><DIV class="DetailsStyle" width="100%"><table border="0" width="100%" id="table1" height="100%" cellspacing="0" cellpadding="0"><tr><td height="40" bgcolor="#FF9999" width="8%" style="letter-spacing: 0" align="center"><img border="0" src="C:\Users\Paddy\AppData\Local\Temp\620DAA7.tmp" width="35" height="35" alt="ErrorImage" ></td><td height="40" bgcolor="#FF9999" width="91%" style="vertical-align: top; letter-spacing: 0" align="left"><b><font size="2" face="Arial" fontsize="70%">One or more errors encountered while loading the designer. The errors are listed below. Some errors can be fixed by rebuilding your project, while others may require code changes.</font><font size="2" face="Arial"></font></b></td></tr><tr><td colspan="2" align="left" valign="top"><DIV id="div1" class="ErrorStyle" width="100%"><span style="font-weight: 600"><br>The designer cannot process the code at line 33: 

Me.pnlFormBackground.Dock = System.Windows.Forms.DockStyle.Fill


The code within the method ’InitializeComponent’ is generated by the designer and should not be manually modified.  Please remove any changes and try opening the designer again. </span><br><a href="" id="details0">Hide</a><font color="#0000FF">   &nbsp</font><a href="" id="task0">Edit</a><font color="#0000FF"></font></span></DIV> </td> </tr> <tr><td colspan="2" align="left" valign="top"><DIV id="div20" class="StackStyleVisible" width="100%"><br>   at Microsoft.VisualStudio.Design.Serialization.CodeDom.XML.CodeDomXmlProcessor.CreateQuoteExpression(XmlElementData xmlElement)<br>   at Microsoft.VisualStudio.Design.Serialization.CodeDom.XML.CodeDomXmlProcessor.XmlElementData.get_CodeDomElement()<br>   at Microsoft.VisualStudio.Design.Serialization.CodeDom.XML.CodeDomXmlProcessor.EndElement(String prefix, String name, String urn)<br>   at Microsoft.VisualStudio.Design.Serialization.CodeDom.XML.CodeDomXmlProcessor.Parse(XmlReader reader)<br>   at Microsoft.VisualStudio.Design.Serialization.CodeDom.XML.CodeDomXmlProcessor.ParseXml(String xmlStream, CodeStatementCollection statementCollection, String fileName, String methodName)<br>   at Microsoft.VisualStudio.Design.Serialization.CodeDom.VSCodeDomParser.OnMethodPopulateStatements(Object sender, EventArgs e)<br>   at System.CodeDom.CodeMemberMethod.get_Statements()<br>   at System.ComponentModel.Design.Serialization.TypeCodeDomSerializer.Deserialize(IDesignerSerializationManager manager, CodeTypeDeclaration declaration)<br>   at System.ComponentModel.Design.Serialization.CodeDomDesignerLoader.PerformLoad(IDesignerSerializationManager manager)<br>   at Microsoft.VisualStudio.Design.Serialization.CodeDom.VSCodeDomDesignerLoader.PerformLoad(IDesignerSerializationManager serializationManager)<br>   at Microsoft.VisualStudio.Design.Serialization.CodeDom.VSCodeDomDesignerLoader.DeferredLoadHandler.Microsoft.VisualStudio.TextManager.Interop.IVsTextBufferDataEvents.OnLoadCompleted(Int32 fReload)</DIV></td></tr></table></div></body></html>

frmMain.vb [Design]


<html><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=UTF-8"><title></title><style>.ErrorStyle { font-family: tahoma; font-size: 11 pt; text-align: left}.DetailsStyle { font-family: tahoma; font-size: 10pt; text-align: left;text-indent: 0; word-spacing: 0; line-height: 100%; float: left; margin-top: 0; margin-bottom: 0}.StackStyleVisible { font-family: tahoma; font-size: 10pt; text-align: left; margin-left: 20; text-indent: 0}.StackStyleHidden { display:none; font-family: tahoma; font-size: 10pt; text-align: left; margin-left: 20; text-indent: 0}</style></head><body><DIV class="DetailsStyle" width="100%"><table border="0" width="100%" id="table1" height="100%" cellspacing="0" cellpadding="0"><tr><td height="40" bgcolor="#FF9999" width="8%" style="letter-spacing: 0" align="center"><img border="0" src="C:\Users\Paddy\AppData\Local\Temp\533D142.tmp" width="35" height="35" alt="ErrorImage" ></td><td height="40" bgcolor="#FF9999" width="91%" style="vertical-align: top; letter-spacing: 0" align="left"><b><font size="2" face="Arial" fontsize="70%">One or more errors encountered while loading the designer. The errors are listed below. Some errors can be fixed by rebuilding your project, while others may require code changes.</font><font size="2" face="Arial"></font></b></td></tr><tr><td colspan="2" align="left" valign="top"><DIV id="div1" class="ErrorStyle" width="100%"><span style="font-weight: 600"><br>The designer cannot process the code at line 41: 

Me.ApplicationNavigation.AllowTabPagesSwitchingByMouseWheel = False


The code within the method ’InitializeComponent’ is generated by the designer and should not be manually modified.  Please remove any changes and try opening the designer again. </span><br><a href="" id="details0">Hide</a><font color="#0000FF">   &nbsp</font><a href="" id="task0">Edit</a><font color="#0000FF"></font></span></DIV> </td> </tr> <tr><td colspan="2" align="left" valign="top"><DIV id="div20" class="StackStyleVisible" width="100%"><br>   at Microsoft.VisualStudio.Design.Serialization.CodeDom.XML.CodeDomXmlProcessor.CreateQuoteExpression(XmlElementData xmlElement)<br>   at Microsoft.VisualStudio.Design.Serialization.CodeDom.XML.CodeDomXmlProcessor.XmlElementData.get_CodeDomElement()<br>   at Microsoft.VisualStudio.Design.Serialization.CodeDom.XML.CodeDomXmlProcessor.EndElement(String prefix, String name, String urn)<br>   at Microsoft.VisualStudio.Design.Serialization.CodeDom.XML.CodeDomXmlProcessor.Parse(XmlReader reader)<br>   at Microsoft.VisualStudio.Design.Serialization.CodeDom.XML.CodeDomXmlProcessor.ParseXml(String xmlStream, CodeStatementCollection statementCollection, String fileName, String methodName)<br>   at Microsoft.VisualStudio.Design.Serialization.CodeDom.VSCodeDomParser.OnMethodPopulateStatements(Object sender, EventArgs e)<br>   at System.CodeDom.CodeMemberMethod.get_Statements()<br>   at System.ComponentModel.Design.Serialization.TypeCodeDomSerializer.Deserialize(IDesignerSerializationManager manager, CodeTypeDeclaration declaration)<br>   at System.ComponentModel.Design.Serialization.CodeDomDesignerLoader.PerformLoad(IDesignerSerializationManager manager)<br>   at Microsoft.VisualStudio.Design.Serialization.CodeDom.VSCodeDomDesignerLoader.PerformLoad(IDesignerSerializationManager serializationManager)<br>   at Microsoft.VisualStudio.Design.Serialization.CodeDom.VSCodeDomDesignerLoader.DeferredLoadHandler.Microsoft.VisualStudio.TextManager.Interop.IVsTextBufferDataEvents.OnLoadCompleted(Int32 fReload)</DIV></td></tr></table></div></body></html>



What do you suggest I do to combat this ongoing problem??  Thanks in advance!
Paddy Jul 29, 2010 - 1:50 PM

I just noticed that in v3.6, the DLL files for Elegant.Ui.Common.dll and Elegant.Ui.Ribbon.dll were located in C:\Program Files\FOSS Software Inc\Elegant Ribbon\bin\ but when

the new version v3.7 came out, the location of these DLL files were changed from C:\Program Files\FOSS Software Inc\Elegant Ribbon\bin\ to

C:\Program Files\FOSS Software Inc\Elegant Ribbon\bin\Core\.  This would explain the reason for the version being 0.0.0.0 and could be the reason why I was getting those

Designer issues.



In regard to screen shots.  I need to get the application to go back to what it looked like when I was using v3.6.  Screen shots for both are attached.  How do I get that look back?


v3.6 in the IDE and when Launched (want):

Launched: http://dl.dropbox.com/u/5335929/SupportSpace/v3.6%20-%20frmMainTitleBar%20-%20Launched.png#@lt;br />
IDE: http://dl.dropbox.com/u/5335929/SupportSpace/v3.6%20-%20frmMainTitleBar.png#@lt;strong>



v3.7 in the IDE and when launched (don’t want):

Launched: http://dl.dropbox.com/u/5335929/SupportSpace/v3.7%20-%20frmMainTitleBar%20-%20Launched.png#@lt;br />
IDE: http://dl.dropbox.com/u/5335929/SupportSpace/v3.7%20-%20frmMainTitleBar.png#@lt;br />


The area I am referring to is shown with the black border.
Technical Support Jul 30, 2010 - 7:03 AM

Thank you for the reply. We are happy that your project works with Elegant Ui version 3.7. Actually you shouldn’t have to delete the old references because when the new version
is installed all you need is to rebuild the solution. Thought the assemblies location has changed, they are always stored in the GAC, so the compiler would find them anyway.

As for changing the application look, it is because the default theme is now different that that used for previous version. This is necessary to get the ribbon look more consistent with
new Backstage View component. You can easily get back to the Office2007Blue theme by dropping the new component ThemeSelector from the toolbox onto the form and selecting
it from the list. If you still have any questions just contact us.
Paddy Jul 30, 2010 - 5:10 PM

"You can easily get back to the Office2007Blue theme by dropping the new component ThemeSelector from the toolbox onto the form and selecting

it from the list."



Thanks, that did it for me.  Now I am going to have to figure out how the end user can select the theme from a drop down menu to be able to change it to their liking. I believe you have a demo app for that.
Paddy Jul 29, 2010 - 1:17 PM

1) Did you tried to build the project before opening the designer?

I tried to upgrade with both VB.NET 2005 open and closed, same situation as explained in my previous post.

I did not build the application before or after the upgrade.  I’ll go try that now....



2) Did you specified any explicit Elegant Ribbon version in the project reference?

If I go into the project reference (prior to the upgrade), I do see the reference for v3.6 for Elegant.Ui.Common and Elegant.Ui.Ribbon but I didn’t specify it myself.   As soon as you drop the control on the form, it’s automatically referenced.



I closed out VB.NET 2005 Pro and then ran the installer for v3.7.  Once this was completed, I launched the project and I go the same issues as outlined in my previous post.  I then went into the project reference and found that the version for Elegant.Ui.Common and Elegant.Ui.Ribbon is 0.0.0.0.



I then clicked on ’Reference Paths’ button > ... > and navigated to C:\Program Files\FOSS Software Inc\Elegant Ribbon\bin\ and the two DLL files didn’t show up.

I then went into Start > Run > C:\Program Files\FOSS Software Inc\Elegant Ribbon\bin\ and only see Elegant.Ui.ToolboxControlsInstaller.dll and three other folders.

I then went into C:\Program Files\FOSS Software Inc\Elegant Ribbon\bin\Core\ and found the two DLL files that should have been referenced (Elegant.Ui.Common.dll and Elegant.Ui.Ribbon.dll)



If I click on the ’Unused References’ button, I am told:

"Project compilation failed.  Cannot determine unused references."



I then deleted the two references to Elegant.Ui.Common and Elegant.Ui.Ribbon in the project references area due to the version being 0.0.0.0 and then tried to rebuild the solution.  Everything for your controls is now ’Not Defined’ or ’Not Declared’.  Expected because of no reference to Elegant.Ui.Common and Elegant.Ui.Ribbon



I then tried to readd the references to Elegant.Ui.Common.dll and Elegant.Ui.Ribbon.dll within C:\Program Files\FOSS Software Inc\Elegant Ribbon\bin\Core\ and I was able to.  The version now being 3.7.0.0.

I then saved everything and rebuilt the solution with success.


I am now able to open the forms in the Solutions Explorer without issue and when trying to F5 the application, the application runs but the title bar of the MDI form doesn’t look the same as it did in v3.6.  frmMain.vb is completely different also.
Technical Support Jul 29, 2010 - 8:49 AM


Unfortunately the stack trace does not contain enough information that could help us to find the source the problem.
We have no similar issue reports.
We tried to migrate quite big VB .NET application from 3.6 to 3.7 version and everything worked fine.
We need to know the following:
1) Did you tried to build the project before opening the designer?
2) Did you specified any explicit Elegant Ribbon version in the project reference?
3) Could you provide us with some simplest possible test project reproducing this problem?