oxite-微软开源博客引擎
该博客引擎的主要目标:
1. 提供撰写博客引擎的一个可重用范例，包括一些基本功能和高级功能（trackbacks, rss, comments, etc）。
2. 提供现实场景下的一个非常简单的ASP.NET MVC范例， 便于学习设计和编码MVC架构。
Oxite在Codeplex主页：http://www.codeplex.com/oxite
源代码下载： http://www.codeplex.com/oxite/SourceControl/DownloadSourceCode.aspx?changeSetId=26899
Getting Started with Oxite （摘自codeplex）
It is pretty easy to get up and running with Oxite, and we'll document the steps required right here.
System Requirements
You can run Oxite on any version of Windows XP, Server 2003, Vista or Server 2008 (32 or 64-bit)
There are three pieces of software you need to get started:
- Some version of Visual Studio or Visual Web Developer Express (VWD Express),
- ASP.NET MVC, and
- SQL Express 2005 or 2008
If you have Visual Studio or Visual Web Developer Express already installed, then you can skip ahead to 'Web Platform Installer', otherwise lets go ahead and get VWD Express installed.
Install Visual Web Developer Express (VWD Express)
Open up the VWD Express download page (right-click and pick open in a new window or tab so you can easily get back to these instructions).
In the purple box on the page labeled Visual Web Developer 2008 Express Edition, select the appropriate language and then click on the 'Download' link next to your language choice.
A dialog will pop up asking what you want to do with the file vwdexpress.exe (IE7 and Firefox 3.x dialogs shown, you may get a different experience)
(IE7) (Firefox)
You can run the file directly from IE (after a warning prompt since you are about to run a file from the internet), or save the file to disk and then run it in Firefox. Either way, you should end up running the VWD Express installation. After the usual license agreement step, you'll be given a choice of installing SQL Server Express 2008 at this point as well. Go for it, we'll need it installed to run Oxite anyway.
Click next and you'll get to see a list of what will be installed, select a location for VWD Express and see the drive space requirements.
From here, click Install and it will run through the installation of everything it needs. It may need a restart when it is close to finishing, but it will continue after the restart is completed. When the installation is completely finished, will finish by requesting a restart, which you should do before we move onto the next step.
Installing MVC
Oxite requires the Beta of ASP.NET MVC, which you can install from the MVC Beta download page
Scroll down the page until you see the two files available for download and click on the 'Download' button next to the 1.4 MB .msi file
Click Run and accept the warning in IE, or save it to disk and run it in Firefox. Follow the prompts all the way through the install.
It is important that we are doing this step after the installation of VWD Express, as the MVC Beta does some configuration of templates and features that the VWD Express product needs to be able to run MVC projects.
Download an Oxite Release or the Oxite source
Now it is time to grab a recent release or the most current drop of the source.
Release or Source Code checkin: Which one to get?
In general you should get the most recent release, as that is a drop of the code that we explicitly chose to package up for people to download. Individual source code checkins are more up-to-date and may contain bug fixes since a release was created, but they may also contain new bugs that just haven't been found yet. Downloading from the source code tab also brings down more files that you need, because it brings down a full copy of everything we have checked into this codeplex project. Having said that, you can look down the list of checkins to see if there is any important functionality or changes that have been done since the last release, and then make your own decision about what to download.
Regardless of what type of source you choose, you end up pulling down a .zip file full of code, images, binaries, etc... unzip that file into a folder where you have read/write access. To avoid any security access issues, I would stick with a folder that is under your user directory (a folder on the desktop or in your 'Documents' folder for example).
Open up the new directory full of files when you've extracted them. If you've downloaded a release, then the top level folders within this new folder will be the various projects that make up the Oxite sample, including /Oxite.Database, /bin, /Oxite.SearchProvider and others. This is the root of the Oxite solution. If you've downloaded a full source code check-in, then the top-level folder will contain /Archive and /Oxite, and the root of the solution will be under the /Oxite folder. Remember the path to that root folder, you'll need it in a minute.
Open and Run Oxite!
Open up Visual Web Developer and do any initial configuration it prompts you to, until you get to the 'Start Page'. Now click the File menu and select 'Open Project...', browse to the root of the solution wherever you extracted it to, and select the Oxite.VWDExpress.sln file.
Note: if you are using VWD Express, then use the Oxite.VWDExpress.sln solution. The other solution contains the same basic code, but also has the database and test projects, neither of which are supported by Visual Studio Web Express.
Click Open to open the solution. You may be prompted that this is not a trusted location, if you aren't opening the code from your own documents folder, and you may be prompted with 'the source code provider for this solution can not be found'. In the first situation, you can click OK to ignore if it is running in a place where you have read/write permission and in the second case you can select 'Yes' to permanently remove the source code control bindings from the project. Once you have the project open, go over to the 'Solution Explorer' on the right hand side of the VWD Express window and find the project named 'OxiteSite' in the list of projects (it should have a globe as an icon), right-click on it and choose 'Set as Startup'.
Now you should be all set, so just click on the little green 'play' button on the toolbar of VWD Express or press the F5 key on your keyboard... if everything works as expected, you should have a browser window open in a few moments with the sample data's first post 'World.Hello()' up and visible.