Sebastian,
It would be nice if it worked... in the meantime to get View_Blog not to throw an error it is necessary to add [ProviderName="DNNMenuNavigationProvider"] to the container, and after that it is necessary to chase the menu all over the screen (depending under what role you log in), plus forcing the container to use DNNMenuNavigationProvider throws off the spacing on the drop-down menu, and now it looks really ugly... So it works, kind of, and I hate to explain clients that this is a free module, and that is what you get for nothing, here is how you chase the menu when you wish to add a blog entry..., but if you want a better one, you will have to buy one. More business to other blog module developers, which is perfectly fine with me, it's just that not all non-profit companies can come up with enough money to buy additional modules at the moment.
So here I am, reading through forums, finding multiple people having the same issue, and then seeing your reply got me puzzled, why is it bundled with DNN5 if it's not working properly? I think that's the reason why John is asking the question about compatibility.
Is there any solution for us who struggle with this issue?
I'm just frustrated that I can't get the site nice and complete because of this "free" blog module that my client wants.
Thanks,
Val