Friday, September 03, 2004

And they said to you "no one will do drivers in .NET"

Ok, it's only the control center, but it's a start... And it's from ATI, what means that soon any machine with an ATI card will have the .NET framework installed.

Via Patrick Steele's .NET Blog


Thanks to David Stone, I'm a proud GMail user. Since I run my own Exchange server, the 1GB is not my primary interest (although I have some friends that loved it!). Most of my interest on it is learning how to do a lightining-fast, cleanly designed, cross browser UI.
If you are interested in a Google mail account, Google gave me 12 invites, and I already spent 6 of them. If you want it, drop me a comment or an e-mail with your e-mail address (don't forget to obfuscate it, beware of spambots) an your name, and I'll invite you.
[Update: now only 3 to go...]

Wednesday, September 01, 2004

SoapInclude & XmlInclude

Yesterday, I coded a webservice that needed to return an array of objects that derived from a common base (abstract) class. When I tried to access the webservice, I had the following message:

The type XXX.YYY was not expected. Use the XmlInclude or SoapInclude attribute to specify types that are not known statically.

I thought: "Doh! Sure! ASP.NET needs to know about all the concrete classes, not only about the base class to be able to generate a proper WSDL, so a proper proxy client can be generated. Simple! Just add a SoapInclude(typeof()) attribute for each of the concrete classes and there we go!".
And so I did it. It didn't work.
I copy & pasted the MSDN sample for the SoapInclude attribute. It didn't work.
I tried it on a machine without SP1. It didn't work.
I tried to add the SoapInclude() attribute on the base class. It didn't work.
On a desperate try, I remove all the SoapInclude() attributes and used XmlInclude() attributes (remember the error message)? Yeah! It worked!
So, I leave this for anyone who may have the same problem and find me through Google or who can explain me why the SoapInclude() attribute didn't work.

Installing .NET 1.1 SP1 and Resharper 108

You can find Microsoft .NET Framework 1.1 Service Pack 1 here and a version for Windows Server 2003 here.
I installed it yesterday and it required a reboot (probably because I was running RSS Bandit, coded in C#). After the reboot, my Resharper trial (build 108) didn't work anymore, giving me a strange HRESULT.
My solution:
When VS.NET asked about removing Resharper, I chose "No". Then, I removed Resharper through "Add/Remove Programs" and reinstalled it. Everything went back to normal.
And why am I saying this? While everything seems fine with my software, it tastes bad. Something in .NET SP1 installation broke Resharper, a .NET application just like mine. Why? What broke? It's hard to say that Jetbrains did something wrong on Resharper that would break on a service pack installation (contrary to Vault, which used a poor design decision). Sooner or later (probably when this gets into Windows Update), my customers will upgrade to SP1 and this may happen to them. We have people testing our software under SP1 (heck, even my machine is running it), but I won't feel comfortable until a lot of people upgrade.

This page is powered by Blogger. Isn't yours?