New Posts New Posts RSS Feed: ShellLayoutView
  FAQ FAQ  Forum Search   Calendar   Register Register  Login Login

ShellLayoutView
 Post Reply Post Reply Page  <123>
Author
  Share Topic Share Topic  Topic Search Topic Search  Topic Options Topic Options
Bill Jensen View Drop Down
IdeaBlade
IdeaBlade
Avatar

Joined: 31-Jul-2007
Location: United States
Posts: 229 		Post Options Post Options   Quote Bill Jensen Quote  Post ReplyReply Direct Link To This Post Topic: ShellLayoutView
    Posted: 05-Sep-2007 at 12:51pm
I believe DevForce 3.5.3.1 is built with DevEx 7.2.1, not 7.1.  I suggest adjusting machine.config to map versions between 7.1.0 and 7.2.2 to 7.2.2.
 
Bill J.
Back to Top
orcities View Drop Down
Senior Member
Senior Member
Avatar

Joined: 28-Aug-2007
Location: United States
Posts: 454 		Post Options Post Options   Quote orcities Quote  Post ReplyReply Direct Link To This Post Posted: 05-Sep-2007 at 1:09pm
Got it to compile. I didn't add the second map. But I still can't open the any LayoutViews. I get the same error as before.
Back to Top
Linguinut View Drop Down
Senior Member
Senior Member
Avatar

Joined: 14-Jun-2007
Location: United States
Posts: 394 		Post Options Post Options   Quote Linguinut Quote  Post ReplyReply Direct Link To This Post Posted: 05-Sep-2007 at 1:50pm
The binding redirects exists properly for the controls:
 
<bindingRedirect oldVersion="7.2.1.0" newVersion="7.2.3.0" />
 
I am getting a couple of errors in the Infrastructure.Foundation project when building.  The XtraGridBindingDescriptor is not referenced.
 
Error 1 The type 'IdeaBlade.UI.WinForms.DevExpressControls.XtraGridBindingDescriptor' is defined in an assembly that is not referenced. You must add a reference to assembly 'IdeaBlade.UI.WinForms.DevExpressControls.v7_2_1, Version=3.5.3.1, Culture=neutral, PublicKeyToken=287b5094865421c0'. C:\Documents and Settings\bill\My Documents\Visual Studio 2005\Projects\CabanaDevExCS\Source\Infrastructure.Foundation\GridBuilders\OrderDetailGridBuilder.cs 33 7 Infrastructure.Foundation
Not sure where to go to resolve that one.
Back to Top
orcities View Drop Down
Senior Member
Senior Member
Avatar

Joined: 28-Aug-2007
Location: United States
Posts: 454 		Post Options Post Options   Quote orcities Quote  Post ReplyReply Direct Link To This Post Posted: 05-Sep-2007 at 1:55pm

<dependentAssembly>

<assemblyIdentity name="DevExpress.Data.v7.1" publicKeyToken="79868b8147b5eae4" />

<bindingRedirect oldVersion="7.1.0.0" newVersion="7.2.2.0" />

<bindingRedirect oldVersion="7.2.1.0" newVersion="7.2.2.0" />

</dependentAssembly>

<dependentAssembly>

<assemblyIdentity name="DevExpress.Utils.v7.1" publicKeyToken="79868b8147b5eae4" />

<bindingRedirect oldVersion="7.1.0.0" newVersion="7.2.2.0" />

<bindingRedirect oldVersion="7.2.1.0" newVersion="7.2.2.0" />

</dependentAssembly>

<dependentAssembly>

<assemblyIdentity name="DevExpress.XtraEditors.v7.1" publicKeyToken="79868b8147b5eae4" />

<bindingRedirect oldVersion="7.1.0.0" newVersion="7.2.2.0" />

<bindingRedirect oldVersion="7.2.1" newVersion="7.2.2" />

</dependentAssembly>

<dependentAssembly>

<assemblyIdentity name="DevExpress.XtraGrid.v7.1" publicKeyToken="79868b8147b5eae4" />

<bindingRedirect oldVersion="7.1.0.0" newVersion="7.2.2.0" />

<bindingRedirect oldVersion="7.2.1.0" newVersion="7.2.2.0" />

</dependentAssembly>
Back to Top
Linguinut View Drop Down
Senior Member
Senior Member
Avatar

Joined: 14-Jun-2007
Location: United States
Posts: 394 		Post Options Post Options   Quote Linguinut Quote  Post ReplyReply Direct Link To This Post Posted: 05-Sep-2007 at 2:30pm
I removed the "v7_1_0" assembly from Infrastructure.Foundation and added the "v7_2_1" assembly available from IdeaBlade.  After rebuilding, I found the same assembly that needed replacing in the Cabana.UI.Admin project.  I rebuilt all again and everything succeeded.  I have a running Cabana on 3.5.3.1 and DevExpress 7.2.3.
Back to Top
Bill Jensen View Drop Down
IdeaBlade
IdeaBlade
Avatar

Joined: 31-Jul-2007
Location: United States
Posts: 229 		Post Options Post Options   Quote Bill Jensen Quote  Post ReplyReply Direct Link To This Post Posted: 06-Sep-2007 at 9:22am
A few thoughts on assembly binding redirection:
 
1.  You have correctly identified the four Developer Express assemblies that require redirection: Data, Utils, XtraEditors and XtraGrid.
 
2.  Rather than redirecting a specific version of an assembly, we often specify a range of version values in the form:
 
<bindingRedirect oldVersion="0.0.0.0-7.1.3.0" newVersion="7.1.3.0" />

3.  Developer Express, in its wisdom, includes the major.minor version numbers in their assembly NAME.  Now that we are on version 7.2.x of DevEx, redirections are required for assembly names ending in ".v.7.2".  For example:

<dependentAssembly>

<assemblyIdentity name="DevExpress.Data.v7.2" publicKeyToken="9b171c9fd64da1d1" />

<bindingRedirect oldVersion="0.0.0.0-7.2.3.0" newVersion="7.2.3.0" />

</dependentAssembly>

4.  Redirects work best in machine.config since they provide a single point to change when upgrading to a new version.

Hope this is helpful.

Bill J.
Back to Top
orcities View Drop Down
Senior Member
Senior Member
Avatar

Joined: 28-Aug-2007
Location: United States
Posts: 454 		Post Options Post Options   Quote orcities Quote  Post ReplyReply Direct Link To This Post Posted: 06-Sep-2007 at 9:34am
Thank you. I have made those changes and now know to make those changes in the future.
 
But, I am still getting that error (Below). Is this due to using the trial version?
 
The path is not of a legal form.
Hide    

at System.IO.Path.NormalizePathFast(String path, Boolean fullCheck)
at System.IO.Path.GetFullPathInternal(String path)
at System.Reflection.AssemblyName.GetAssemblyName(String assemblyFile)
at Microsoft.VisualStudio.Design.VSTypeResolutionService.AddProjectDependencies(Project project)
at Microsoft.VisualStudio.Design.VSTypeResolutionService.AssemblyEntry.get_Assembly()
at Microsoft.VisualStudio.Design.VSTypeResolutionService.AssemblyEntry.Search(String fullName, String typeName, Boolean ignoreTypeCase, Assembly& assembly, String description)
at Microsoft.VisualStudio.Design.VSTypeResolutionService.SearchProjectEntries(AssemblyName assemblyName, String typeName, Boolean ignoreTypeCase, Assembly& assembly)
at Microsoft.VisualStudio.Design.VSTypeResolutionService.SearchEntries(AssemblyName assemblyName, String typeName, Boolean ignoreCase, Assembly& assembly, ReferenceType refType)
at Microsoft.VisualStudio.Design.VSTypeResolutionService.SearchEntries(AssemblyName assemblyName, String typeName, Boolean ignoreTypeCase, Assembly& assembly)
at Microsoft.VisualStudio.Design.VSTypeResolutionService.System.ComponentModel.Design.ITypeResolutionService.GetAssembly(AssemblyName name, Boolean throwOnError)
at Microsoft.VisualStudio.Design.VSTypeResolutionService.System.ComponentModel.Design.ITypeResolutionService.GetAssembly(AssemblyName name)
at Microsoft.VisualStudio.Design.VSDynamicTypeService.OnAssemblyResolve(Object sender, ResolveEventArgs e)
at System.AppDomain.OnAssemblyResolveEvent(String assemblyFullName)
Back to Top
davidklitzke View Drop Down
IdeaBlade
IdeaBlade
Avatar

Joined: 14-Jun-2007
Posts: 715 		Post Options Post Options   Quote davidklitzke Quote  Post ReplyReply Direct Link To This Post Posted: 06-Sep-2007 at 11:33am
Here are my own recommendations on Assembly Binding Redirections based on my experience with customers who have had problems in this area:
 
(1) When you install DevForce initially, the Assembly Binding Redirector is automatically invoked, and you shouldn't have to do anything after the DevForce Install.
 
(2) If you install a new version of Infragistics or DevExpress later, you need to rerun the Assembly Binding Redirector.
 
(3) Use the Assembly Binding Redirector Tool in preference to manually editing the config tool
 
(4) Assembly binding redirection only works across minor releases (e.g., 7.2.1 to 7.2.3).  It won't redirect version information from a minor release of a major release to minor release of a different major version (e.g., 7.1.6 to 7.2.3)
Back to Top
Linguinut View Drop Down
Senior Member
Senior Member
Avatar

Joined: 14-Jun-2007
Location: United States
Posts: 394 		Post Options Post Options   Quote Linguinut Quote  Post ReplyReply Direct Link To This Post Posted: 06-Sep-2007 at 12:28pm
Interesting feedback on Microsoft.com:
 
 
Also, there are cmd utilities that you could try running to cleanup some of the assemblies in Cabana.  See the root of the project folder and run flushCabana.cmd and/or fullflushCabana.cmd.  Rebuilds would be in order after that.
 
Sorry to hear that you are still experiencing that error.
Back to Top
Bill Jensen View Drop Down
IdeaBlade
IdeaBlade
Avatar

Joined: 31-Jul-2007
Location: United States
Posts: 229 		Post Options Post Options   Quote Bill Jensen Quote  Post ReplyReply Direct Link To This Post Posted: 06-Sep-2007 at 2:19pm
Thanks for the link, Bill.  Very interesting.
 
Dan, you're welcome to try the flush commands to blow away your \bin and \obj folders, then rebuild your solutions, but from the MSDN feedback, it sounds like you have a broken reference somewhere.  I trust you've checked for missing references.
 
Bill J.
Back to Top
orcities View Drop Down
Senior Member
Senior Member
Avatar

Joined: 28-Aug-2007
Location: United States
Posts: 454 		Post Options Post Options   Quote orcities Quote  Post ReplyReply Direct Link To This Post Posted: 06-Sep-2007 at 2:21pm

David thank you for the help.

 I have now purchased DevExpress and installed the Pro version of 7.2.3. I have used the binding redirect tool. But, I get he following error when I try to build Cab.DevEx.

 
Error 7 Cannot implicitly convert type 'DevExpress.XtraGrid.Views.Grid.GridView []' to 'DevExpress.XtraGrid.Views.Grid.GridView [c:\Program Files\Developer Express .NET v7.2\Sources\DevExpress.DLL\DevExpress.XtraGrid.v7.2.dll]' C:\Development\CabanaDevExCS\Source\Infrastructure.IdeaBlade\IdeaBlade.Cab.DevEx\Views\Base\DevExDetailGridViewBuilder.cs 71 27 IdeaBlade.Cab.DevEx
 
It only occurs for Grid Items. I have verified the right assembly but I still get it.
 
Any clue on how to get by this. I have else checked intellisence and it has those classes.

 
Back to Top
orcities View Drop Down
Senior Member
Senior Member
Avatar

Joined: 28-Aug-2007
Location: United States
Posts: 454 		Post Options Post Options   Quote orcities Quote  Post ReplyReply Direct Link To This Post Posted: 06-Sep-2007 at 2:22pm
I have verified references and replaced references.
Back to Top
Linguinut View Drop Down
Senior Member
Senior Member
Avatar

Joined: 14-Jun-2007
Location: United States
Posts: 394 		Post Options Post Options   Quote Linguinut Quote  Post ReplyReply Direct Link To This Post Posted: 06-Sep-2007 at 2:25pm
First, run ReBuild on your LIB solution.  That will replace the assemblies that you just verified references on.  There are a few sneaky references out there, though.  I checked every project and I still missed one or two.  You may have to go through them, again. 
Back to Top
orcities View Drop Down
Senior Member
Senior Member
Avatar

Joined: 28-Aug-2007
Location: United States
Posts: 454 		Post Options Post Options   Quote orcities Quote  Post ReplyReply Direct Link To This Post Posted: 06-Sep-2007 at 2:44pm
I have run the flush, rebuilt the project, checked for bad or missing references. I can not seem to find any.
 
I get it to compile and run but can't see the the designer.
Back to Top
orcities View Drop Down
Senior Member
Senior Member
Avatar

Joined: 28-Aug-2007
Location: United States
Posts: 454 		Post Options Post Options   Quote orcities Quote  Post ReplyReply Direct Link To This Post Posted: 06-Sep-2007 at 2:58pm
The strange thing is that when I am using the DevEx version I can't even open the DotNet designer files.
 
But I can when I use the DotNet Lib version.
Back to Top
Bill Jensen View Drop Down
IdeaBlade
IdeaBlade
Avatar

Joined: 31-Jul-2007
Location: United States
Posts: 229 		Post Options Post Options   Quote Bill Jensen Quote  Post ReplyReply Direct Link To This Post Posted: 06-Sep-2007 at 3:14pm

Perhaps there's a problem with your Visual Studio toolbox.

Select Tools->Choose Toolbox Items...
 
This is a frustrating dialog - it's fixed size so you have to adjust column widths to see the whole field.
 
Click on the header of the AssemblyName column to make all the Developer Express assemblies sort together.  Then check them to be sure they're all of the proper name (i.e., ending in v7.2), version (7.2.3.0), and source (the GAC).
 
Sorry it's being such a problem for you.
 
Bill J.
Back to Top
 Post Reply Post Reply Page  <123>

Forum Jump Forum Permissions View Drop Down