Comments on: VB Dynamic Query Library woes

By: deedee

deedee — Mon, 09 Aug 2010 22:51:03 +0000

Hi Josh, I am getting the same error as you — "Type 'System.Data.Linq.Mapping.DatabaseAttribute' is not defined" I have been working on this for 2 days, if you find a solution or already have please post or send me an email. I am extremly fustrated and running out of time to complete my project. I would really appreciate any help. Thanks

By: Josh

Josh — Mon, 09 Aug 2010 22:51:03 +0000

Another great big THANK YOU! I also had a problem with an error displaying the "Signature" class was not defined after the namespace removal, so I had to remove the mention of the namespace in the "Equals" function Public Overloads Function Equals(ByVal other As Signature) As Boolean Implements IEquatable(Of Signature).Equals

By: Dave

Dave — Mon, 09 Aug 2010 22:51:03 +0000

This has been a bear of an app to write. I just finished another site doing almost the same things but this one just is acting weird. I am getting the: Type 'System.Data.Linq.Mapping.DatabaseAttribute' is not defined I have never had this error b4. Very curious. Anyway what part of the DBML generated code did you remove? Here's mine: Option Strict On Option Explicit On Imports System Imports System.Collections.Generic Imports System.ComponentModel Imports System.Data Imports System.Data.Linq Imports System.Data.Linq.Mapping Imports System.Linq Imports System.Linq.Expressions Imports System.Reflection _ Partial Public Class Troop533EventsDataContext Inherits System.Data.Linq.DataContext Private Shared mappingSource As System.Data.Linq.Mapping.MappingSource = New AttributeMappingSource Any help would be appreciated. Contact me at this email address if you wouldn't mind helping. Thanks in advance. youngboy1606 AT ya hoo.com

By: Steve Hobbs

Steve Hobbs — Mon, 09 Aug 2010 22:51:03 +0000

Hmm to be honest it sounds like you might have a different problem to what is described here. For a start, I didn't modify anything in my generated .dbml file. If you've got the Dynamic Query library included in your project like I have, then you may have the same problem with conflicting namespaces in Vb.Net; otherwise, I'm not sure what it could be.

By: dested

dested — Mon, 09 Aug 2010 22:49:24 +0000

THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU Really. Thank you.

By: Steve Hobbs

Steve Hobbs — Mon, 09 Aug 2010 22:49:24 +0000

Just a quirk to be aware of when working with VB.Net class libraries really. You might be able to remove the default namespace in the properties for the project, which would also solve this problem. Depends on your particular scenario really.

By: noobian

noobian — Mon, 09 Aug 2010 22:47:57 +0000

Thanks, big help. So, is this a built in feature, a quirk, or a bug?