Geeks With Blogs

Tim Huffam Dotting the I and crossing the T of I.T. June 2008 Entries
Visual Studio (VS200) loosing it's source control bindings
VSTS2008 has, on occasion, lost it's source control settings - specifically, the bindings to TFS server for a given solution and it's projects. This seems to be because the solution and project files are not being updated when you use the TFS Source Control Explorer to do a 'Get Latest' - a 'feature' of VS2008 which allows you to work disconnected/offline - however it seems to have an issue trying to reconnect itself. To resolve we simply removed the local source directory and did a 'Get Specific ......

Posted On Thursday, June 12, 2008 11:08 AM

Dundas chart error databinding: Series data points do not support values of type "myclass", only values of these types can be used: Double, Decimal, Single, int, long, uint, ulong, String, DateTime, short, ushort.
The following error can occur when executing the .DataBind() method on a Dundas chart object within an ASP.Net page (.Net 3.0): Series data points do not support values of type "myclass", only values of these types can be used: Double, Decimal, Single, int, long, uint, ulong, String, DateTime, short, ushort. I had set the DataSource property to a generics List of myclass objects (List<myclass>). It turns out that this error is caused by a mismatch between the type of objects within the list ......

Posted On Thursday, June 12, 2008 8:23 AM

Checking ExpectedException and is thrown by specified type
Using the VS2008 unit testing framework, if you want to check for an expected exception, sometimes your test will pass because the exception was raised by another line of code - after the line you were specifically trying to test. To resolve this you have to manually check for the expected exception - using a try-catch block. However there is a catch (excuse the pun).... Microsoft.VisualStudio.Test... will not fail when types are different as long as the actual ......

Posted On Friday, June 6, 2008 4:19 PM

System.ObjectDisposedException: Cannot access a disposed object. Getting Linq to prepopulate/explicitly fetch data from the database.
Exception: System.ObjectDisposedExcept... Cannot access a disposed object. Object name: 'DataContext accessed after Dispose.'. This can occur when using Linq to SQL to retrieve data from a database - and when you try to access data after the data context object has been disposed. More specifically, the exception occurs when trying to access an item that has not yet been retrieved from the database and the data context object has been disposed. This often occurs when using a variable, that was populated ......

Posted On Tuesday, June 3, 2008 9:41 AM

Copyright © Tim Huffam | Powered by: GeeksWithBlogs.net