tag:blogger.com,1999:blog-1688176320920284646.post5309074160035321436..comments2023-12-20T10:24:23.540+00:00Comments on A day in the life of...: The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)Unknownnoreply@blogger.comBlogger2125tag:blogger.com,1999:blog-1688176320920284646.post-34441098491533545812007-08-16T08:49:00.000+01:002007-08-16T08:49:00.000+01:00It's ECO IV, the one currently under development.It's ECO IV, the one currently under development.Peter Leslie Morrishttps://www.blogger.com/profile/09377536995235480828noreply@blogger.comtag:blogger.com,1999:blog-1688176320920284646.post-7389834299518049062007-08-16T01:13:00.000+01:002007-08-16T01:13:00.000+01:00Hi Peter, which is the newer version of ECO are yo...Hi Peter, which is the newer version of ECO are you using?<BR/><BR/>it is available to test?<BR/><BR/>Peter, I am using C# Builder 2006 and I am waiting for a release ECO for Visual Studio, while I have to lost time with the bug in C# Builder ect, I was thinking, if my model is a dll, and I am using the eco services to get and update data (I don't using expressionHandle, oclPShandle, not using binding), so will be very hard to migrate to visual studio 2005 the project?<BR/><BR/>any advice is welcome.<BR/><BR/>kind regards<BR/>FrankUnknownhttps://www.blogger.com/profile/14914927386821533932noreply@blogger.com