well, for those that have been emailing, i hope you stayed subscribed. feedreader has finally found a home and the complete source code is available.
as i’m sure most of you have reflected the code ;-) you’ll know it isn’t brain surgery, but that there are probably some things that could be cleaned up and we know there are areas that need to be fixed.
so visit the feedreader codeplex today and get the source released under the creative commons attribution-sharealike 2.5 license.
remember, the purpose of open source is to share :-D, so be sure to contribute back your fixes and log issues as well!
i’ve updated the origami skin for subtext…although gotdotnet is having some problems and i can’t upload it just right now.
- fixed css for safari, opera and ie6
- removed the need for modifying the DTP.aspx body element
- fixed the cookie preservation of the user personalization areas
- fixed the css images references
there are still a few config things that you have to do for your config that will be outlined in the README file.
there are still some things i’m working on and one thing that i had (google ad support) was screwing up some of the css config…but i’ll let everyone else figure out their own config for stuff like that.
are you running windows vista beta 2 or later? i am. more about that some other time and my frustrations as a developer workstation!
at any result, one of the problems i’ve been having is getting use to the user access control features (basically run as a least privelege user). i couldn’t take it anymore and made myself an administrator. guess what, still didn’t help, imo (again, more about that when i have time to document the scenarios fully — after all, i’m giving the team a chance…it is beta ;-)).
well, some of the MSI packages (namely the web application project msi) distributed from the asp.net team will fail when installing on vista even if you are an admin. why? seriously, i’m trying to understand that myself. but nonetheless, i know *where* they are failing — and it is essentially in some areas of installers and log files…minor, but important seeing how any failure in the process of the msi setup will rollback the setup!!!
so, in order to get around it, do this:
- run a command prompt in elevated mode (right click on command prompt and choose run as administrator)…yeah, i know even if you are an administrator
- in a command prompt use msiexec to start the install..like this:
msiexec /i <path-to-msi-package>
i’ve found that worked without error for me…good luck!