Oxite: What are you going to do with it? [closed]

问题:

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.

Closed 7 years ago.

Microsoft released the source for Oxite, their blogging engine that's intended to help .NET developers learn ASP.NET MVC. They also released the source for the Mix site, which was built with Oxite.

Microsoft says that developers can build applications with Oxite, since it has a lot of built-in features like trackbacks, pingbacks, and RSS support.

Are you going to use Oxite to learn ASP.NET MVC? Do you think you could do anything useful with it?

回答1:

I would stay away from it. It's a very bad example. I don't understand why microsoft put it on internet. First of all the security reasons, but the code is very hard to read for new developers. I use asp.net mvc since preview 2, but it's still very difficult to read that code because it's bad. Many better examples are found or used here on stack overflow. Personally I suggest watching the screencasts on Rob Connery's website or on Autumnofagile

Karl Seguin took the time to sum it all up

Rob Connery works for Microsoft and doesn't like it either

A new word is named after it: Oxitis

回答2:

I would highly recommend staying clear of Oxite as an example of how to write an ASP.NET MVC application. In it's current form, it's fundamentally flawed and will do more damage than good.

回答3:

First off, Oxite in it's current form is a Blog Engine, not a CMS. You can add pages, but that is hardly a CMS. Secondly, I'm going to wait and see what happens this week now that Rob Conery is doing some severe refactoring on it. Refactoring that was sorely needed. I think with his input and the continued effort of the team, it will get over the initial problems that many have had with it. So I think I will probably adopt it as my blogging platform and hopefully integrate it with my CMS.

回答4:

I hadn't seen this before. Looks interesting.

What are you going to do with it?

If someone wants me to write a CMS and specifies that I must use .NET, then I'll look at oxite as a possible alternative to things like DotNetNuke. I don't know anything about either of them though :-)

回答5:

I downloaded the source, but I don't think I can do anything with it until Rob refactors it.

回答6:

I'm curious if there's been any movement in the opinion on this app? I might like to give it a whirl, although I'd also want to look at it as a model (so to speak) for doing MVC development with ASP.Net MVC. If this is not a good example of code to follow, does anyone have suggestions for alternative applications that are relatively feature-ful and employ good coding practice, using the ASP.Net MVC stack? Thanks.

回答7:

I read at the Mix website that the Oxite source code is "componentized" enough such that WebForms developers can take advantage of it too. Since I'm not ready to go with ASP.NET MVC for my projects yet, Oxite might be a good way for me to figure out how to transition from a WebForms app to an ASP.NET MVC app.