microsoft clickonce publishing sucks (parts 1 and 2)...

"Microsoft .NET ClickOnce Launch Utility has encountered a problem and needs to close. We are sorry for the inconvenience". who is this "we" who is sorry? are they sorry enough to actual do something about it besides apologize? the details say applaunch.exe has a system.io.fileloadexception. this seems to be another example of microsoft putting out sloppy code. my google search shows nobody else reporting this problem. guess I'm just special :p

part 2 of why ClickOnce sucks? Joe Wirtley has already covered this very nicely - I found his post when I ran into the same problems as he did and I suggest you read it: ClickOnce and Bogus Required Assemblies.

microsoft visual studio help sucks (part 1)

notice in the screenshot step "2. click on the Compile tab". the option does not exist. therefore I cannot change my warning level. these guys sure have a hard time coordinating things (I presume at one time the program matched the help). btw, I originally posted this with windows live writer and somehow after posting to blogger, it got zapped. so I retyped this post. proper communication can be so difficult sometimes. sheesh!

microsoft windows live writer sucks (part 1)

try to publish to blogger with a picture included and you get the error:

funny, if I just use the regular blogger interface it works fine.  so why does microsoft give me options that their software doesn't support? this is a good reason to not use windows live writer.

Update: I (not surprisingly) am not the first to notice this problem. The Dino and friends futilely tried to work around it months ago.