development blog for the wicked stuff we encounter

I'm using MySql for a small project as the database backend with the MySql Connector for .Net by MySql AG. (this was done by ByteFX formerly) and found out that however the tables were created to be UTF-8, INSERT and UPDATE were failing on special (Hungarian, Russian etc.) characters! After some RTFM, I found the appropriate solution: add the charset=utf8; part to your connection string, and everything will be nice and lovely :)

Today, I got mad again. These bastards over at Redmond totaly screwed up the deployment and the upgrade mechanisms in Visual Studio 2005. I have a huge project with about 30-40 aspx pages, and I used to have them compiled into one dll with VS 2003. Now, this f*** creates several small App_whatever_hexid.dll-s to make you cry out loud. Of course this breaks the IIS sites sometimes, when you deploy with overwrite - shit happens, dual references.
The best: you can not create a solution. Simply you can't, you can only have several projects (or whatever, because it is now page based) but you can not clearly group in one.
I found an MS WebAPplication Support stuff; but it still does not play as I want. Anyway, at least it will let you create a solution, BUT can not compile and deploy in one step.. so i think i need to write a macro to do this. At least this WAP lets you create a single DLL.
Another madness: the objects created in the aspx file are not referenced in the aspx.cs directly, but they are stored in a separate file with .designer.aspx.cs extension... If you want to add old VS2003 files to a new project, you need to right click and say 'Convert it to a Web Application' - WHY?!
The IDE is the slowest ever. Intelisense is better by no need to type the 'this.' preword to list the local objects.. but fuck, it's 2006, why should I wait seconds to switch between the desing and the code view?!
If you have a Marshalled or InterOped dll, make sure to recompile it, because in 80%, it will not work, and will report funny error codes... who told a thing about framework uncompability issues in *that* low level?!
One positive feeling stuff: VS2005 at least doesn't erase all lines from the InitializeComponent() function when you add events to any object in the Design view, as it was in VS2003 :)

I store my personal documents in a 128bit encoded .dmg file, which is password protected (good old porns ;) I finally faced the problem, that I've grown out this image - but i had no place to create a new one and copy over the contents (I was working heavy on a dvd edit) - so i RTFM. hdiutil resize -size nn[m|g|t] mysecret.dmg