Jonel Rienton's Blog

I have been evaluating Microsoft's TFS (service) for almost a couple of months now. It allows you to host your solution in the cloud with lets you add up to 5 users. Build is currently in preview and will be included in the Free Plan on a limited basis.

Go to https://tfs.visualstudio.com to check it out.

In the earlier post I did related to this topic, I have talked about using Json.Net to consume the result of Sitecore Item Web API. In that post, I have used the keyword dynamic to express my intention of consuming the returned json of the API.

Sitecore recently released it’s Item Web API product and I think it will be good for the community to see some sample application. I plan a to do a 3 series blog iteration in the coming weeks, this, being the first one.

It's been almost a year since I've been Sitecore certified and I've learned so much by reading documentations, reviewing existing code, reading best in class blogs and gathering peers recommendations. In my initial months with Sitecore, I found out about the log viewer which basically allows us to view the current and previous logs of Sitecore. Pretty handy if you are troubleshooting some issues or using the logs to see what's happening with your application/website.  One of the drawbacks I noticed right away is I have to refresh the log every time to see the latest additions.

 I've recently hit a snag while using Sitecore's fast query. To begin with, I first noticed the issue when one of my colleagues reported that the upload application we have recently developed is not working. The upload application is supposed to add children to items that already existed. It turns out that the issue was the fast query I have written was not finding the parent item those children are supposed to be loaded under.

I have been tinkering with LINQ for quite a bit now and I came across a trivial question about how does LINQ return an entity. I'm going to start off by sharing you a very simple example just to illustrate.  To begin, I'll create a Contact table:

Today I have been to a Microsoft event. The presenter talked about ASP.Net security, Visual Studio.Net 2008 and a few tips on how to secure your web applications. One thing I like about this kind of events is there's always hidden gold that you can walk with. One that stands out is when the presenter talked about ViewStateUserKey.  To avoid malicious user from using your ViewState value for XSS kind of attacks, setting the ViewStateUserKey in the Page_Init event of the Page will alleviate this.