Home
Nilas Jensen's Library tagged → View Popular
Sync Framework Tutorial - Part #1 - Introduction « Alex Duggleby’s Palace of Words
-
At Tech-Ed in Barcelona this year Soma Somasegar announced the Microsoft Sync Framework. It provides a set of tools and best practices for enabling online/offline and sharing applications with any kind of data store and over any kind of transport channel.
At the core the SF has a synchronization runtime that takes care of the main sync’ing algorithm and provides a number of hooks to allow system-specific providers and custom conflict handling.
The sync providers enumerate or apply changes for their specific client system data store and can be built to transform between different schemas of the source and destination systems. In addition to the data store they also need some place to store the metadata required for synchronization.
Three providers are currently available from Microsoft:
- Sync Services for ADO.net: Similar to RDA (Remote Data Access) this provider will allow synchronizing databases. On the client side the SQL Server Compact Edition is utilized.
- Sync Services for File Systems: Check out the new version of the SyncToy (currently beta) which allows easy change tracking between folders.
- Sync Service for FeedSync: formerly known as SSE - Simple Sharing Extensions, this provider allows the communication of sync changes between hosts using RSS/ATOM feeds
15 Seconds : Using Managed Components from Unmanaged Code
-
Standard COM implementation relies on the Windows registry for looking up the information related to COM components, like CLSID, Interface IDs, the path of the component's housing (DLL/exe), the component threading model, etc. .NET framework does not depend on the registry and uses metadata for this information. Therefore, we have to generate the COM-compatible registry entries for our managed server so that the COM runtime could instantiate our server.
Like tlbimp.exe, there is a tool named regasm.exe. This tool reads the metadata information within an assembly and adds the corresponding COM-compatible registry entries. Classes in the assembly are not COM creatable until they are actually registered in the Windows registry.
FileHelpers Library 2.0 - Marcos Meli
-
The FileHelpers are a free and easy to use .NET library to import/export
data from fixed
length or delimited records in files, strings or
streams.
The idea is pretty simple:
You can strong type your flat file (fixed or delimited) simply describing a class that
maps to each record and later read/write your file as an strong typed .NET array
The Library also has support for import/export data from differents storages like Excel,
Access, SqlServer, etc.
Start to use the FileHelper right now:
Microsoft Interop Forms Toolkit 2.0
-
Interop Forms Toolkit 2.0
The Interop Forms Toolkit 2.0 is a free add-in that simplifies the process of displaying .NET forms and controls in a Visual Basic 6 application. Instead of upgrading the entire code base, these applications can now be extended one form at a time. The goal is a phased upgrade, with production releases at the end of each iteration containing both Visual Basic 6 and Visual Basic .NET forms running in the same Visual Basic 6 process.
Most importantly, the Toolkit guides you down a migration path that allows you to focus on writing code that adds business value instead of infrastructure and interop code.
Calling a .NET Component from a COM Component
-
This code starts by defining an interface named iTemperature. Because the interface is defined with the Public keyword, it will be exported to the type library you'll create from this assembly. You can think of an interface definition as the skeleton for all or part of a class definition. The interface definition can contain members (properties, methods—either functions or subs—and events), just like a class. But unlike a class, an interface definition contains no code for any of these members. A class can implement one interface (as in this example) or more than one interface.
Wrap It Up: Call Into The .NET Framework From Existing Visual Basic 6.0 Apps -- MSDN Magazine, May 2006
-
Public Function Ping(ByVal hostNameOrAddress As String, _
Optional ByVal timeout As Integer = -1)
ClassInterfaceAttribute Class (System.Runtime.InteropServices)
-
Although class interfaces eliminate the task of explicitly defining interfaces for each class, their use in production applications is strongly discouraged.
Qualifying .NET Types for Interoperation
-
Classes should implement interfaces explicitly.
Although COM interop provides a mechanism to automatically generate an interface containing all members of the class and the members of its base class, it is far better to provide explicit interfaces. The automatically generated interface is called the class interface.
-
For instance, parameterized constructors, static methods, and constant fields are not exposed to COM clients.
- 1 more annotations...
Selected Tags
Related Tags
Sponsored Links
Top Contributors
Groups interested in dotnet
-
Dotnet
This is for dotnet, c#, Sil...
Items: 20 | Visits: 36
Created by: Alok Ranjan
-
C#3.0 LINQ
Items: 4 | Visits: 35
Created by: Arrix Z
Highlighter, Sticky notes, Tagging, Groups and Network: integrated suite dramatically boosting research productivity. Learn more »
Join Diigo
- yyensen on 2007-12-18
- yyensen on 2007-12-18