> heh. dannytuppeny and theJazzyBrain, you two are funny! It cracks me up when people think *ALPHA* software should be working smooth and perfect out of the box.
It cracks me up that you think it makes sense for every single developer that downloads Oxite to spend the same hour troubleshooting the same problems because they were too lazy to include the assemblies. That's not a waste of time at all, no? Not only are
the DLLs not included, but one of those referenced in the web.config is *NOT* the version you can even download (same version number, different public key) so you need to start changing web.config. Nice one!
> It's good you two are giving up, because clearly you're not the sort who is up dealing with alpha software in the first place and therefore would likely not have given much in the way of constructive criticism anyway.
That's funny, I see plenty of constructive criticism above. I posted a suggested solution to the fact it took me an hour to get up and running, and even included a few bugs. I could have said "this is shit, it doesn't work" but not only did I spend
time coming back here to post, but also explained, in detail, the issues I had. People like you make me wish I hadn't bothered.
> If you've ever tried installing alpha software before, and based on what's been posted here, the two of you have not
No surprise, you're wrong. I'm a software developer and I use alpha software on a daily basis. I also worked on a team building an application against early private builds of .NET 2.0 during its development which was used as a Microsoft case study for
the .NET 2.0 launch.
> you'd know that, unless it's fairly simplistic software and/or is wholly based on some standard framework (and it should be clear that, given your experience, Oxite
> uses more than the standard .NET components), you'll have to do some manual setup on your environment before you can effectively build/run it.
"Some" I can live with. Oxite requires *far* too much effort to run in any form. Not only did I have to download and *build* other components, I had to *install* things on my system. For software that's not complete and could change these dependencies
at any time, it's just not acceptable. If I was installing some mammoth application, maybe I'd think about it. This is a simple ASP.NET web application. .Net has been designed very well so you can deploy an app with all external libraries in the same
folder and have it work. There is no excuse for such a simple app to require such a lengthy setup.
> That's the way it is guys, so if you're not up to dealing with that, fine -- but don't come complaining about it... Just go away and play with you Macs (heh heh) until Oxite is nicely packaged, then you can go download, built and start doing...
whatever *waves hands vaguely*
It's idiots like you that put lots of people off open source projects. Yes, I moaned. But I did so because I was so shocked at the effort involved in getting an ASP.NET web application running to demo. This is not 1995. I gave full details of ll my problems.
I even went back after the original post to finish it off and provide more feedback. I could've just left it, but I liked the idea, and hoped maybe the developers would care enough to read my comments and either address the issues or share the reasons not
to. I wasn't expecting some arse to come and tell me I'm not good enough to use alpha software.
TLDR Version: If the developers of Oxite want people to play around with it and submit feedback, they need to make it easy to download and run. They also need to stop idiots like Carnix scaring off people that are doing your QA for free :-)