.NET Blog - Chris Frazier Style

I'm putting some of the finishing touches on my first winforms project, so I decided to try out some code on an app that I wrote over a year ago today - I wanted it to run on .netfx 1.1 instead of 1.0, because it's the central login point for 2 different apps. After looking around at things and jogging that old memory, I got it working again, in both 1.0 and 1.1 using Denis Bauer's ASP.NET version switcher. Very nice. I know it's been said before, but this is an indespensible tool for anyone running side by side asp.net apps.

My problem was this (if you're still reading): Since I have two different apps accessing the login page of this site from different hosts, the machineKey element of the *.config files need to be synched up for each site - either in web. or machine. - much like a server farm scenario. Apparently, tho, the newer fx and the older fx don't play nicely together when it comes to communication. Even tho the two apps had identical machineKey elements, authorization failed from site B to site A every time. All I had to do was change the versions that the apps were running on to be synched, and voila! Single Sign On is back. Whew

It seems that cross-posting has become a cool feature since other, more respected developers have released new versions of their prospective blogging engines.

This is a cross-post. You can view this post here and there. I've been doing it for a while - ever since I got my grubby little hands on someone's blog engine code and was able to play with the source code / webservice combinations that http://weblogs.asp.net exposes. I'm doing it. I know of one other person who's doing it as well.

Anyways, it required a minimal amount of code to achieve - although I'm guessing there is probably a better way to do it, like w/ the MetablogAPI implementation. It's just a webservice call, and I'm able to post technical stuff right up next to non-technical stuff.

Okay, I'll be quiet now.

P.S. One more thing - Thanks to everybody who's blogging the PDC. It's neat to read about what's going on in real-time.

Jeff Julian has put up a couple of skins at http://www.geekswithblogs.com/TextSkins .

Go to the Admin section of your blog, and in the “Custom CSS Selectors” textbox add:

main {
margin-left:200px;
padding:0px 20px 0px 0px;
width: 580px;
}

It still has a bit of gap-osis, but at least your main content will end up where it does for IE. I haven't tried this out on Opera yet, but I've implemented it here and there.

HAND

Thanks, Scott.

So I've posted a few times about cross-posting from my blog to my other blog, since my other blog gets about 300% of the traffic of my blog (translation : me + 2 people, and I'm not sure about one of them anymore). I've been using a 'simple blog service' to do this with a little checkbox on my blog. Well, it doesn't look like it's working anymore.

I hope I'm jumping to conclusions, because I put my blog in debug mode and wrote out a trace statement to confirm that this was the post I made:

Remote Post Inserted with ID : 31937

but, a quick look at the numbers that are generated in the main feed reveals that the post made before this one was 31935, before that one was 31927, and after was 31943. What gives? I know you can have published/nonpublished - but this is a lot of space between numbers - are we only gonna see every 8th post from now on?

Please - somebody put my cross-postin' mind at ease :)

I just worked out a slightly bastardized version of Julien's Lighty for my other blog.

I don't think it looks quite as good as the other one, but it's a start I guess...Maybe I'm using the wrong Custom skin (marvin2.css) This is fun to play with!

I added a scroller over here - just some custom javascript. I wanted to get it working - it looks great on IE, I can't say the exact same for mozilla or opera, tho. I'm working on it. I'm also working on giving it a cleaner UI w/ images instead of text - this is just the 'prototype' to see if I can get this scroller working.

update: I took it off. It was an okay idea, but everything looked funky in other browsers, plus the scroll up/scroll down text didn't jibe w/ the rest of the site. Maybe next time.