Archives
-
.NET Framework 3.5 SP1 Changes
-
Training for ASP.NET Virtual Earth Control
For all of those that develop or would like to develop ASP.NET solutions with integration of Virtual Earth using the new ASP.NET control here is the link for a very interesting series of videos and samples about how to use the ASP.NET Virtual Earth control.
-
Windows Presentation Foundation Major Release 3
With the release of the .NET Framework 3.5 SP1 the WPF suffered the third major release of it’s short history.
-
Silverlight Tools Beta 2 for Visual Studio 2008 SP1 RTM
It’s already available the Silverlight Tools Beta 2 for Visual Studio 2008 and Visual Studio 2008 with SP1 RTM version, as the Beta version of the SP1 of Visual Studio 2008 is no longer supported.
-
Import 3D Objects into Virtual Earth
With the aquisition of Caligari by Microsoft in February 2008, it was made available a free tool, named TrueSpace that was placed for download completely for free. This will allow the development of solutions using Virtual Earth in his 3D version. This was without any doubt one of the greater drawbacks of developing with Virtual Earth, but now this is all solved as Chris Pendleton the Virtual Earth Team Evangelist announced on his blog and were he explains how to do each of the steps. have fun with this new and very interesting feature made available for Virtual Earth.
-
RTM of SP1 for .NET 3.5, Visual Studio 2008 and Visual Studio Team Foundation Server Released
The RTM version of SP1 for .NET Framework 3.5, Visual Studio 2008 and also Team Foundation Server is already available for MSDN Subscribers, so check and download it, and start using it. It’s great.
-
Composite Application Guidance for WPF (Prism) now goes to Silverlight 2.0
As I said in a previous post Composite Application Guidance for WPF formerly known as "Prism" was made available and this was a great news because now the development of WPF solutions is easier and as a Guidance that will lead us all the way, helping us make the right choices whenever problems emerge. This is great but being Silverlight a subset of WPF, so wouldn't be great to have the same kind of guidance for Silverlight 2.0?