Skip to main content

Applying Themes for Silverlight 4

ටික දවසකට පස්සේ ලියන්න හොඳ දෙයක් එක්ක වෙලාවක් හම්බ උනා. මේ දවස් වල මම පොඩි අත්හදා බැලීමක් කරනවා Silverlight 4 එක්ක. Visual Studio 2010 තමා පාවිච්චි කරන්නේ. හැබැයි එක හිතපු තරම් ලේසි උනේ නෑ. ඒ නිසා මම හිතුවා ඒ ගැන පොඩ්ඩක් ලියන්න.

මුලින්ම කියන්න තියෙන්නේ Silverlight 4 එක්ක වැඩ කරන්න නම් VS 2010 විතරක් තිබුනට මදි, ඒකට ඔයාලට ඕනෙ වෙනවා VS2010 Service Pack 1. ඒක download කරගන්න පුළුවන් මෙන්න මේ ලින්ක් එකෙන්. මෙතන ඇත්තටම තියෙන්නේ ISO image එකක්, ඒක mount කරලා install කළා නම් වැඩේ ගොඩ.

ඊට පස්සේ අපි බලමු කොහෙන්ද මේ Themes හොයාගන්න පුළුවන් කියල. ඒකට යන්න මෙන්න මේ ලින්ක් ඒකට, එතන තියෙන "SL4Themes-templates.zip" කියන file එක download කරගන්න. මේ themes Microsoft එකෙන් officially release කරලා තියෙන themes වගයක්. ඇත්තටම මේ download එකේ තියෙන්නේ Project Templates. දැන් කරන්න තියෙන්නේ මේක Unzip කරලා VisualStudio2010 කියන folder එක ඇතුලේ තියෙන JetPack.vsix වගේ file එකක් double click කරන එක. එකෙන් පොඩි Installer එකක් දුවලා install වෙනවා Visual Studion Project Template එකක්.

දැන් කරන්න තියෙන්නේ VS 2010 open කරලා New Project එකක් හදන එක, එකේ අලුත් Templates install වෙලා තියෙනවා පේනවා මෙන්න මේ වගේ.


දැන් තියෙන්නේ, ඒ අලුත් Template එකක් පාවිච්චි කරලා project එකක් හදාගන්න. එතකොට ඒ project එකට අපි තෝරගත්ත Theme එක apply වෙනවා. කරලා බලන්න හරිම ලේසි හරිම ලස්සනයි.

Comments

  1. you knw how to see ubuntu source code?

    ReplyDelete
  2. Hmm, I just did a quick google search and found out several interesting links.
    http://ubuntuforums.org/archive/index.php/t-14756.html
    https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2009-May/008045.html
    Visit above links and check, they have even posted an archive url.
    If you still not satisfied you may ask this in an Ubuntu forum. People there might give you a complete answer.

    ReplyDelete
  3. Thanks! great work!

    ReplyDelete

Post a Comment

Popular posts from this blog

Adding Unique Constraints with Entity Framework Code First

Entity Framework Code First is a great way to define and maintain your database within your application it self. While it poses a nice set of complementing libraries like Data Annotations and Fluent Configurations which helps you specially in defining phase of your database, it would give you a headache if you try to define a unique constraint on a column. For example in the users table of your application you could probably have an int ID column which would serve as the primary key and you might need to make your Username column a unique one. Since you are using EF Code First you will soon find out there is no direct way to accomplish this requirement. Unfortunately fluent configurations doesn't have syntax like HasUnique(u => u.Username); I asked the same question in stackoverflow , but didn't get a convincing answer. Since there is no direct support from EF for this you could take one of following alternatives to achieve it. Approach 1 :  ...

The list of do's and don'ts when preparing your resume

During past couple of years many times I was asked by my colleagues in the HR department "Could you please shortlist these resumes for interviews?" answer was almost always yes. As a result I have gone through a large number of resumes to check whether if these people are suitable for an interview.  While I'm scanning these resumes I found many reasons that I could reject these let alone the technical incompetencies of the candidates. Then suddenly one day I said to myself "why don't you write simple blog post about this?". So here I'm trying to put up a list of reasons that your resume might get rejected and how to minimize it. When you read this you will realize how trivial some mistakes are but they could surely cost your chance of landing your dream job. Typos in the resume Well I hate typos because it shows you how inconsiderate you are, keep in mind your resume is the first contact point with your potential employer so why don't ...

Building Highly Scalable Web Applications with Windows Azure

Among many other benefits of moving or building your web applications in cloud, for me I think the most important benefit we get is scalability. When it comes to web applications there are two approaches for scalability. Scale out - This means we increase the number of running instances of the application with a load balancer which distributes the requests among those instances Scale up - This means we increase the physical resources on a single application instance, for example we can increase the RAM of the hosted machine In reality preferred way of web application scalability should be to scale out. Because there are obvious hardware limitations in scale up approach. Bearing that in mind if we look at what Windows Azure provides out of the box, for a certain level it supports scale up approach and it has a great amount of support for scale out approach. Scaling your application out Windows Azure supports both automatic and manual scale out of the ap...