Devart Forums

About a minute ago i reported a bug in linq connect version 3.0.4.0 using support ticket. This bug is absolutely critical and prevents me from using this version. I would like to known when you are going to fix it.

Regards
Piotr Wójcicki

EDITED:

Just downloaded version 3.0.5 - the this particlar bug seems to be fixed, but immediatle i encountered several more. This version is also unsuable and should not be released. I am downgrading to 2.20. This is very dissapointing as i really liked new template features. Is it possible to use new entity developer with version 2.20 of linq connect ?

You should be able to use the runtime LinqConnect assemblies when the new version is installed. To do so, copy the old versions of the Devart.Data.Linq and Devart.Data.SqlServer.Linq assemblies (provided that you are working with MS SQL Server) to the Bin folder of your application and set the references to them. You should also remove the policy.*.Devart.* files from the GAC so that the old assemblies are not replaced by the new ones.

Also, could you please describe the problems you are encountering with LinqConnect 3.0.5?

For example version 3.0.5 generated such sql :

declare @p13 bigint
set @p13=NULL
exec sp_executesql N'INSERT INTO [dbo].[ad_adds] ([ItemId], [AdId], [Date], [KeywordId], [BidId], [Price],
[CampaignId], [BidAmount], [DiscountApplied], [Deleted]) VALUES (@p1, @p2, @p3, @p4, @p5, @p6, @p7, @p8, @p9, @p10) ;
SELECT @@ret1 = [AdAddId] FROM [dbo].[ad_adds] WHERE [AdAddId] = SCOPE_IDENTITY()',N'@p1 bigint,@p2 bigint,@p3 datetime,
@p4 bigint,@p5 bigint,@p6 float,@p7 bigint,@p8 float,@p9 float,@p10 bit,@ret1 bigint output',
@p1=2437672,@p2=92,@p3='2011-09-30 16:41:42.477',@p4=170,@p5=116,@p6=0.14999999999999999,@p7=64,@p8=0.14999999999999999,
@p9=0,@p10=0,@ret1=@p13 output
select @p13

Which is invalid and generated error on execution:

Msg 137, Level 15, State 1, Line 4
Must declare the scalar variable "@@ret1".

Version 2.20 generates correct insert statement for identical c# code.

Regards
Piotr Wójcicki

Thank you for your report, we have reproduced the problem. We will analyze it and inform you as soon as it is fixed.

We have fixed this issue, the fix will be available in the nearest build, which we plan to release in about a week.

The fix is available in the latest 3.0.14 build of LinqConnect. The new build can be downloaded from
http://www.devart.com/linqconnect/download.html
(the trial and free versions) or from Registered Users' Area (for users with active subscription only).

For the detailed information about the fixes and improvements available in LinqConnect 3.0.14, please refer to
http://www.devart.com/forums/viewtopic.php?t=22548