Thursday, July 02, 2009
Just put the first version of my SL navigator that uses a Coverflow to show that list of PDFs and notes that I have submitted to my blog. Also makes heavy use of the Vectorlight Richtext control (thanks). It requires SL 3 but should be out in few weeks. check it out
Wednesday, June 24, 2009
VectorLight Controls for Silverlight
vectorlight offers an amazing array of high quality controls. I have been using the their RichText and am very impressed especailly since the price is right, free for now. It makes me wonder why anyone would pay the extra for Telerik or ComponentOne. Many of their controls are in the Toolkit or are available free.
Monday, June 22, 2009
silverlight Coverflow
Just found a great Coverflow for Silverlight that can be used royality free,the demo is very cool, so click here
Wednesday, June 10, 2009
Monday, June 08, 2009
RIA Data services
I have been playing around with RIA Data Services for a while and must say this is pretty cool stuff as it makes writting multi-tier apps so easy. I am writing a series of articles :
1. Introduction to RIA Data services that you download the PDF here
or code
1. Introduction to RIA Data services that you download the PDF here
or code
Labels: RIA Data services silverlight
Tuesday, June 02, 2009
Silverlight Host Page QueryString
One of the things you will want to do at some point is get access to the query string parameters passed to the page hosting your Silverlight application.
private void Application_Startup(object sender, StartupEventArgs e)
{
string test;
if (HtmlPage.Document.QueryString.Count > 0)
test = HtmlPage.Document.QueryString["fid"] ;
this.RootVisual = new Page();
}
private void Application_Startup(object sender, StartupEventArgs e)
{
string test;
if (HtmlPage.Document.QueryString.Count > 0)
test = HtmlPage.Document.QueryString["fid"] ;
this.RootVisual = new Page();
}
Thursday, May 28, 2009
WCF Tips
Default Serialization
.NET 3.5 SP1 has introduced a new kink: if you don't decorate your class at all (omit / not add the [DataContract] attribute) then the object becomes "fully" serializable by WCF. All public properties will be automatically included.
so the serialzation of
[DataContract]
class foo
{
[DataMember]
public string test;
}
is the same as as :
class foo
{
public string test;
}
2. Visibility
Similar to service contracts, the visibility of the data members or the data contract itself is of no consequence to WCF. You can include internal types with private data members in the data contract:
[DataContract]
struct Contact
{
[DataMember]
string m_FirstName;
[DataMember]
string m_LastName;
}
3 deserializing event
Since no constructor calls are ever made during deserialization, the deserializing event-handling method is logically your deserialization constructor. It is intended for performing some custom pre-deserialization steps typically in a constructor.
for more details see http://codeidol.com/csharp/wcf/Data-Contracts/Data-Contract-Attributes/
.NET 3.5 SP1 has introduced a new kink: if you don't decorate your class at all (omit / not add the [DataContract] attribute) then the object becomes "fully" serializable by WCF. All public properties will be automatically included.
so the serialzation of
[DataContract]
class foo
{
[DataMember]
public string test;
}
is the same as as :
class foo
{
public string test;
}
2. Visibility
Similar to service contracts, the visibility of the data members or the data contract itself is of no consequence to WCF. You can include internal types with private data members in the data contract:
[DataContract]
struct Contact
{
[DataMember]
string m_FirstName;
[DataMember]
string m_LastName;
}
3 deserializing event
Since no constructor calls are ever made during deserialization, the deserializing event-handling method is logically your deserialization constructor. It is intended for performing some custom pre-deserialization steps typically in a constructor.
for more details see http://codeidol.com/csharp/wcf/Data-Contracts/Data-Contract-Attributes/
