Did you ever have a problem with referencing a assembly with Visual Studio? Visual Studio .NET 2003 "usually" updates the reference to the assembly if a new version of the assembly is available.
With Visual Studio 2005 it can be configured if the reference should be updated automatically to the current version, or if a reference should be fixed with one version:
I like this new feature :-)
Yesterday Klaus Aschenbrenner was given a presentation for the .NET User Group Austria: XQuery & XML Support in SQL Server 2005. This presentation is repeated for the .NET User Group Styria and the London .NET User Group.
Do you have something to talk about at TechEd Europe? Submit a BOF session at http://www.ineta.org/Bof.
There are already three proposals where you can give your votes:
- MSF and MOF, what's in it for me?
- MS Patterns & Practices - are they relevant to me?
- Now what are they going to do to my VB?
Don Box would like to remove SOAPSUDS.EXE from your laptop ;-)
He has some good information about The Good, The Bad, and The Ugly about .NET Remoting.
Are you attending TechEd Europe? I have a presentation about localization and globalization of .NET applications:
Creating a Klingon Culture
I already had a Klingon sample to extend resources with help of a custom resource reader:
nuqneHdir and Qapla'
This time I will go further and have a deeper look into how to extend localization and globalization features. Of course I will also show .NET 2.0 changes. What are your issues with localization / globalization?
I just had a discussion with a friend who had problems using Queued Components with ASP.NET.
- Using the queue moniker from ASP.NET, the ASPNET account needs access to the type library.
- With QC you cannot pass serializable objects with the paremeters. The objects must implement IPersistStream. The easiest way to send objects to the QC is by using strings.
All these issues can be read in chapter 10 of my upcoming book .NET Enterprise Services.
The last chapter of my upcoming book is a case study that includes a complete solution with multiple projects. The scenario of this case study includes multiple cooperating companies.
- Data access classes that use ADO.NET for invoking stored procedures in SQL Server
- Serviced components that makes use of the data access classes
- A Windows Forms application as a client-front end to access the serviced components
- A Web service that's used by the "partner" company
- Queued components for disconnected access
- A Web application as front end for end users
Now I'm going back to my earlier chapters to work through the comments of my reviewers :-)
Eric Gunersson blogs about Whidbey C# Features:
- C# Featurette #3: Static Classes
- We can use the static keyword with classes. Until now I've always used private constructors, the static keyword is better.
- C# Featurette #2: Inline Warning Control
- I hope it's not neccessary to use this feature as often as it was necessary with C++
- C# Featurette #1: Reference and Value Type Constraints
- This is really great - defining constraints with generics.