The event will have a keynote and 3 tracks (Web Developer, UX and Architect) with 4 sessions each by the best speakers in each field.
Don’t miss it! Register now!
Today I came across this issue when trying to sign in to Windows Live Messenger.
Everyone I talked to was able to sign in, though, so I tried another account and was also able to sign in.
Binging around, I found several blog posts pointing to a post in the Messenger Support blog with the solution to this problem. In my case (Windows 7 x64) the solution would be to remove the %LOCALAPPDATA%\Microsoft\Windows Live Contacts (usually C:\Users\<Windows Logon name>\AppData\Local\Microsoft\Windows Live Contacts) folder.
Instead of removing the folder, I thought of renaming it to avoid removing my contacts for all account that were able to sign in. When I tried it, I got an error stating the the folder was already being used by another application.
Since I had Windows Live Mail open and assumed it uses the same contact store, I closed it and was able to sign in to messenger with no problems.
As a developer and architect, I find it disturbing that such errors are presented to the user. The message hinted that there was a problem signing in to the server and, as it turned out, it was a problem with only one account for only one Windows user in only one machine.
So, developers and architects out there (me included), always give the user an error message meaningful to what problem he/she is running into. Adding technical data to help support is nice but should be expressly accessed by the user (Windows Live Messenger got that part right).
Most enterprises backup their data on a regular basis and stored those backups for some amount of time.
But, beyond restoring last day’s backup or part of a previous recent backup, are these backups real useful? Will they be useful 3, 4, 5 or 10 years from now?
Nowadays, the tendency is to virtualize almost every machine which increases the probability of a successful restore in the future. But some software packages come with timed and online checking licenses and one might end up with a successful restore of an unusable system.
And what if the hardware to run the system (virtualized or not) no longer exists?
The solution is to backup the business data (instead of the system data) in a interoperable format like XML (that can contain both data and metadata).
The added benefit beyond disaster recovery is system or application migrations.
That doesn’t mean that systems don’t need to be backed up. They do, but only for operational purposes.
The tool space for software architecture has been growing. There are new tools and continuous improvement in the existing ones.
The tool allows comparing two versions of an assembly to identify API differences: API additions and removals. Comparing versions of APIs comes very handy during API design process. Often you want to ensure that things did not get removed accidentally (which can cause incompatibilities), and as APIs grow, you want to review the addition without having to re-review APIs that were already reviewed. The tool, called Framework Design Studio (FDS) supports these scenarios. – from Krzysztof’s blog post
The Lattix tools can be used in the following environments:
The site has lots of resources on its getting started section that can be used to evaluate the tools:
The latest release (Lattix 4.1) was released on April 21, 2008.
NDepend, from fellow C# MVP Patrick Smacchia, targets only the .NET Framework (stay tuned for more) is also in continuous development. Its UI is more familiar for Microsoft Visual Studio and Microsoft Office users than Lattix’s UI and a really cool feature:
The latest release (NDepend 2.8.1) was released on April 26, 2008.
The site has lots of product information:
The latest release (2008.02) was released on Marsh 26, 2008.
I just came across this today:
Framework Design Studio is a set of tools for reusable library designers. The package contains a GUI tool for viewing, reviewing, and comparing versions of managed APIs. It also contains a command line tool for generating API diff reports.
This seems to be a great tool to check if your new version of your framework will break any previous released APIs.
Although honoring the previously released APIs, your new version might have side effects and, to find out what they might be, there is another great tool: NDepend.
About the Deliverable
The Web Client Software Factory (WCSF) provides a set of guidance for architects and developers building enterprise Web applications. The factory includes samples, reusable code and a guidance package which automates key development tasks from within Visual Studio.
Using the Web Client Software Factory assets, developers can create Composite Web applications composed of independently developed and deployed modules. These modules are dynamically brought together at runtime into a common shell. Additionally the factory includes support for ASP.NET AJAX thus providing users with a richer and more responsive user experience.
New In This Release
The February 2008 release of the Web Client Software Factory has the following improvements to the June 2007 release.
In addition, this release of WCSF has the following community issues and fixes:
For those who missed my webcast (and wanted to watch it) it’s available to download at the MSEVENTS site.
Here is the list of topics covered in the WCSF geekSpeak webcast:
And here is a list of online resources: