Saturday, November 01, 2008
NOTE: In this series I build a blogengine using ASP.NET MVC and jQuery from scratch in order to learn more about these new technologies. If you haven't read the first post in this series, I would encourage you do to that first, or check out the jBlogMvc category. You can also always subscribe to the feeds.
jBlogMvc is converted to be used on ASP.NET MVC Beta 1 if you haven't downloaded it yet you can find it here, to read about the changes and additions in the beta 1 I do recommend reading ScottGu's asp net mvc beta1 announcement if you haven't already read it.
This part had witnessed a big change in project structure hence the new release of the beta1 and building a themable folder structure as shown in the pic.
Continue this article here.
Thursday, October 09, 2008
NOTE: In this series I build a blogengine using ASP.NET MVC and jQuery from scratch in order to learn more about these new technologies. If you haven't read the first post in this series, I would encourage you do to that first, or check out the jBlogMvc category. You can also always subscribe to the feeds.
What about new features this part will cover :
- Configuration is saved in the database.
- Managing Posts (Editing, Deleting).
- Posts are now paged.
- Some jquery magic is used.
So, lets have a tour in the project one more time.
Read the complete article here.
Monday, October 06, 2008
NOTE: In this series I build a blogengine using ASP.NET MVC and jQuery from scratch in order to learn more about these new technologies. If you haven't read the first post in this series, I would encourage you do to that first, or check out the jBlogMvc category. You can also always subscribe to the feeds.
In this part of the series, I build the administration area of the blog engine I am building using the ASP.NET MVC and jQuery, in this part I will cover more basic features used in any blog engine, so lets get started.
What will part 1 cover ?
Basically it will cover how to build an administration area, I chose the wordpress blog engine and tried to clone its structure and some look and feel of it, the operations I will implement in this part will be :
- Visitor
- Login -- I will just reuse the code available with the default project template for membership stuff.
- Admin
The stuff I collected and used all over the net from blogs and used in this part can be summarized in the following,
- Using membership for validation
- Using the Authorize attribute
- Using Model Binders
- jQuery Client validation
- Small validation framework for business rules and server side validation.(originally written by scott gu)
- Using nested master pages in ASP.NET MVC
- Applying the "Post/Redirect/Get" (aka PRG) pattern.
- Applying some css to make it look nice (based on wordpress blogengine admin layout)
Read the full article here
Saturday, August 18, 2007
At SCS we are approaching the final phase of Maisonette so I had the task of developing the setup project after looking at many alternatives we picked WiX toolset to be tool we develop our msi files with.
Here in this blog I willl try to share all the problems we faced in developing the setup.
see u soon.
Thursday, July 26, 2007
While having my first steps towards learning
WiX v.3, The first step was to read some of the tutorials over
here, then after downloading the samples I started exploring them to learn more. In my very first sample (named SampleWebDir) almost the simplest one although I had some troubles because the samples were built using the WiX v2 while I am trying to build it using v3. Simple changes had to be done inorder to make it built:
- Change the Wix Schema from
xmlns='http://schemas.microsoft.com/wix/2003/01/wi'
to xmlns='http://schemas.microsoft.com/wix/2006/wi'
- Add Reference to the WixIIsExtension dll
- Now inlcude the IIS namespace within the wxs file to be as :
<wix xmlns="http://schemas.microsoft.com/wix/2006/wi" xmlns:iis="http://schemas.microsoft.com/wix/IIsExtension">
- Prefix the web elements with the iis: to be like this
<iis:WebVirtualDir>
<iis:WebApplication>
<iis:WebSite>
<iis:WebAddress>
- To remove warnings:
- Add an Upgrade Code to the Product element
- Remove the LongName key/value in the File Element is now depreacted.
- Remove the Package Id is has been deprecated.
- To remove all the localization errors put assigned a culture to the project (right click the project node)>>(Properties)>>(Linker tab)>>(put the Culture as: en-US)for example.
Note:The steps up there are when using votive on visual studio and were tested on windows vista running iis7.