Comments on Matt on ... Whatever: LINQ to SQL enum mapping

global:: helped me too - VS2010 RC with Framework ...

2010-03-02T08:54:49.616-08:00

global:: helped me too - VS2010 RC with Framework 4...

Thanks for this!

Your post is still helping - it was the fix to my ...

2010-01-21T15:09:26.484-08:00

Your post is still helping - it was the fix to my error as well. Thanks!

My project was building fine but suddenly that DBM...

2009-10-19T08:06:16.708-07:00

My project was building fine but suddenly that DBML1005 error appeared after making an unrelated change to the dbml file. Prepending the global:: namespace fixed the issue.

Thanks!!!

Awesome. You saved me!!

2009-08-10T21:10:27.880-07:00

Awesome. You saved me!!

Your nearly-two-year-old post has just saved my da...

2009-06-03T14:40:29.735-07:00

Your nearly-two-year-old post has just saved my day: it appears that still today, in June 2009, we have same problem in Visual Studio 2008 SP1! Thanks for the workaround!

Thanks a lot for the fix mate. Wonder how you came...

2008-09-07T09:51:00.000-07:00

Thanks a lot for the fix mate. Wonder how you came up with "global::" prefix :)

Thanks Matt for the fix, for me I haven't set a na...

2008-08-06T19:47:00.000-07:00

Thanks Matt for the fix, for me I haven't set a namespace for the DataContext/Entity types so it should be the same as my enum types. However, although it works most of the time intermittently I get this error and find I have to either restart visual studio or delete the linq class file and recreate. But your workaround solved the issue for me.

This bug still exists in the release version of VS...

2008-08-04T13:02:00.000-07:00

This bug still exists in the release version of VS 2008. Thanks for posting a fix!

Broken keyboard on this bug. Thank you.

2008-04-04T06:31:00.000-07:00

Broken keyboard on this bug. Thank you.

You missed the point- setting the non-namespace-qu...

2008-03-21T09:27:00.000-07:00

You missed the point- setting the non-namespace-qualified type name works fine if the enum is in the same namespace as the DataContext/Entity types. It breaks when the enum is in a different namespace.

Works for me, if I just set the enum's type name, ...

2008-03-21T01:43:00.000-07:00

Works for me, if I just set the enum's type name, instead of the FullName.

I did (https://connect.microsoft.com/VisualStudio/...

2008-03-17T03:59:00.000-07:00

I did (https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=289435), but after fighting with the Connect moderator for a couple of rounds (and even giving them a sample app), I gave up. Some groups have really sharp moderators watching their Connect postings, some don't. I had a workaround, and too much work to do on my own product to keep fighting with them- I believe they "Closed, Not Reproduced" the issue. Ha!

Hi,
Did you end up filing a bug for this?

2008-03-14T16:56:00.000-07:00

Hi,
Did you end up filing a bug for this?

Comments on Matt on ... Whatever: LINQ to SQL enum mapping

global:: helped me too - VS2010 RC with Framework ...

Your post is still helping - it was the fix to my ...

My project was building fine but suddenly that DBM...

Awesome. You saved me!!

Your nearly-two-year-old post has just saved my da...

Thanks a lot for the fix mate. Wonder how you came...

Thanks Matt for the fix, for me I haven't set a na...

This bug still exists in the release version of VS...

Broken keyboard on this bug. Thank you.

You missed the point- setting the non-namespace-qu...

Works for me, if I just set the enum's type name, ...

I did (https://connect.microsoft.com/VisualStudio/...

Hi,Did you end up filing a bug for this?

Hi,
Did you end up filing a bug for this?