I think we'd better move to somewhere else. But a big problem is that to be able to export our data (posts) from weblogs.asp.net, we have to wait for Community Server...
Thanks for bringing this out again, as a daily (or hourly?) reader of this site, what I observe and can tell is that "this" is not a democratic community. Telligent control everything, they give you air, food and water, and you guys just live without these elements. Microsoft give tons of $ to Telligent, but well, Telligent just want to keep this site as a reference (their commerical resume use), and then put the upgrade process right after all of their commerical clients.
I know, Telligent must upgrade this site in one day, but so what? this is their "job" and this is not answer the question exactly. I'd second to SubText, or any other blogging engine. I'm pretty sure all of the blogging engine/ISV would 'dedicate' a team to maintain this site 24x7, that's the same or even better quality of services than Telligent.
Thanks for the compliments Roy!
I've wanted to get a blog going on weblogs.asp.net and after trying hard to get in touch with someone at Telligent, I was told to wait a couple weeks for the CS 2.0 upgrade. That was more than a couple weeks ago. To be honest, as an MVP, I find it sad that I'm not being supported in this effort.
We said that we'd perform an upgrade when we shipped CS 2.0. At the time, back in October we thought we'd ship CS 2.0 in early January but we slipped back to late February. The delay in the CS 2.0 RTM caused a delay in the upgrade. I posted to the forum created for the bloggers on forums.asp.net giving a timeline that we are working towards for the upgrade.
As Alex says, the CS 2.0 upgrade for weblogs.asp.net is coming in the next few weeks. We'll begin testing on our staging server next week. As soon as we stabilize followiing the upgrade, we'll begin opening up new blog registrations to interested ASP.NET bloggers!
Roy, Fabrice, y'know the easiest way to get a CS2.0 upgrade is to move to codebetter LOL :)
Alex, Rich,
Thanks for the update.
The forum post was lost on me, and in any case, I wanted to make this infromation public. I'm glad we're getting an upgrade!
"As soon as we stabilize followiing the upgrade, we'll begin opening up new blog registrations to interested ASP.NET bloggers!"
Does that mean that weblogs.asp.net is a place meant for asp.net bloggers? Because I'm not an ASP.NET blogger, I'm starting to feel a little alienated.
"ASP.NET bloggers"
Definitely the time to move. Most of us are .NET bloggers, not ASP.NET bloggers.
As someone mentioned, it would be a time to move given that we still (even after the update from Alex) have no idea when the upgrade will actually happen (I did a search on the forums for "weblogs upgrade" and "timeline" but can't find the timeline thread he mentions).
Of course the biggest problem we have with moving is that we have no access to our current blog data, and I really don't want to abandon 2 years of posts right now.
I feel like we're between a rock and a hardPlace.
Well, upgrade the software does not answer the question.
The point is why do Weblogs.asp.net is foreced to use CS, but not SubText? I'm a big follower of SubText project, and I'm sure all of the other blogging engines (built by .NET) want to host this site and join this competition too!
(BTW, I do agree that this site is ONLY available for ASP.NET bloggers - the site name (weblogs.asp.net explains everything), all posts are "ON TOPIC" and informative, while generic .NET bloggers should go to other site, like codebetter, dotnetjunkies or somewhere else.
I'm with you Bill Simser. I too don't want to abandone my old posts and especially the massive amount of links (sorry if that sounds arrogant) to these posts (at least some of them). Moving that content is 1, but making sure people who're looking through google for those posts will end up on my new place is likely to be a bigger problem.
Peter: my blog was already on this server when it was still dotnetweblogs. I never favored the move to weblogs.asp.net, nor do I favor the way it is going now that we 'just have to move'. I just can't move that easily: my old posts are still read a lot and I don't want people to find a 404 and think the post is gone while it's somewhere else.
I also don't like your tone, you have to realize a lot of the bloggers here were already here before the whole site became weblogs.asp.net. They have written a lot of content which is linked to by a massive amount of sites. Simply telling them 'to move' is IMHO very harsh and is likely not going to be met with lots of cheers and joys.
I thought that it was for .Net in general and that the domain name was because it was implemented with/using asp.net.
Are all the blogs on blogger.com suppoed to be about blogging?
I'm not a prolific blogger and I don't mind the plain look so I'm not to concerned about the improvements. Whoever is paying for it has the say on these things. Putting paying clients first makes sense, but if a non-paying client is maintained for marketing and visibilty reasons, then it isn't really a non-paying client.
That said, it does seem to me that this is becoming annother community thing started by MS that was doing very well up to a certain point, then stuff happens and the community starts to come appart.
Ok, assume you guys can maintain posting in this http://*.asp.net site with anything related to .NET, and how about the "engine"? Is SubText and DasBlog a better choice? I can introduce a professional (commerical) team in maintaining this site. Democratic?