Devart Forums

Hi, Since only one version of devart can be installed at any given time, does that mean that if I want to roll out a new version of Devart that I have to update the references and redeploy all asp.net apps at the same time? In other words, if devart is currently at version 1, for example, and all my apps are referencing version 1 and then version 2 comes out. Do I have to update references in my app to v2 and redeploy everything? Or, as I hope, can I just deploy v2 of devart on the server and the existing apps will start using it without problem?
Thanks ... Ed

Hi,

I am using version 7.4.146

I am setting up a new MVC4 application using devart to connect to oracle. I have a single context and model. I have been able to instantiate a db context and query the db. So I know I have my connection info right. However, when I try to create a controller for my one and only model, I get:

Unable to retrieve metadata for 'my db'. Using the same DbCompiledModel to create contexts against different types of database servers is not supported. Instead, use a separate DbCompiledModel for each type of server being used.

I have no idea what this means or what I can do about it.
Please help.
Thanks ... Ed

Thanks for the info. I'll get started right away!
Ed

Hi,
I am a contractor working at a very large multinational. We have been using DevArt for some time now. However, we find that when a new version of dotConnect comes out, it is very difficult for us to roll it out. It seems that only 1 version of the softare can be installed at a time. This means that have to go into each of my 25+ applications reset references, recompile, retest and redeploy every time a new drop of devart comes out that we want. Please tell me there is a better way!
Thanks ... Ed

Hi,
Does dotConnect support this as well as code-first migrations?
If so, where can I read up on it?
If not, is it coming?
Thanks ... Ed

Hi,
I sent a message earlier with the following example query in vb.net:

Dim qry = from a in db.YourTable where a.IntegerField = CInt (“1”) select a.

This errors out when executed with the following error:
“No coercion operator is defined between types ‘System.String’ and ‘System.Int32’. “

I then tried it with int32.Parse(“1”) instead of the CInt and it works correctly.

Either way, it’s a bug as in prior versions of LinqConnect I could use the following query and it would work.

Dim qry = from a in db.YourTable where a.IntegerField = “1” select a.

This is really a big problem. I have 20+ applications and 1000’s of lines of code I would have to review and change just to do this silly cast.
Now, I realize that this is not an issue in C#, but obviously it is in vb. This should be a fairly straightforward fix on your side. Whereas it is a monstrous change on mine.
I have been unable to upgrade since version 6.8 because of one problem after the next. Please, please, get this right.
Thanks … Ed

Cool! I can't wait to get my hands on it!
Thanks ... Ed

Any news?
Thanks ... Ed

That works, but is not a tasty work-around. I have 25 applications and who knows how many similar calls spread out all over the place.
Any idea of a timeframe for when this will be fixed? I have been waiting for several months to upgrade from 6.8 because every time I try, I run into another problem/bug.
Thanks ... Ed

More info,
I did as you suggested as a test and got the followign error:
What's up with the embedded \r\n's?
Thanks ... Ed

System.InvalidCastException: Specified cast is not valid.\r\n at
Devart.Data.Linq.Engine.SingleKeyManager`2.a(Object[] A_0)\r\n at
Devart.Data.Linq.Engine.KeyManager`2.b(Object[] A_0)\r\n at
Devart.Data.Linq.Engine.ah.a(Expression A_0, Object& A_1)\r\n at
Devart.Data.Linq.Engine.ah.e(Expression A_0)\r\n at
Devart.Data.Linq.DataProvider.a(Expression A_0)\r\n at
Devart.Data.Linq.Engine.DataQuery`1.System.Linq.IQueryProvider.Execute
[S](Expression expression)\r\n at System.Linq.Queryable.FirstOrDefault
[TSource](IQueryable`1 source)\r\n at StewDB.EXEMPTION.GetByPrimaryKey
(StewDBDataContext db, Int32 lExemptionSeq) in c:\\Code\\Dev\\Exemption
\\App_Code\\StewDBPartials.cs:line 102\r\n at
ExemptionManager.cmdSearch_Click(Object sender, EventArgs e) in c:\\Code \\Dev\\Exemption\\ExemptionManager.aspx.cs:line 169

I don't think we are working with int16's at all. The definition of the pk in our db is:

EXEMPTION_SEQ NUMBER(*,0) NOT NULL ENABLE

The definition in the lqml (the default after the table was dropped on the lqml), is as follows:
Property
Type = System.Decimal
Server Data Type = NUMBER NOT NULL
Auto Generated Value = True

No int16 anywhere to be found.

Here is some more info.
If, instead of:
return qry.FirstOrDefault();
I do the following, it works. Something's not right.
Thanks ... Ed

Hi,
I have a VERY simple query that is failing after I upgraded from 6.80.350.0 to 7.2.114.0.
All I am doing is a simplet select on a primary key:
var qry = from a in db.EXEMPTIONs
where a.EXEMPTION_SEQ == lExemptionSeq
select a;
return qry.FirstOrDefault();

When I execute the return statement, I get the following error: Now what's really odd about this is that if I do a db.GetCommand(qry) to see what the sql being generated is, I get the following:

db.GetCommand(qry).CommandText
"SELECT t1.EXEMPTION_SEQ, t1.EXEMPTION_DATE, t1.STATUS_SEQ, t1.RISK_SEQ, t1.START_DATE, t1.END_DATE, t1.DATE_APPROVED, t1.DATE_CLOSED, t1.CROP_SEQ, t1.REGION_SEQ, t1.LOCATION_SEQ, t1.REQUESTOR_LDAP, t1.SOP_DOC_NUMBER, t1.SECTIONS_AFFECTED, t1.CHANGE_SOP, t1.REQUEST, t1.REASON, t1.RISK_ASSESSMENT, t1.CONDITIONS, t1.EXEMPTION_NUMBER, t1.HISTORIC_EXEMPTION_NUMBER, t1.IS_REVIEWED\r\nFROM STEWARDSHIP.EXEMPTION t1\r\nWHERE t1.EXEMPTION_SEQ = 123"

Note the embedded \r\n's at the end? Where did those come from? I'm pretty sure that's what is causeing the problem and I'm also sure that my code has not changed from devart versoin 6.8 to 7.2. It's gotta be some change you folks made. Please help.
Thanks ... Ed

I got the stuff you sent and will take a look at it. As an aside, it appears that the issue is with some procs and not others. I can't seem to nail down what the difference is. However, I am certain this is a bug because when I do this with the 6.8 version it works fine. It's only with the new 7.1+ versions that I have the problem. I will see if I can create a reproduceable case and send it to you.
Thanks ... Ed

I just downloaded 7.1.58 in great hopes of it *finally* fixing a number of bugs only to find completely new ones that make it unusable.
I open an existing lqml that works in version 6.8, I delete a stored proc and then delete the associated complex type. I then try to re-drop the same stored proc onto the designer. It correctly adds the proc to the list of methods in the model explorer, BUT no complex type was created in either the design diagram or the model explorer. Once again I am stuck waiting for a fix. This has been going on for months. I like the product but am beginning to lose faith. Please get this right and let me know when you have a fix complete.
Thanks ... Ed