Despite this, the best error message I've ever seen (second, "This operation can destabilize the fare space- Time continuum "), it is also one of the most disappointing.
I have developed an ASP.NET MVC site that works fully through VS2008. It is fully hosted on a local IIS7 server (Win2008Server and Win7beta), and also works on another Win2008Server host. A few days ago, I uploaded the site to a new host (Win2008Server), and "Operation Runtime Could Unset" in error, whenever one of my LinqToSQL statements (and only one) is evaluated .
The question in question is simplified to the point of ambiguity, and even then whenever I evaluate the result then the error occurs:
var result = Select db.calendarEvents E from = E; Foreach (different phenomena in result) // error occurs on this line {...} The remote host is running in full confidence in the question, and there is no switch statement in sight (Both of these issues were related to error on Google).
A similar problem was reported, but there is no interface (which I know).
Any ideas?
--- Just a break: The table time data type in the question uses, and the map for a timezone property is obviously only available in .NET 3.5 SP1. I am waiting to know if SP1 is installed in my new host ...
Okay, the end result was that my site was set on the net on my host server. 3.5 installed (not SP1), and a table that used the time SQL datatype, was broken with the above error. Indicates that LINQ supports SQL to start mapping these new types with .NET 3.5 SP1.
My host has migrated my site to a .NET 3.5 SP1 server, and it's all good.
Comments
Post a Comment