This is a short weekend at home for me, because tomorrow evening I've to go to Milan for the Windows Professional Conference 2004.
Next week will be a full immersion week on .NET and related technologies. I'll meet Dino Esposito, Francesco Balena, the UgiDotNet Spiderman Andrea Saltarello ( 
) and many other.
My schedule will be focused expecialy on .NET programming and what I'm planning to listen will be:
Francesco Balena: Windows Form & Smart Client programming, .NET Worst Practice, news on the 2005 platforms.
Dino Esposito: ASP.NET Programming, optimization and scalability, ASP.NET Security, ASP.NET 2.0
Giuseppe Di Mauro: N-Tier Enterprise Programming with .NET (really curious to see this)
plus many other interesting things, such as ADO.NET 2 features, SQL Server 2005 Programming, Web Services and SOA, Web Services Enhancements 2, .NET and software testing, Windows Server security and administration, the future of Windows platforms (Longhorn, XP Reloaded etc) and many more...
As you can see, a really full week ut I'm excited to start it...
I hope to have time to blog something to discuss with all the community.
I've seen this decision only now... the Refactoring feature will be cut off from Visual Basic .NET 2005! 
The decision is announced officially on the Visual Basic .NET Team Blog. Really a bad news...
Seems that the main problem for this cut is the limited time to release the product... I don't agree with this, I think that all the community and VB developers will be more happy to have a complete product some months later than an incomplete product soon. The Sam Gentile's post about this completely respect my opinions.
Why VB.NET must be always a step under C#? I agree with Sam: by cutting Refactory the team has deprived the worthwhile VB.NET community of having a true enterprise language. 
A little "message on the bottle" for the VB.NET team... I don't know what are your schedule for the features of VB.NET, but you've done a big error and caused a big lack on the final product that we're waiting for. I love VB.NET and I hope that errors like this can't be the cause to migrate to other languages... Think about this!