I would say the goal is to beat the clock rather than to struggle with cryptic puzzles. You get timed on your escape.
Fun for someone that is looking of a little brain teaser as a short break. I finished this in 20minutes. What did you score?

M


Skype has more than 480 million user accounts - almost twice as many as Facebook - and the application comes bundled with more than 50 mobile phones and even the Sony PSP.
The funny thing is that Skype isn't even a financial success story, but it has long been a leader in Internet telephony.
The online auction powerhouse, eBay, bought Skype from entrepreneurs Niklas Zennstrom and Janus Friis for $US2.6 billion in 2005, but the agreement did not include a fundamental piece of peer-to-peer communications technology that drives the software.
eBay may have to shut down Skype due to this licensing dispute.
eBay has since been licensing the technology from the founders’ new company, Joltid, but the pair recently decided to revoke the licensing agreement. eBay is now trying to force Joltid to let it continue using the technology through legal battle in the English High Court of Justice.
Will you be able to function without skype?
This game is like super duper fun! Really enjoyed it. Its quick and simple and fun to do if you 10 minutes to spare. I really recommend playing this game, you will absolutely love it. It does get boring after a bit but your really wanna go get those achievements! Can you make this little penguin try to fly .. give it a try!
Zero Punctuation is a video game review series created by comedy writer, video game journalist and gamer Ben “Yahtzee” Croshaw and produced by online magazine The Escapist.















I dint like the new Harry Potter movie all that much, but at least we have a silly funny thanks to it.





From my previous post on room games, we played Vision. It was a bit long and it had less direction than the first game, but I must say I enjoyed it. Especially at the end when you open a door and you get hope, but it's just a balcony.
An email has been going around claiming that the point system has been implemented in South Africa. This is not true. I have received about ten copies of this email and I think it's just fair that we all have the facts. Below is an article that proves differently.
MEDIA STATEMENT: AARTO DEVELOPMENTS [6 July 2009]
During his address at the National Assembly on 3 July 2009 the Minister of Transport committed to the implementation of the AARTO (Administrative Adjudication of Road Traffic Offences) throughout the country in 2010. The AARTO seeks to effect an efficient road traffic management environment in the country.
The objective of the AARTO is to enhance road safety and instill the culture of compliance with road traffic safety legislation. To ensure compliance, the introduction of the points-demerit system will be implemented as part of the national roll out in 2010.
The purpose of the pilot project both in Tshwane and
Infringers issued with infringement notices in both pilot projects will be aware of the allocation of the demerit points on the infringement notices received. This is part of the educational and communication awareness drive to inform infringing motorists of the workings of the demerit points system. Currently motorists are not being penalized in terms of the demerit point system. However, as from 2010 when the demerit point system is implemented throughout
The demerit point system may lead to the suspension and ultimately to the cancellation of the driving license.
The best source of information is the website of AARTO at www.aarto.co.za
For demerit points visit the AARTO Chargebook at http://www.aarto.co.za/public/downloads/027_AARTO-Chargebook-July-2008-Part3.pdf
M




Visual Studio 2008 is a superset of Visual Studio 2005 and given framework multi-targeting and the layered approach of Framework 3.0 and 3.5, it makes perfect sense to move your development environment over.
When migrating from Visual Studio 2003 the issue is that: you are on a different CLR version (1.1) which has some breaking changes compared to the CLR 2.0 (which is used by Fx 2.0/3.0/3.5). You are also on a different framework version (1.1) which has some breaking changes compared to Framework v2.0 (which is also an essential part of Fx 3.0/3.5). There is no reason for you to go to VS2005 as an intermediate step, so by all means go from the IDE of 2003 to 2008, but be prepared to face all the issues people faced when they moved from Fx 1.x to Fx 2.0.
Breaking changes are categorized in design-time changes (Visual Studio changes: design, compile, project upgrade) and runtime changes (.NET Framework). Runtime changes impact application compiled with 1.0 or 1.1 running on 2.0, but can also impact application originally written in 1.0 or 1.1 and then recompiled for 2.0. Instead, design-time changes do not impact application compiled for 1.0 or 1.1 and just running on 2.0. You just get design time changes if you recompile your application to 2.0. So, my advice is of course to have a look to this list and if your application implements one of the presented issues, then implement the described workaround.
Migration Steps
Migrating from 2.0 to 3.5 requires some changes because there is a new assembly that has been added alongwith System.Data. The new assembly is System.Data.DataSetExtensions which has some DataSet properties transferred from System.Data.
If you plan to convert from 2.0 to 3.5 and if you are using System.Data with dataset in existing project, the dataset extension properties will not comppile.
The solution will be simple when converting .prj file to use framework 3.5 you have to add new assembly reference to it.
Check these very interesting posts on migrating. It will help us a lot
http://www.danielmoth.com/Blog/2007/10/migrating-from-net-framework-v1x-to.html
http://blogs.msdn.com/peterlau/archive/2006/05/11/595294.aspx
Microsoft .NET Framework 1.1 and 2.0 Compatibility
http://msdn.microsoft.com/en-gb/library/ms994381.aspx
Compatibility Testing Scenarios
http://msdn.microsoft.com/en-gb/library/ms994387.aspx
-----------------------------------------------------------------------------------------------------------------
BREAKING CHANGES
Below is a list of all of the breaking changes made in the newer versions. The links next to the issues contain the work around solutions.
.net 2.0
http://msdn.microsoft.com/en-us/library/t357fb32.aspx
Design Time Breaking Changes
http://msdn.microsoft.com/en-us/netframework/aa570326.aspx
C# http://msdn.microsoft.com/en-us/netframework/aa497232.aspx
System.Data http://msdn.microsoft.com/en-us/netframework/aa497234.aspx
· Design time connection string will not get upgraded automatically from native ODBC to managed client when upgrading a VS6 database project. Data designers in v2.0 do not work with ODBC connections.
Visual Studio http://msdn.microsoft.com/en-us/netframework/aa497236.aspx
· Solution configuration changes after migration so that a peoject will be marked “Do not build” even though it was marked to be built, for solution with the same GUID
· Extensibility no longer uses Microsoft.Office.dll
· Build Error after migrating an application that compiles in VS2003: Invalid characters in resx files
Windows Forms Design http://msdn.microsoft.com/en-us/netframework/aa497237.aspx
· V1.1 Controls with an AutoSize property that is not a Boolean will throw an exception when used in the v2.0 designer
CLR Design http://msdn.microsoft.com/en-us/netframework/aa570329.aspx
· Aligning TlbeExp behavior with run-time behaviour
· New String.Split overloads make certain existing calls ambiguous
· System.DirectoryServices.SearchWaitHandler class is removed
XML and Serialization http://msdn.microsoft.com/en-us/netframework/aa497238.aspx
Run Time Breaking Changes
http://msdn.microsoft.com/en-us/netframework/aa497239.aspx
CLR http://msdn.microsoft.com/en-us/netframework/aa497241.aspx
Fusion http://msdn.microsoft.com/en-us/netframework/aa497243.aspx
Localization http://msdn.microsoft.com/en-us/netframework/aa497244.aspx
System.Data http://msdn.microsoft.com/en-us/netframework/aa497245.aspx
· RejectChanges() to have cascade semantics like AcceptChanges, it is to be independent of the current DataRow state
· V2.0 has a new set of Performance Counters that are specific to each provider; all counters in the .NET CLR Data category have been obsoleted
· In 1.0 and 1.1 if a user does not specify a value or set the Size to zero on the Parameter object the Size was reported as Zero for OleDB, Odbc, OracleClient. Internally these 3 providers, we inferred the size and when we bound the parameter to the underlying stream to send to the server, we inferred the size and reported that to the server. SqlClient inferred from the value if a value exists and reported this inferred size.
· In v1.1 DataTable.rows.Remove(row) does not actually remove rows that are in ‘deleted’ state. Removing is conditional, based on the state of the row being removed
· Introducing type checking for UDTs/Object, may break applications relying on *no* type checking
· The new XML inference engine assigns different Column ordinals in some specific cases
· Deprecated unused property DataTable.DisplayExpression in v2.0
· DataRow is cleared when the value of one column (cell) is changed
· XSD: a Fixed value compares to be the same as in the schema, even though it has multiple Cyrillic-E ( 0x0400) characters
· XmlDataDocument uses internal APIs to create partially initialized DataRows. A DataSet containing such rows if merged into an empty DataSet may result in a constraint violation exception in version 2.0. In v1.x, no exceptioni was being thrown
· Introducing type checking for UDT DataColumns may break applications relying on *no* type checking
· The behavior of LinePosition in XmlTextReader.ReadChars method differs between v1.1 and v2.0
· Casting the return value from SqlHelper.ExecuteXmlReader to an XmlTextReader, worked reliably in v1.0 and v1.1. In v2.0 this may throw a cast exception, indicating the underlying type was an xmlTextReaderImpl.
· In v2.0, DataView[DataRowView.Index]== DataRowView while this was not guaranteed to v1.x
· In v1.x DataSet.Merge(DataRow[] rows) used to use DataTable.TableName to lookup tables in DataSet whereas c 2.0 uses the combination of DataTable.Namespace and DataTable.Name to lookup tables. This results in a change of semantics for v2.0 Merge.
Enterprise Services http://msdn.microsoft.com/en-us/netframework/aa497242.aspx
· AuthenticationTypes.Secure will be used as the default authentication type for DirectoryEntry
Windows Forms http://msdn.microsoft.com/en-us/netframework/aa497247.aspx
· Addition of missing values to the KnownColors enum in order to support new System Colors
· TabControl Enter and Leave events are raised for Tabs being clicked in addition to when focus leaves a TabPage
· Mouse Enter and Leave events are now raised for scrollbars and ScrollableControl
· Calling TreeNode.Bounds.Location in the Form’s Load event returns 0,0
· The first RadioButton in a group doesn’t become checked when the first RadioButton in the group gets focus
· No KeyPress event for (Char) 127 + different handling comparing th v.1.x
· ComboBox.PreferredHeight does not return the correct value as expected
· BindingContextChanged event fires less number of times when LB is added/removed to a form
· January PAG blocks are broken on v.2.0
· Layout events occr more frequently and earlier in v2.0 than in v1.1
· The Cursor property is now respected for the ComboBox Text area
· Windows Forms will now throw an IllegalCrossThreadException when a debugger is attached and a property of a control is accessed from a thread it wasn’t created on.
· Backgrounds that were transparent in v1.1 are showing up as grey in v2.0
· Setting the ImageList.Stream property to null now clears the images in the list
· Controls with a FlatStyle property now render using VisualStyles with FlatStyle.Standard set
· Accessibility changes completed in v2.0 may affect users using an accessibility reader
· Windows Forms parameters have had some name changes
XML and Serialization http://msdn.microsoft.com/en-us/netframework/aa497248.aspx
· MarshalByRef should be removed from System.Uri signature
· Bug fix for invalid URI construction logic when working with a URI scheme unknown to System.Uri
· If a callback function of an asyn delegate throws an exception, the callback will be invoked twice
· If a MBR object (whick already has an identity) is cloned, the identity is cloned as well, whick means any future remote calls to the cloned object get dispatched to the original object
· Invalid nntp and news URI’s should not be considered valid by System.Uri
· When creating a WebPermission with Regex people usually go with a simple regex like this: new Regex(“http://myhost.com/.*”) When user wants to Deny on above created permission, there are many ways to by-pass that user requirement by using a URI string with userinfo and/or explicit port, so the regex won’t match. To improve WebPremission story with Deny we want to canonicalize the user URI string by roundtriping it through System.Uri class and also we want to strip userinfo part before calling Regex.Match(). As the result some WebPermission form like using the following Regex will stop working new Regex(“http:/myshost.com:80/.*”). This is because we strip default port as part of URI string canonicalization so Regex parser will not find it anymore hence won’t match
· Supporting Nullable by default can break existing code when proxy is re-generated
· Uri.LocalPath returns excaped string for HTTP in version 1.1 but unescapes the string in version 2.0
· HTTP: acme.org now throws a parsing exception
· MarshalByRef removed from System.Uri signature
· We throw when generating WSDL if the service has duplicate [WebServiceBinding(Name=…)]
· Breaking Change – [WSS – PD7 – P2] System.Net.WebClient.UploadValues() method adds to the end of its output in ciolation of the application/x-www.form-urlencoded content type encoding scheme
· ASP.NET Web Service requests always send the AcceptEncoding: gzip HTTP header on v2.0
· Whenever an HttpWebResponse gets a 404. 500, or other error from the server, we automatically read a portion of the response content into memory and attach it to a WebException.
· GlobalProxySelection.Select behaves differently from v1.1 when an empty system.net tag is present in machine.config
· The proxy by pass list now has escaped(regex) significant characters
· NetworkStream now honours the FileAccess parameter.
· The wrong version of assembly may be loaded when deserializing in Simple mode
· XML Serialization generates AssemblyResolveEvents in v2.0 but not in v1.1
· The default for serializing DateTime is RoundTrip which is breaking
VS tools and Office http://msdn.microsoft.com/en-us/netframework/aa497246.aspx
· VSTO orkloadr requires .net 1.1 to load policy
.net 3.0
The .NET Framework version 3.0 was issued solely to include the following technologies in the .NET Framework and in the Windows Software Development Kit (SDK):
Windows Communication Foundation
Windows Presentation Foundation
Windows Workflow Foundation
Windows CardSpace
There were no feature changes to the core .NET Framework for this version.
.net 3.5
http://msdn.microsoft.com/en-us/library/bb332048.aspx
.net 3.5 SP1
Breaking Changes SP1
http://msdn.microsoft.com/en-us/library/dd310284.aspx
Common Language Runtime
Performance Improvements – NO MODIFICATIONS REQUIRED
ADO.NET - NO MODIFICATIONS REQUIRED
C#
Queries over non-generic collections now use standard C# cast semantics MODIFICATION
UIFX Server, ASP.NET, IIS
IIS Integrated Mode MODIFICATION
Integrated Windows authentication MODIFICATION
CDOSYS MODIFICATION
ASP.NET request validations MODIFICATION
URL validations MODIFICATION
Session states MODIFICATION
URL encoding MODIFICATION
DefaultHTTPHandler on IIS MODIFICATION
Server and client number formatting consistencies – NO MODIFICATIONS REQUIRED
ASP.NET hidden fields MODIFICATION
Windows Presentation Foundation (WPF)
BitmapEffect classes are obsolete MODIFICATION
Assembly name change– NO MODIFICATIONS
Hyperlink behavior– NO MODIFICATIONS
Internet Explorer in Protected Mode on Windows
CanConvertToString methods on ValueSerializer classes – NO MODIFICATIONS REQUIRED
Windows Communication Foundation (WCF) and Windows Workflow Foundation (WF)
Schema matching – NO MODIFICATIONS REQUIRED
Security improvements for authentication MODIFICATION
Partial trust support for event logging – NO MODIFICATIONS REQUIRED
RemoteEndpointMessageProperty availability – NO MODIFICATIONS REQUIRED
Running multiple .net Frameworks on the same server