Channel 9 Forums - Coffeehouse - .NET 2.0 SP1 broke our app http://mschnlnine.vo.llnwd.net/d1/Dev/App_Themes/C9/images/feedimage.png Channel 9 Forums - Coffeehouse - .NET 2.0 SP1 broke our app http://channel9.msdn.com/Forums Channel 9 keeps you up to date with the latest news and behind the scenes info from Microsoft that developers love to keep up with. From LINQ to SilverLight – Watch videos and hear about all the cool technologies coming and the people behind them. http://channel9.msdn.com/Forums en Sat, 18 May 2013 13:54:44 GMT Sat, 18 May 2013 13:54:44 GMT Rev9 8 -8 -1 Coffeehouse - .NET 2.0 SP1 broke our app One of our clients installed .NET 2.0 SP1 this week and suddenly our .NET 2.0 application (which has been running fine for 2 years now) started producing errors. Luckily, we found the problem pretty fast and were able to solve it and release a new version. Has this happened to other Niners? Is there a list somewhere with the breaking changes in SP1?

]]> http://channel9.msdn.com/Forums/Coffeehouse/259521-NET-20-SP1-broke-our-app/259521#259521 Fri, 07 Dec 2007 12:33:47 GMT http://channel9.msdn.com/Forums/Coffeehouse/259521-NET-20-SP1-broke-our-app/259521#259521 Tommy Carlier 8 http://channel9.msdn.com/Niners/TommyCarlier/Discussions/RSS Coffeehouse - .NET 2.0 SP1 broke our app What did break in your scenario?

]]> http://channel9.msdn.com/Forums/Coffeehouse/259521-NET-20-SP1-broke-our-app/f67c3d40bd4541b6985e9df900992d4a#f67c3d40bd4541b6985e9df900992d4a Fri, 07 Dec 2007 12:41:28 GMT http://channel9.msdn.com/Forums/Coffeehouse/259521-NET-20-SP1-broke-our-app/f67c3d40bd4541b6985e9df900992d4a#f67c3d40bd4541b6985e9df900992d4a Christian Liensberger 8 http://channel9.msdn.com/Niners/littleguru/Discussions/RSS Coffeehouse - .NET 2.0 SP1 broke our app Assume you have a DataTable t where one of the columns is of type string. t.Select("x=3") should select the rows where x is "3". In .NET 2.0 this was not a problem. In .NET 2.0 SP1 we had to put the number between quotes, like this: t.Select("x='3'");

]]> http://channel9.msdn.com/Forums/Coffeehouse/259521-NET-20-SP1-broke-our-app/080f67ce052048ff8e299df900992d91#080f67ce052048ff8e299df900992d91 Fri, 07 Dec 2007 12:47:29 GMT http://channel9.msdn.com/Forums/Coffeehouse/259521-NET-20-SP1-broke-our-app/080f67ce052048ff8e299df900992d91#080f67ce052048ff8e299df900992d91 Tommy Carlier 8 http://channel9.msdn.com/Niners/TommyCarlier/Discussions/RSS Coffeehouse - .NET 2.0 SP1 broke our app I see. Smiley Luckily I'm not having DataTables. Scott had a list of changes, but I don't know if that will do it for you... I think he only covers some of the public methods and stuff that changed.

]]> http://channel9.msdn.com/Forums/Coffeehouse/259521-NET-20-SP1-broke-our-app/0e48a56f9455485d87be9df900992de3#0e48a56f9455485d87be9df900992de3 Fri, 07 Dec 2007 13:02:04 GMT http://channel9.msdn.com/Forums/Coffeehouse/259521-NET-20-SP1-broke-our-app/0e48a56f9455485d87be9df900992de3#0e48a56f9455485d87be9df900992de3 Christian Liensberger 8 http://channel9.msdn.com/Niners/littleguru/Discussions/RSS Coffeehouse - .NET 2.0 SP1 broke our app
TommyCarlier wrote:
One of our clients installed .NET 2.0 SP1 this week and suddenly our .NET 2.0 application (which has been running fine for 2 years now) started producing errors.


How much fun is that? Someone loads an update without your knowing about it and next thing you know the support guys are swamped .. sigh. Now try explaining to your customer that it was Microsoft that killed the app ..

]]> http://channel9.msdn.com/Forums/Coffeehouse/259521-NET-20-SP1-broke-our-app/aaa110ca66bf4856b0839df900992e2e#aaa110ca66bf4856b0839df900992e2e Fri, 07 Dec 2007 13:04:04 GMT http://channel9.msdn.com/Forums/Coffeehouse/259521-NET-20-SP1-broke-our-app/aaa110ca66bf4856b0839df900992e2e#aaa110ca66bf4856b0839df900992e2e Rossj 8 http://channel9.msdn.com/Niners/Rossj/Discussions/RSS Coffeehouse - .NET 2.0 SP1 broke our app
TommyCarlier wrote:
Assume you have a DataTable t where one of the columns is of type string. t.Select("x=3") should select the rows where x is "3". In .NET 2.0 this was not a problem. In .NET 2.0 SP1 we had to put the number between quotes, like this: t.Select("x='3'");


Never rely on bugs and undocumented features. Very old wisdom.

]]> http://channel9.msdn.com/Forums/Coffeehouse/259521-NET-20-SP1-broke-our-app/87658d0894ee44a99edf9df900992e7c#87658d0894ee44a99edf9df900992e7c Fri, 07 Dec 2007 15:53:45 GMT http://channel9.msdn.com/Forums/Coffeehouse/259521-NET-20-SP1-broke-our-app/87658d0894ee44a99edf9df900992e7c#87658d0894ee44a99edf9df900992e7c Alexei Pavlov 8 http://channel9.msdn.com/Niners/BlackTiger/Discussions/RSS Coffeehouse - .NET 2.0 SP1 broke our app When you create an expression for a filter, enclose strings with single quotation marks:

"LastName = 'Jones'"

Found at MSDN from the System.Data.DataColumn.Expression property.

]]> http://channel9.msdn.com/Forums/Coffeehouse/259521-NET-20-SP1-broke-our-app/875efa112b214da98e9d9df900992ec9#875efa112b214da98e9d9df900992ec9 Fri, 07 Dec 2007 16:19:30 GMT http://channel9.msdn.com/Forums/Coffeehouse/259521-NET-20-SP1-broke-our-app/875efa112b214da98e9d9df900992ec9#875efa112b214da98e9d9df900992ec9 ZippyV 8 http://channel9.msdn.com/Niners/ZippyV/Discussions/RSS Coffeehouse - .NET 2.0 SP1 broke our app There are similar issues with SqlStatements in 2.0. While doing inserts .net is picky about quotes vs single quotes on insert statements.

]]> http://channel9.msdn.com/Forums/Coffeehouse/259521-NET-20-SP1-broke-our-app/3e50cdcb1fc243e3aa7c9df900992f38#3e50cdcb1fc243e3aa7c9df900992f38 Sun, 09 Dec 2007 01:49:06 GMT http://channel9.msdn.com/Forums/Coffeehouse/259521-NET-20-SP1-broke-our-app/3e50cdcb1fc243e3aa7c9df900992f38#3e50cdcb1fc243e3aa7c9df900992f38 tgraupmann 8 http://channel9.msdn.com/Niners/tgraupmann/Discussions/RSS