British Inside

I like a clean output window when I'm building in Visual Studio; I fix warnings so that all I see in the window is a bunch of "0 errors, 0 warnings". So Visual Studio 2005 gave me some work to do. Although I've been using 2005 for a month or so for building a 2.0 version of the Community Server MSI, I've only just started ...

Community Server 2.1 RC1 is up there for download. Obviously it's the best release yet and it's I'm now officially an enthusiast. Yeah, I've worked at Telligent for almost a year now but only recently full-time on the CS team. It's a great team, but getting my new blog site setup on CS has finally got me involved in the ...

Well, I got my CS site up and working - on my local machine. :D And then, my FTP program decided to have a very immature and badly-timed hissy fit. It took an hour to upload the files, often quoting 4bytes/sec upload speed. Yes BYTES. It started moaning about files not being uploaded correctly that had spaces in the name. And then at about 11pm ...

..and within 15 minutes (how is that possible?) the ringtone spam comments poured into my blog. So, this is it. This is the weekend that CYA moves to CS. It's not hard, thousands of people do this each day but the longer I leave it the bigger hurdle it appears. I'm just going to install it, set it to single blog mode and pick a theme. It ain't ...

"Dozing Dogs has an installation program, right?" I should have looked innocent and said that I'd really love to have one but I hadn't gotten around to it. But I didn't, so my Community Server coding recently is inside MSI and the associated configuration wizard exe. But, hell, coding is fun even in there. Even when ...

ok, so I just installed CS on my locahost using the MSI and followed the same advice that I used to give Dozing Dogs customers; namely, install on localhost but use your production (hosting company's) SQL Server if possible. Doing this means that you won't have to move the db, just the web site. I decided to install into the existing ...