Code Simplified – Viral Sarvaiya

Code Simplified – Viral Sarvaiya, Web Developer Friends, dot net Developer, Sql Server Developer

Archive for June, 2010

Text to speech in with C#

Posted by Viral Sarvaiya on June 16, 2010

here i demonstrate the text to Speech conversion…

step 1 : create new web site.

step 2 :  in the default.aspx page, copy the following code…

<html xmlns="">
<head runat="server">
 <title>Text to speach</title>
 <form id="form1" runat="server">
 <asp:TextBox ID="txtspeach" runat="server"></asp:TextBox>
 <br />
 <asp:Button ID="btn1" runat="server" Text="Speach" onclick="btn1_Click" />

Step 3: Right click on the solution explore of the visual studio and add reference

in the add reference dialog box select the COM tag and add “Microsoft Speech Object library” and click to ok.

Step 4 : In the Default.aspx.cs file, copy the following code……

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using SpeechLib;
using System.Threading;

public partial class _Default : System.Web.UI.Page
 protected void btn1_Click(object sender, EventArgs e)
 SpVoice objspeach = new SpVoice();
 objspeach.Speak(txtspeach.Text.Trim(), SpeechVoiceSpeakFlags.SVSFDefault);

Step 5 : Run the code…

enter the text which u want to speech and then click to button, and listen the text…..


for more details : click here


Posted in ASP.NET | Tagged: , , , | 16 Comments »

Animation in Silverlight

Posted by Viral Sarvaiya on June 16, 2010

Table of Contents

  1. Overview
  2. Introduction to Silverlight Animations
  3. What is Silverlight Animation?
  4. What is the namespace used in Silverlight Animations?
  5. Timeline
  6. What are the Types of Animations in Silverlight?
  7. Define Animation types
  8. What is Storyboard?
  9. Storyboard Properties
  10. Storyboard Methods
  11. How to implement the Animation?
  12. What are the important properties/Methods used in the Animation?
    1. Duration
    2. BeginTime
    3. AutoReverse
    4. RepeatBehavior
    5. FillBehavior
    6. SpeedRatio
  13. How to trigger the Storyboard Begin event with XAML?
  14. Example of ColorAnimation
  15. Example of DoubleAnimation
  16. Example of PointAnimation
  17. Example of Animation with Code behind
  18. Animation in XAML versus Animation in Code
  19. Start, Stop, Pause, and Resume an Animation
  20. Conclusion
  21. History

For More Details click here.

Posted in ASP.NET | Tagged: , | 1 Comment »

Security for WCF RIA Services

Posted by Viral Sarvaiya on June 11, 2010

The following checklist is a starting point for ensuring secure usage of a domain service.

  1. Minimize the data and operations exposed by a domain service. This is the first line of defense against information disclosure and denial of service.
    1. Expose only those entities that are needed by the client. This approach may require that you separate server logic and validation from client logic and validation, if it enables you to reduce the number exposed entities. For example, an expense report application that does not need the Employee entity on the client should not expose it through a domain service.
    2. Shape entities to avoid exposing sensitive data. You can use the ExcludeAttribute attribute or presentation model to reduce the data that is available to a client. For example, if birth date and Social Security number are not required in an application, exclude them from the shape that is visible to the client.
    3. Require query methods to take parameters that are needed in your application, instead of relying on data filtering capabilities in LINQ. For example, if expense reports are shown for a given employee, you should require an employee ID as a parameter in the query method and you should not provide a method that gets all expense reports. This approach minimizes the potential of data harvesting for all employees.
    4. Create query methods that provide only the data needed for specific scenarios in your application. This approach means that you might provide multiple query methods that return portions of the data instead of a single query method that returns all of the data. For example, if products are shown by category or supplier, you can provide two methods that accept category or supplier information, instead of a single method that returns all of the products.
    5. Filter data to provide only the data normally required for your application. For example, you might have a query method that returns only orders that were fulfilled in the past year.
    6. Restrict the number of results that can be returned from a query to minimize accidental or deliberate overloading of the server. You use the ResultLimit property on the QueryAttribute to throttle the numbers of results that can be returned. For example, if a large number of products can be returned, enforce paging on the client by throttling the results to 20. Also, consider using the OutputCacheAttribute attribute for output caching to reduce the load on the middle tier and database.
    7. Minimize the number of operations for each exposed entity. For example, if an order application only needs to add or modify orders, you should expose query, insert, and update operations on the orders entity, but not delete operations. In addition, you should expose only query operations for the products entity but not any data modification operations.
    8. Whenever possible, use named update methods that restrict which members can be updated.
  2. Restrict data and operation access to authenticated users and users in specific roles.
    1. Avoid anonymous access whenever possible by using the RequiresAuthenticationAttribute attribute. When you must allow anonymous access, limit it to the smallest set of domain services and the smallest subset of operations within those domain services.
    2. Add the operation-specific RequiresRoleAttribute attribute whenever possible. Consider each operation separately in a domain service. For example, all users may need to query the products entity, but only users in the administrator role need to update it.
    3. Consider using the AuthorizationContext property to provide a customized authorization model.
    4. Treat any data sent by a client as suspicious. A malicious client (even one that is authenticated and authorized) can provide tampered values for current and original values in a change set. Your application logic should not assume that these values are trustworthy. Instead, consider potential threats from tampered original values.
  3. Use the https protocol for Forms authentication. Sending passwords in clear text is a significant vulnerability, but it can be mitigated by using https.
  4. Expose the minimum number of endpoints. By default, RIA Services creates a binary endpoint for a domain service. Add additional endpoints only if you have clients that specifically need the endpoints. Disable any endpoints that are not in use.

For More Details :

Posted in RIA WCF | Tagged: , , , , , , , , | Leave a Comment »

WCF RIA Services

Posted by Viral Sarvaiya on June 11, 2010

WCF RIA Services simplifies the development of n-tier solutions for Rich Internet Applications (RIA), such as Silverlight applications. A common problem when developing an n-tier RIA solution is coordinating application logic between the middle tier and the presentation tier. To create the best user experience, you want your RIA client to be aware of the application logic that resides on the server, but you do not want to develop and maintain the application logic on both the presentation tier and the middle tier. RIA Services solves this problem by providing framework components, tools, and services that make the application logic on the server available to the RIA client without requiring you to manually duplicate that programming logic. You can create a RIA client that is aware of business rules and know that the client is automatically updated with latest middle tier logic every time that the solution is re-compiled.

The following illustration shows a simplified version of an n-tier application. RIA Services focuses on the box between the presentation tier and the data access layer (DAL) to facilitate n-tier development with a RIA Services client.

RIA Services n-tier applicationRIA Services adds tools to Visual Studio that enable linking client and server projects in a single solution and generating code for the client project from the middle-tier code. The framework components support prescriptive patterns for writing application logic so that it can be reused on the presentation tier. Services for common scenarios, such as authentication and user settings management, are provided to reduce development time.

For More Details :

Posted in RIA WCF | Tagged: , , , , , | 1 Comment »

OData Basics – At the AZGroups “Day of .NET” with ScottGu

Posted by Viral Sarvaiya on June 10, 2010

Posted in ASP.NET | Leave a Comment »

%d bloggers like this: