In this short article I'll show you the most interesting way, how to create custom Live Tiles using generated Png images. When creating Live/Pinned Tiles for your Windows Phone application, you have basically two options, how to create them. The easier way is to use just ShellTile object, define static front and back image, strings for the front and back tile and you are done. StandardTileData NewTileData = new StandardTileData
Title = "title",
BackgroundImage = new Uri("", UriKind.Relative),
Count = 0,
One of the best things introduced for developers in SharePoint 2010 was the SPMonitoredScope
, which can be used to trace your application, and to pin down potential bottlenecks. I wrote a post on how to use it way back in 2009 – Improve you SharePoint 2010 applications with monitoring using SPMonitoredScope
. It’s still worth a read and still true for SharePoint 2013. But the SharePoint team has continued to evolve the SPMonitoredScope in SharePoint 2013, with two small but interesting changes.
Note: this post is written for SharePoint 2013 Preview – things can/will be changed up until and after
New constructor with a TraceSeverity option
The SPMonitoredScope in SharePoint 2013 has a new constructor which allows you to specify a TraceSeverity for the scope. Why this TraceSeverity then? By default when entering and exiting a monitored scope this is logged in the ULS logs with the ULS log trace severity Verbose (always used by custom usage in SharePoint 2010). By now specifying a trace severity scope we can control at what level of diagnostics logging this should be visible in the trace logs. You can find the logging level for this in Central Administration > Monitoring > Configure diagnostic logging...(Read whole news on source site)
Tim Leung is a software developer based in the UK. For the past 12 years, he has specialised in enterprise application development using products from the Microsoft technology stack. In particular, he possesses deep knowledge of the Microsoft .NET Framework and SQL Server. He's an active member of the U.K. developer community and helps to run the UK VBUG User Group. Tim is passionate about LightSwitch and rapid application development. He is the co-author of the book 'Pro Visual Studio LightSwitch 2011 Development'
(published by Apress). Last month, Microsoft announced a major new enhancement
RavenDB stores JSON documents. Internally on disk, we actually store the values in BSON format. This works great, but there are occasions where users are storing large documents in RavenDB. In those cases, we have found that compressing those documents can drastically reduce the on-disk size of the documents. Before we go on, we have to explain what this is for. It isn’t actually disk space that we are trying to save, although that is a nice benefit. What we are actually trying to do is reduce the IO cost that we have when loading / saving documents. By compressing
the documents before they hit the disk, we can save in valuable IO time (at the expense of using relatively bountiful CPU time). Reducing the amount of IO we use have a nice impact on performance, and it means that we can put more documents in our page cache without running out of room. And yes, it does reduce the total disk size, but the major thing is the IO cost. Note that we only support compression for documents, not for indexes. The reason for that is quite simple, for indexes, we are doing a lot of random reads, whereas...(Read whole news on source site)
A common complaint that we hear about RavenDB 1.0 is that it depends on Newtonsoft.Json 4.0.8, while many libraries are already using 4.5.7. We already resolved the problem once and for all in the RavenDB 1.2 branch, but that is a few months from going live yet. Therefor, we create a new nuget package: http://nuget.org/packages/RavenDB.Client/1.0.971
This nuget package is the exact same as 960, except that we compiled it against Newtonsoft.Json 4.5.7. Note that this is only supported for the client mode, if you want to run RavenDB Server or RavenDB Embedded, it is still going to require Newtonsoft.Json
4.0.8 in the 1.0 version. The main idea is that you can get to run against RavenDB Server using Newtonsoft.Json 4.5.7 on the client side, which is the most common scenario for RavenDB....(Read whole news on source site)
Troy Hunt: Lessons in website security anti-patterns by Tesco - Troy Hunt discusses a number of security anti-patterns occurring on one fo the largest UK Supermarket Chains website, discussing the security considerations of password storage and looking at a number of other security factors which should be reviewed - useful pointers for everyone.
Transactions in Windows [...]
Almost every application you write needs to expose an user interface that let the user change the configuration. In common desktop applications these settings go under a preferences section, usually available from a menu item, but for sure it is not true for all the applications, so every time you install a new software you have to rely on a manual and search a place where this configuration has been placed.
As for other features, in metro-style application this now goes under a very strict guideline checked as a strong requirement by the certification team. One thing you need to be aware is that the settings contract is used not only to expose user preferences but also is a place where you have to move your licensing terms, about and other things that are not exactly settings, in the common feel of the term.
Hook...(Read whole news on source site)
Microsoft Courses 40003A and 40004A Released In the last few months, I was co-authoring (with Amit Raz
, Erez Harari
, Alon Levi
and Sebastian Pederiva
) two Microsoft learning courses: Course 40003A: Programming Windows 8 Metro Style Apps using HTML5: Early Lab Collection Course 40004A: Programming Windows 8 Metro Style Apps using C#: Early Lab Collection The courses are a three-day instructor-led courses. they provides students with a first look at the features of Metro style app development for Windows 8. They also provides
hands-on opportunities to implement WinRT APIs, to manage the Metro style app lifecycle, and to develop Metro style apps that target multiple device types, screen resolutions and view states. For more details about the courses you can go to: Course 40003A Course 40004A
...(Read whole news on source site)
Hopefully it’s obvious that you probably won’t need to do this very often, but when it’s needed, it’s nice to have available. I thought I’d share this little helper to dynamically create a form, append it to body, and submit it...without AJAX. First I'll show you how I'm converting my view model to a parameter list and a query string. Basically I've created an extension method that loops through properties and checks if it's an IEnumerable or not. If it is, then I loop through the values of that property. Otherwise, I just add the value. This method
does not work with complex types. Typically view models are flat, so this works well most of the time. The ToQueryString method just calls the ToParameterList, adds a ? to the front and then just selects what it needs from the parameter list. public static class ObjectExtensions
public static List> ToParameterList(this object o)
var parameters = new List>();
var properties = o.GetType().GetProperties();
...(Read whole news on source site)