Guy Burstein : .Net Framework 3.5

Building an Occasionally Connected ADO.Net Data Service with “Astoria Offline” Preview

Guy Burstein — Sat, 07 Mar 2009 13:48:51 GMT

Building an Occasionally Connected ADO.Net Data Service with “Astoria Offline” Preview

This is a step by step walkthrough of creating a new ADO.Net Data Service that support offline and synchronization with the recently released “Astoria Offline” alpha preview.

1. Create an ADO.Net Data Service that Allows Synchronization

Create a new standard Web Application project.

Add a new Entity Data Model. This time, make sure you select the [Offline Preview] ADO.Net Data Model template. Also notice that the extension of the file is now .edmxpreview instead of .edmx.

Continue with the wizard to create the data model. When the wizard completes, notice that the project has a new reference to System.Data.Entity.Preview.dll.

Add a new ADO.Net Data Service to the project, but make sure you select the [Offline Preview] ADO.Net Data Service template.

In the “Choose what to publish wizard” select Existing Entity Model. We could have started from this wizard from the beginning and create a new Entity Data Model from here.

Select the Entity Container that is part of the Entity Data Model you created earlier. In my sample it is BankEntities. Also notice the new “Enable Synchronization” checkbox – make sure it is checked.

This adds several things to your project:

1. Several new references were added to the project: Microsoft.Data.Entities.Synchronization is the extension for Sync Services that enables entity Synchronization. System.Data.Services.Preview and System.Data.Services.Client.Preview are the ones that does the magic of Astoria Offline.

2. Two new SQL Scripts were added to the Entity Data Model (notice the Bank.create.sql and the Bank.drop.sql scripts in the image). These contain the DDL statements needed to change the database schema in order to support synchronization.

To actually enable synchronization, you’ll have to run the create script. To do that, open it in Visual Studio, and execute it against your database.

3. The ADO.Net Data Service is added to the project and it is now empty. It is already connected the the entity data model, but right now does not support anything.

Set the access rules to the resources of the data model (in this sample I give full access to all the resources). In addition to that, tell the data service that it supports synchronization. To do that, cast the config object to IDataServiceConfiguration2 interface (new in this preview) and assign true to the AllowSynchronization property.

public class BankDataService : DataService<BankEntities>

  // This method is called only once to initialize service-wide policies.

  public static void InitializeService(IDataServiceConfiguration config)

    config.SetEntitySetAccessRule("*", EntitySetRights.All);

    ((IDataServiceConfiguration2)config).AllowSynchronization = true;

The ADO.Net Data Service is now ready to run. Press F5 to run it and play with the URL in the address bar to navigate through the resources.

2. Create a Occasionally Connected Client Application

Add a standard Windows Forms Application to the solution.

Add a Service Reference to the project and let visual studio discover the data service in your solution. When you add the reference Visual Studio will tell you that this ADO.Net Data Service is offline enabled.

Click Yes to enable offline scenarios in the client application.

A scary dialog should appear and tell you that an error has occurred. You can disregard it by pressing Cancel.

Adding this service reference has added not only the client side proxy for consuming this service, but also a local database with the database schema that matches your model.

Open the Data Sources window (Shift + Alt + D), and add a new data source of type Object. Select one of the object types in your client application that matches the model and click OK.

Drag the list of objects onto your form and let Visual Studio create all the necessary controls for navigating through the data.

Double click the window title to add an event handler to the form’s loaded event. In this event handler we will load the data from the Local Database. Add a new for the context, and in the Load event handler – use it to get the data and bind it to the binding source.

public partial class CustomersForm : Form

  public CustomersForm()

    InitializeComponent();

  BankEntities db;

  private void CustomersForm_Load(object sender, EventArgs e)

    db = new BankEntities();

    var query = from c in db.Customers

                select c;

    this.customersBindingSource.DataSource = query;

In order to support saving changes to the local database – enable the Save button on the Form and double click it to add an event handler. In the handler – simply apply the changes to the database.

private void customersBindingNavigatorSaveItem_Click(object sender, EventArgs e)

  db.SaveChanges();

Add another menu item the the binding navigator that will do the actual synchronization. For it click event handler – implement the synchronization logic:

Add a Microsoft.Data.Entities.Synchronization.DataServiceSyncProvider instance, and point to the the ADO.Net Data Service URL.

Create a Microsoft.Data.Entities.Synchronization.ObjectContextSyncProvider instance, which is the client-side wrapper for the BankEntities’s ObjectContext.

Create a new Microsoft.Synchronization.SyncOrchestrator instance and set the local and remote providers.

Then, do the actual synchronization. Notice that the sync operation sync between the service and the local database, therefore the data needs to be fetched from the local database again.

private void syncItem_Click(object sender, EventArgs e)

  DataServiceSyncProvider dsp = new DataServiceSyncProvider(

            new Uri("http://localhost:8474/BankDataService.svc/"), "global");

  ObjectContextSyncProvider esp = new ObjectContextSyncProvider(

      () => new BankEntities());

  SyncOrchestrator so = new SyncOrchestrator();

  so.RemoteProvider = dsp;

  so.LocalProvider = esp;

  so.Direction = SyncDirectionOrder.UploadAndDownload;

  so.Synchronize();

  // Load the data again

  CustomersForm_Load(null, null);

Finally, set the client application as the startup project and run it. Sync it for the first time to get the data from the remote server to your local database, and then sync it occasionally to upload changes and download changes to your client.

Enjoy!

.Net Framework 3.5 SP1 and Visual Studio 2008 SP1 are Available!

Guy Burstein — Mon, 11 Aug 2008 18:32:38 GMT

.Net Framework 3.5 SP1 and Visual Studio 2008 SP1 are Available!

Unlike other Service Packs from Microsoft, the SP1 of.Net Framework 3.5 and Visual Studio 2008 not only contains bug fixes and improvements, it also contains new technologies such as ADO.Net Entity Framework v1, ADO.Net Data Services v1, ASP.Net Dynamic Data and the framework and tools support for working with SQL Server 2008 that was RTM'ed last week.

Here are some useful download links:

VS 2008 Service Pack Preparation Tool
.NET Framework 3.5 Service pack 1
Visual Studio 2008 Service Pack 1 (exe)
Visual Studio 2008 Service Pack 1 (iso)
Visual Studio 2008 Express Editions with SP1 (Web Install)
Visual Studio 2008 Shell (isolated mode) with Service Pack 1 Redistributable
Visual Studio 2008 Service Pack 1 Remote Debugger
Visual Studio 2008 Service Pack 1 Stand-Alone Profiler
Visual Studio 2008 Team Foundation Server SP1
Visual C++ 2008 SP1 Redistributable Package (x86, x64, ia64)
Visual C++ 2008 SP1 Sample Library
Microsoft Report Viewer Redistributable 2008 SP1 Language Pack
.NET Framework 3.5 Client Profile Language Pack

While downloading and installing the SP1 of.Net Framework 3.5 and Visual Studio 2008 you can take your time to read the posts I've written during the beta time frame:

Overview of the Service Pack 1

ADO.Net Entity Framework

ADO.Net Data Services

A Simple ADO.Net Data Service Walkthrough (updated for SP1)
Querying an ADO.Net Data Service via .Net Client (updated for SP1)

ADO.Net Sync Services

Sync Services for ADO.Net now use SQL Server 2008 Change Tracking

SQL Server 2008 and Data Access Technologies

Note: If you were waiting for SQL Server 2008 and couldn't install it, now you can.

Enjoy!

How To: Call a Java EE Web Service from a .Net Client

Guy Burstein — Sat, 19 Jul 2008 13:51:53 GMT

How To: Call a Java EE Web Service from a .Net Client

Many organizations have server side investments in Java technologies. While they want to build a compelling UI with Microsoft’s latest technologies, such as WPF and Silverlight, they still want to benefit from those existing investments instead of rewriting them. In order to do so, we have to bridge between those technologies and allow client side technologies consume Java web services.

This post is a step by step guide for building a Java EE Web Service, and a .Net client application that consumes it.

Before we get started with this walkthrough, make sure you have the following installed on your machine:

Create a Java Web Service (Java EE, JAX-WS)

1. Create a new Web Application

In the NetBeans 6.1 IDE, choose File –> New Project. In the New Project Dialog select the Web category, and choose Web Application from the projects list. Then, Click Next.

* If the web category is not available in this dialog, it means that the NetBeans version you have installed isn’t the Web and Java EE package.

In the Name and Location page, set the location where you want to create the web application, and provide a name for the project. Click Next.

In the Server and Settings page, leave the default settings (Java EE 5, Use GlassFish V2) and Click Finish.

This creates the initial web application and opens the project for editing.

2. Create the Web Service

Add a new web service to the project. Right click the project node and choose New –> Web Service.

* Notice that the location of the Web Service option in the menu may change from this image and your IDE.

In the New Web Service dialog, provide the Web Service Name, and the Package. The name of the service will affect the final URL for calling the service, and the package name will be the namespace of the service contract. Click Finish.

The Web Service now appears in the project tree.

To implement the service, double click the service node in the project tree (in the figure above – CalculatorService). This will open the Web Service in Design mode, that lets you graphically design your service.

Change to Source View by clicking on the Source button in the upper toolbar, and this will open the CalculatorService.Java file for editing. Here is a sample implementation of the service. Notice how Java Annotations are similar to .Net Attributes, especially how similar they are to the Web Services attributes we know…

package org.bursteg.calculator;
 
import javax.jws.WebMethod;
import javax.jws.WebParam;
import javax.jws.WebService;
 
@WebService
public class CalculatorService 
{
        @WebMethod
        public int Add(@WebParam(name="a") int a, 
                       @WebParam(name="b") int b) 
        {
            return a + b;
        }
}

Deploy the web service to the web application server. From the NetBeans IDE this is done by right clicking the project node, and choosing Undeploy and Deploy.

After the web application has been deployed, just to make sure the web service works as expected, you can right click the web service node, and choose Test Web Service.

This will open the browser and navigate to a test page with the url of the service (http://localhost:9232/Calculator/CalculatorServiceService) with a ?Tester suffix.

Call the Java Web Service from a .Net Client

In Visual Studio 2008, create a new console application.

This creates a new solution with a single Console Application project in it.

Right click the project node and choose Add Service Reference.

In the Add Service Reference Dialog, paste the address of the service metadata endpoint (service address + ?wsdl suffix: http://localhost:9232/Calculator/CalculatorServiceService?wsdl), and click Go. The dialog will get the service metadata and understand the service contract.

Provide a namespace for the service reference, and click OK.

This will generate the client side proxy that lets you consume the service easily, and the required configuration settings into the configuration file.

To call the service using the generated client side proxy, open Program.cs and use the following code:

static void Main(string[] args)
{
    CalculatorServiceClient proxy = new CalculatorServiceClient();
    int result = proxy.Add(2, 3);
    Console.WriteLine("Calculator Service returned: " + result.ToString());
}

Run the program and see that the web service is being called and the result is correct.

Conclusion

Since Java EE Web Services (JAX-WS) are standard SOAP services, they are easily interoperable from a .Net client application with only several clicks. Visual Studio generated a .Net client proxy that makes it very easy to connect and call the service.

Enjoy!

LINQ to SQL Support for SQL Server 2008

Guy Burstein — Tue, 13 May 2008 11:17:49 GMT

LINQ to SQL Support for SQL Server 2008

With the release of Visual Studio 2008 and .Net Framework 3.5 SP1, LINQ to SQL now supports some of the new features in SQL Server 2008.

LINQ to SQL with SQL Server 2008 Date Time Types

LINQ to SQL and FILESTREAM

Enjoy!

Visual Studio 2008 and .Net Framework 3.5 SP1 Beta - A Guided Tour

Guy Burstein — Mon, 12 May 2008 20:09:23 GMT

Visual Studio 2008 and .Net Framework 3.5 SP1 Beta - A Guided Tour

Over the last month I've been working with an internal build of the Visual Studio 2008 and .Net Framework 3.5 SP1 Beta in order to explore the new features in it. This post lists all the posts I've written exploring the service pack.

Overview of the Service Pack 1

ADO.Net Entity Framework

ADO.Net Data Services

A Simple ADO.Net Data Service Walkthrough (updated for SP1)
Querying an ADO.Net Data Service via .Net Client (updated for SP1)

ADO.Net Sync Services

Sync Services for ADO.Net now use SQL Server 2008 Change Tracking

SQL Server 2008 and Data Access Technologies

Enjoy!

.NET 3.5 Enhancements Training Kit is available for Download

Guy Burstein — Sat, 12 Apr 2008 10:09:19 GMT

.NET 3.5 Enhancements Training Kit is available for Download

The Developer and Platform Evangelism Group in Microsoft has created a new training kit for all the enhancements for the .Net Framework 3.5:

ASP.NET MVC
ASP.NET Dynamic Data
ASP.NET AJAX History
ASP.NET Silverlight controls
ADO.NET Data Services
ADO.NET Entity Framework

Download the training kit (34.9 MB)

Enjoy!