This post originated from an RSS feed registered with .NET Buzz by Doug Thews. Original Post: VB.NET/VS.NET 2005 Bug for SQL Server Projects Feed Title: IlluminatiLand Feed URL: http://apps5.oingo.com/apps/domainpark/domainpark.cgi?client=netw8744&s=JETBRAINS.COM Feed Description: A technology blog for people enlightened enough to think for themselves Latest .NET Buzz Posts Latest .NET Buzz Posts by Doug Thews Latest Posts From IlluminatiLand

Thanks to Niels Berglund for helping me confirm that there is a strange bug only for VB.NET SQL Server projects created in VS.NET 2005.

If you try and rename either the assembly or root namespace properties inside the MyProjects property page, you will get a very strange error message about there being a static member/variable inside the autogenerated VB.NET code module MySettings.vb.

What's strange is that the MySettings.vb module does not get auto-generated after the rename, so I'm not completely certain why it would compile and deploy correctly before but not after renaming these properties. I think it's a case of an error message not being correct, but I haven't been able to confirm this.

But, for now, you should probably look to keep the defaults of root namespace and assembly name when working with VB.NET SQL Server projects in VS.NET 2005.