Visual studio 2019 with devart bug/issue

Discussion of open issues, suggestions and bugs regarding Entity Developer - ORM modeling and code generation tool
Post Reply
figueiredorj
Posts: 41
Joined: Fri 12 Apr 2013 19:05

Visual studio 2019 with devart bug/issue

Post by figueiredorj » Sun 07 Apr 2019 11:01

don't know if it is just me - when starting a new project with dbcontext I am unable to save.

sample table

Code: Select all

USE [l4master]
GO

/****** Object:  Table [dbo].[T_USER]    Script Date: 07/04/2019 12:00:54 ******/
SET ANSI_NULLS ON
GO

SET QUOTED_IDENTIFIER ON
GO

CREATE TABLE [dbo].[T_USER](
	[ID] [uniqueidentifier] NOT NULL,
	[USERNAME] [nvarchar](50) NOT NULL,
	[PASSWORD] [nvarchar](250) NOT NULL,
	[LAST_LOGIN] [datetime] NULL,
 CONSTRAINT [PK_T_USER] PRIMARY KEY CLUSTERED 
(
	[ID] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
) ON [PRIMARY]
GO

ALTER TABLE [dbo].[T_USER] ADD  CONSTRAINT [DF_T_USER_ID]  DEFAULT (newid()) FOR [ID]
GO



Severity Code Description Project File Line Suppression State
Error Custom tool error: Object of type 'System.Int32' cannot be converted to type 'System.UInt32'. C:\DEV\l4\master\source\l4.master.App\l4.master.data.design\DataModel.edml 1


Any ideas?

Shalex
Site Admin
Posts: 8661
Joined: Thu 14 Aug 2008 12:44

Re: Visual studio 2019 with devart bug/issue

Post by Shalex » Thu 11 Apr 2019 19:19

Entity Framework supports only primitive types: https://docs.microsoft.com/en-us/dotnet ... data-types.

You should not use unsigned System.UInt32 as a property type.

Post Reply