An ATA controller on a load balancer failed this morning for Shacknews.com.
From what I understand, they are nearly done repairing the server.
February 26, 2008
February 19, 2008
Classic Content Flashback: "SiN Episodes" and USK
Sorry I've been quiet. I've been buried in work and beta testing for VistaGameDoctor.com SP1.
In the meantime, here's a flashback to some darker times. These posts summarize the changes that we had to make to get "SiN Episodes" shipped in Germany.
Part 1: http://www.romsteady.net/blog/2006/11/sin-and-usk-part-1.html
Part 2: http://www.ritualistic.com/content.php/articles/061205_sin_usk.php
Part 3: http://www.ritualistic.com/content.php/articles/061212_sin_usk.php
Part 4: http://www.ritualistic.com/content.php/articles/061222_sin_usk.php
Part 5: http://www.romsteady.net/blog/2007/01/sin-and-usk-part-5.html
Part 6: http://www.romsteady.net/blog/2007/01/sin-and-usk-part-6.html
In the meantime, here's a flashback to some darker times. These posts summarize the changes that we had to make to get "SiN Episode
Part 1: http://www.romsteady.net/blog/2006/11/sin-and-usk-part-1.html
Part 2: http://www.ritualistic.com/content.php/articles/061205_sin_usk.php
Part 3: http://www.ritualistic.com/content.php/articles/061212_sin_usk.php
Part 4: http://www.ritualistic.com/content.php/articles/061222_sin_usk.php
Part 5: http://www.romsteady.net/blog/2007/01/sin-and-usk-part-5.html
Part 6: http://www.romsteady.net/blog/2007/01/sin-and-usk-part-6.html
February 5, 2008
WORKAROUND: The value for the property "Settings Property Name" is not valid for the current language.
Symptoms: You are setting up your DBML file in Visual Studio 2008 so that you can use LINQ to SQL, and when you try to compile, you get the following error message:
Solution: Rename your connection string key to get rid of the periods, and nag Microsoft to fix this issue.
The value for the property "Settings Property Name" is not valid for the current language.Cause:You are using a named connection string and the key for that connection string has a period in it, like "Sql.Finance.ReadWrite."
Solution: Rename your connection string key to get rid of the periods, and nag Microsoft to fix this issue.
Tags:
LINQ,
Visual Studio,
Workarounds
February 4, 2008
VistaGameDoctor 2.0 coming soon
I've been rewriting VistaGameDoctor.com so that it is more community focused. It's been a bit of a challenge, but it's been worth it because I've also been using it to wrap my head around LINQ.
LINQ does take a bit of getting used to. For example, you can have a new item in an returned class be the returned value of a function in LINQ to SQL, but you can't pass that value of the function into another portion of the query. There's going to be some fun nested query stuff going on over the next bit.
The code is about 90% done. I'm just trying to lock down a few of the more esoteric features to allow community moderators and submissions and distinguish those submissions from ones that I put up in my normal testing.
Once the test version is up, I'll post a link.
LINQ does take a bit of getting used to. For example, you can have a new item in an returned class be the returned value of a function in LINQ to SQL, but you can't pass that value of the function into another portion of the query. There's going to be some fun nested query stuff going on over the next bit.
The code is about 90% done. I'm just trying to lock down a few of the more esoteric features to allow community moderators and submissions and distinguish those submissions from ones that I put up in my normal testing.
Once the test version is up, I'll post a link.
Subscribe to:
Posts (Atom)