Browse by Tags

• .net
• .NET 2.0
• .NET 3.0
• .NET 3.5
• .NET 4.0
• .NET RIA Services
• ASP .NET
• ASP.NET
• C#
• Database
• DBML
• IIS
• MMC
• Silverlight
• Visual Studio 2008
• Visual Studio 2010
• Visual Studiol 2008

• Bug with Visual Studio 2010 and DBML designer – Changes not causing regeneration of DataContext code.

  Vote for this bug if you encounter this problem.  Basically in 2010, if you regen the DBML file outside of VS the underlying DataContext code does not get regenerated.  This is bad because changes outside of VS 2010 to your DBML will not get Read More... Posted Monday, July 13, 2009 9:53 PM by david | 0 Comments Filed under: C#, .NET 3.5, Linq, Visual Studio 2010, .NET 4.0, DBML

• Solved: Connection String does not show up when editing the connection property of a DBML file.

  The DBML editor in Visual Studio 2008 tends to create a nasty name in the settings file for your database connection string.  We have our databases named with the associated environment e.g. Product_dev or Product_test.  When the DBML editor Read More... Posted Friday, June 26, 2009 1:19 AM by david | 0 Comments Filed under: Database, .net, ASP.NET, Linq, DBML

• .NET RIA Services – New Domain Service Class does not show your available DataContexts

  One issue I noticed with RIA services is that LINQ to SQL DBML classes do not show in the Available Data Context drop down until you have compiled the dbml at least once.  This is for obvious reasons but it would be nice to have a warning message Read More... Posted Friday, May 08, 2009 4:56 PM by david | 0 Comments Filed under: ASP .NET, C#, Visual Studio 2008, .NET 3.5, Linq, Silverlight, .NET RIA Services

• Linqpad

  Ha!  Kudos to Joseph Albahari for a cool tool!   http://www.linqpad.net/ Read More... Posted Wednesday, April 22, 2009 6:09 PM by david | 0 Comments Filed under: .NET 3.5, Linq, .NET 3.0

• Why is .NET 3.5 not listed in the ASP.NET tab in the IIS MMC Snap-In?

  I keep seeing this question posted and I anticipate seeing the question pop up more often. The short answer is: There is no .NET 3.5 application layer for the IIS application context configuration tab. You should set the Framework version to .NET 2.0. Read More... Posted Wednesday, November 28, 2007 6:29 AM by david | 0 Comments Filed under: .NET 3.5, .NET 2.0, MMC, Visual Studiol 2008, ASP.NET, IIS, Linq, .NET 3.0