Free $5 for start real Forex trading

By signing up you will get $10.000 virtual money for practice and $5 for start real trading. It means you can be forex trader with NO INVESMENT at all http://bit.ly/marketivasignup

Charp on the Air

. Monday, December 14, 2009
0 comments

 

Here is Mike Chambers’s article on Adobe Air and Charp /.net

CommandProxy : .NET / AIR Integration Proof of Concept

 

Two of the most requested features for Adobe AIR have been the ability to launch native executables from an AIR application, and the ability to integrate native libraries into an AIR application. Unfortunately, neither feature will be included in Adobe AIR 1.0.

However, this does not mean that you cannot build an AIR application that has closer / tighter integration with the underlying operating system. This lower level of integration is possible, but it requires some work on your part. I have put together a proof of concept project, which shows how to integrate Adobe AIR applications with c# / .NET code on any operating system that Adobe AIR currently runs on (Mac and Windows). The project is called CommandProxy. It provides a communication proxy between an AIR application and the underlying operating system and could theoretically work with other web based desktop runtimes (such as Mozilla Prism).

Update : I have posted some additional thoughts on this proof of concept here.
Note, this project is in no way supported by Adobe. This is a proof of concept project that I put together to help developers understand one possible way to extend AIR functionality beyond that that is provided by the runtime.

The general concept behind the project is similar to the now defunct Artemis project (which is Java based). The AIR application communicates with the CommandProxy process to communicate and integrate with the underlying operating system. Currently the command proxy supports launching processes (and getting the output from the processes) as well as taking a screenshot of the user’s current screen. However, the framework is built in such a manner that it is possible to add new functionality to the proxy.

Here is an overview of the life-cycle of an AIR application using the command proxy.

CommandProxy / AIR Application Lifecycle

  1. Command Proxy process is launched by the user. The shortcut for the process passes in the path to the AIR application to launch (or this can be hard coded into the proxy)
  2. The Command Proxy process then launches the AIR application, passing in a communication key, as well as the socket port that the AIR application should use to communicate with the proxy.
  3. The AIR app may then at some point communicate with the proxy to execute a command. For example, it may tell the proxy to launch a specific process.
  4. The proxy executes the specified command.
  5. If appropriate, the proxy then returns any command output back to the AIR application.
  6. The command / response cycle can occur multiple times during the application life-cycle
  7. When the AIR application process is terminated (i.e. the user closes the application), then the proxy process automatically exits.

Currently, the project is meant as a proof of concept, and not as a general use framework. This mainly means that there is not a lot of documentation (although the code is fully commented) and if you want to use it, you are going to have to compile the proxy yourself. If there is interest, then I am willing to expand the project to other contributors.

If you wanted to use something like this in a production level application, then you would need to:

  • Compile the CommandProxy
  • Compile the AIR application
  • Create the AIR file to install the AIR application
  • Create a custom installer that first installs the AIR application, and then installs the short cut to the command proxy

Instead of launching the AIR application directly, the user would launch the command proxy process, which would then launch the AIR application.

The project is hosted on Google code, and includes the following:

  • Full C# / .NET code, compilable under Visual Studio and Mono. (Screenshots do not work under Mono)
  • ActionScript 3 library for communicating with the proxy.
  • Some very basic documentation

If you have questions, then post them in the comments and I will try and address them (and maybe create an FAQ on the project page). If there is interest, then I could also create a mail list on Google groups to discuss the project. If you find bugs with the code, then post them on the project’s issues page.

I am also hoping to post some examples of AIR apps that use the proxy. Lee Brimelow built a simple example of an AIR application that takes a screenshot, and then opens it in Photoshop for editing. You can see a demo of that example toward the end of the video posted here (it is about half way through the video).

MonoDevelop goes cross platform

. Sunday, December 13, 2009
0 comments

Tags: Monodevelop,Windows,Mono,Beta

Since the beginning of time, man has yearned to get a cross platform .NET IDE. Homer's Odyssey described one man's effort to achieve such a thing. And it was not until today, September 9th of 2009 that the world can test out such a tool.

With this release MonoDevelop leaves its cozy Linux nest and embarks on a wild adventure into the hearth of MacOS and Windows. The MonoDevelop team made this one of their major goals for this release: to turn our loved IDE into a cross platform IDE.

Read more

Mono for Windows

.
0 comments

Tags: Mono,C#,Linux,Windows

Mono provides the necessary software to develop and run .NET client and server applications on Linux, Solaris, Mac OS X, Windows, and Unix. Sponsored by Novell, the Mono open source project has an active and enthusiastic contributing community and is positioned to become the leading choice for development of Linux applications.Mono is a software that can develop and run .NET client and server applications.
Mono can run binaries produced by Visual Studio, there is no need to recompile. Mono API coverage is limited to the .NET 1.1 API at this point, with spotty support for 2.0.

Here are some key features of "Mono for Windows":
· Multi-platform
· Based on the ECMA/ISO standards
· Can run .NET, Java, Python and more.
· Open Source, Free Software.
· Commercially supported.
· Comprehensive technology coverage.

· LINQ to SQL is now partially supported
· New debugger engine - Mono Soft Debugger
· Early partial support for C# 4.0
· Includes some components of the ParallelFx framework
· Dynamic language runtime (DLR) is now distributed as part .NET 4 profile
· The WindowsBase assembly is now part of the standard Mono distribution
· A lot of WinForms fixes
· The csharp command now supports auto-completion using the tab key
· xbuild, the Mono implementation of the msbuild build tool has advanced significantly
· Mono now includes a sandbox and its verifier
· As part of the gsoc 2009, Jerry Maine ported Mono.Simd to AMD64
· It is now possible to compile Mono to use the LLVM code generation engine as an optimizing compiler for Mono
· Support for generics is greatly improved compared to 2.4
· Signal Chaining
· Debugging support for GDB

Download

C # - VB and examples of parallel programming

. Wednesday, December 9, 2009
0 comments

Expressed thanks to the Mitarbeiet the Visual Basic team are examples of parallel programming with. NET 4 Beta 2 now available in Visual Basic been. For the Beta 2 of. NET Framework 4 updated samples are available not only as a C # source code, but most of them now in VB code. It is up 21 examples of calculating the number of PI circuit on image processing algorithms to spell check, or a sudoku example. In the PI sample are shown five variants to compute the circle number. On the console, the time required and the accuracy will be issued. During the slowest algorithm takes more than 15 seconds,) is the function ParallelPartionerPI in less than half a second finished (quad-core machine.
All examples can be loaded separately, but are also summarized in a solution file, which contains all the examples.
For more information about returns under [www.dotnetpro.de/SLFSL43], the Parallel Computing Development Center

Intel Launches Atom Store for Developers

. Sunday, December 6, 2009
0 comments

Intel today made good on a promise from the Intel Developer Forum (IDF) to release a Software Development Kit (SDK) for Atom-based application developers. This is the first step in establishing an eventual online store for Atom applications.

When he announced the plans for an "Atom App Store" in September, Intel CEO Paul Otellini noted that Atom is in many different devices and it wasn't a single device experience like the iPhone/iPod Touch. Thus, Intel's goal for developers was "write once and run in many places."

As such, the beta version of the Intel Atom Developer Program is available for developers on both Microsoft Windows and Intel's Linux-based Moblin operating systems. It works with popular developer toolkits like Visual Studio to install the app store on the device and everything around it, according to Scott Apeland, director of the Intel Developer Network.

The Atom Developer Program is designed for independent software vendors (ISVs) and software developers to create Atom applications for different platforms, and make the process of porting an app from one platform to another as seamless as possible. In addition to Moblin and Windows, Intel expects to add support for Adobe AIR and Microsoft Silverlight in a future release, said Apeland.

Java/.NET Interoperability: Web Services Aren't Always the Answer

. Saturday, December 5, 2009
0 comments

Web services can be very useful for integrating standalone components that communicate across a network. When used with straightforward call/return scenarios involving a very limited number of data types, setting them up and getting them to work is trivial. Because web services are standards-based, mixing .NET and Java technologies with them is also easy, which leads some people to believe that web services are the answer to the question of Java/.NET interoperability. They often are not.

A simple web search on "Java .NET interoperability" will return many different approaches, but anyone who heard the Microsoft keynote at JavaOne 2009 this past June may have come away believing web services were the best way. This is unfortunate, because for many tasks, web services are not the ideal Java/.NET interoperability solution. For some tasks, using web services is simply impossible. In this article, I identify three scenarios involving Java/.NET interoperability for which web services would be an unwise choice.

For many tasks, web services are not the ideal Java/.NET interoperability solution.

First, let me define precisely what I mean by Java/.NET interoperability. Admittedly, it's a high bar, but a true .NET/Java interoperability mechanism should allow you to substitute something written in Java anywhere you might ordinarily use something written in a .NET language. In other words, it would allow you to access any Java-based entity (such as an object, class, or method) from .NET code, or vice versa. For many scenarios where developers and architects could not use web services, Java/.NET interoperability as I define it would be very useful.

Scenario 1. Embedding .NET UI Controls Inside Java Apps
Consider a situation where you'd like to employ a Windows Forms control inside an AWT-based Java application. The standard way to do this is to obtain a handle to the peer (the underlying Windows object) of the surrounding AWT container, and then use that handle to set the parent object of the Windows Forms control to be the AWT container's peer. (There's more to it than that, but this is the main requirement for getting the embedding to work.) You can't use a web service to implement this kind of interoperability.

Web services are loosely coupled; the service and the client run in separate processes. With separate processes, you can't exchange window handles; the handles are valid and meaningful only in the same process. In other words, this is an interoperability scenario that must be tightly coupled, a situation that web services cannot accommodate. A developer who wanted to embed .NET-based controls inside a Java-based GUI application (or vice versa) would have to use a different approach.

Scenario 2. Calling a .NET Library from a Java App
What if you had a .NET-based library that you wanted to use in an otherwise Java-based application? Any number of factors could lead to this scenario. For example, suppose you:
  1. Already use the library in .NET development, and you want to make use of the expertise you've developed.
  2. Paid a lot for that library and don't want to pay more for a Java library.
  3. Determined the library is simply the best available, regardless of platform.

In this case, you could use a web service to access the .NET code from Java, but that seems like overkill. It doesn't make sense that one would have to set up a server to simply access a library. Web services are much more appropriate for facilitating communications between larger standalone components, not for integrating a library into a larger system. It's also overkill to create a web service to allow access to a library from an application, if the library resides on the same machine. In such a case, it would make much more sense to be able to run the .NET-based library inside the Java application's process, which is impossible with a web service.

Scenario 3. Registering a .NET Listener with a Java API
Suppose you have a JMS (Java Message Service) infrastructure and you want to create a .NET component that will send messages to, and receive messages from, that infrastructure. Ordinarily, you send messages to JMS by calling various send methods in the JMS API, and you receive messages by registering listeners with the JMS infrastructure. The listeners execute when messages arrive.

You can do this with web services, but they aren't very good at handling asynchronous communications. If you want to implement asynchronous communications using web services, you have two options:

  1. Implement a polling mechanism, in which the client repeatedly polls the service for a result. When the result is available, the service places it in a location where the polling operation will find it.
  2. Implement a callback mechanism, in which the client leaves a return address. The service calls this return address when a result is available.

Unfortunately, both of these mechanisms require implementing a significant infrastructure. In the case of polling, you need both a polling mechanism and a mechanism for the service to place a return value where the polling mechanism can see it. In the case of callbacks, you must embed an entirely new "reverse" web service inside the client, so that the original service can contact it and return the asynchronous result.

Both options suffer from a lack of proportionality. As in the scenario where you want an application simply to call a library, web services require implementing mechanisms that are totally out of proportion with the task at hand. Registering a listener that will execute when a certain action occurs is a prime example. There have to be better ways to do this, and there are.

Scenario 2. Calling a .NET Library from a Java App
What if you had a .NET-based library that you wanted to use in an otherwise Java-based application? Any number of factors could lead to this scenario. For example, suppose you:
  1. Already use the library in .NET development, and you want to make use of the expertise you've developed.
  2. Paid a lot for that library and don't want to pay more for a Java library.
  3. Determined the library is simply the best available, regardless of platform.

advertisement

In this case, you could use a web service to access the .NET code from Java, but that seems like overkill. It doesn't make sense that one would have to set up a server to simply access a library. Web services are much more appropriate for facilitating communications between larger standalone components, not for integrating a library into a larger system. It's also overkill to create a web service to allow access to a library from an application, if the library resides on the same machine. In such a case, it would make much more sense to be able to run the .NET-based library inside the Java application's process, which is impossible with a web service.

Scenario 3. Registering a .NET Listener with a Java API
Suppose you have a JMS (Java Message Service) infrastructure and you want to create a .NET component that will send messages to, and receive messages from, that infrastructure. Ordinarily, you send messages to JMS by calling various send methods in the JMS API, and you receive messages by registering listeners with the JMS infrastructure. The listeners execute when messages arrive.

You can do this with web services, but they aren't very good at handling asynchronous communications. If you want to implement asynchronous communications using web services, you have two options:

  1. Implement a polling mechanism, in which the client repeatedly polls the service for a result. When the result is available, the service places it in a location where the polling operation will find it.
  2. Implement a callback mechanism, in which the client leaves a return address. The service calls this return address when a result is available.

Unfortunately, both of these mechanisms require implementing a significant infrastructure. In the case of polling, you need both a polling mechanism and a mechanism for the service to place a return value where the polling mechanism can see it. In the case of callbacks, you must embed an entirely new "reverse" web service inside the client, so that the original service can contact it and return the asynchronous result.

Both options suffer from a lack of proportionality. As in the scenario where you want an application simply to call a library, web services require implementing mechanisms that are totally out of proportion with the task at hand. Registering a listener that will execute when a certain action occurs is a prime example. There have to be better ways to do this, and there are.

For complex, yet still relatively simple, Java/.NET interoperability requirements, web services force you to reinvent the wheel.

Additional Tools Needed for Java/.NET interoperability
For complex, yet still relatively simple, Java/.NET interoperability requirements (such as calling a .NET library from a Java application or registering a .NET listener with a Java API), web services force you to reinvent the wheel. You have to create elaborate infrastructures—exchanging XML through sockets—to accomplish tasks that should be very simple. This is just silly. And for other tasks, such as embedding .NET UI controls inside Java applications, using web services is simply impossible.

The developer and architect toolbox should hold more than just web services for Java/.NET interoperability solutions. They're fine for some things, but for many interoperability tasks, you need a different tool. A Java/.NET bridge will work well in situations where web services are inappropriate or just don't work, and may well be more efficient or easier to use even in those situations where you can use web services.

If you understand the limitations of web services for interoperability and familiarize yourself with other solutions, you can make the best use of both Java and .NET technologies in your applications.

by Wayne Citrin

Visual Studio 2010 is faster than 2008

. Wednesday, December 2, 2009
0 comments

image

What's new from the visual studio 2010?. Some say that the visual studio 2010 more quickly than before. Could happen, but we can not say anything because Visual Studio is still in Beta 2 stage. Some friends prefer visual studion in 2005 from the 2008 version. That happens because the visual studio 2005 more quickly. I will soon leave visual studio 2008 and moved to the 2010 version if it is true that later stable version is faster than the 2008 version.

Microsoft has now released the beta version of Visual Studio 2010. The product comes in three different licenses.

1.Professional

2.Premium

3.Ultimate

Visual Studio 2010 seems to be more promising than the previous versions. Some of the notable features in Visual Studio 2010 are

  1. Built in support for Mutli-Core and Cloud computing
  2. New prototyping, modeling and visual tools are available
  3. Integrated tools for Modeling, designing,building and lot more.
  4. Features new Intellisense editor and an IntelliTrace debugger
  5. Contains automated testing tools.
  6. Contains Azure and other development toolkits
  7. Allows to develop application with the .NET 4 framework
  8. Support for SharePoint Development

With all these features and .NET 4 framework , i’m eagerly waiting for stable release.

Click here to download Visual Studio 2010 Beta 2

Windows Double Explorer

.
0 comments

I found a very interesting tool. This tool is like total commander which I normally use. This tool is run on windows 7 and free for download. You can download at any time but remember that this tool is still alpha version. You can try this tool but should not be your primary tool. We should wait for later after the stable version has been released.

image

Download

Tags: Windows 7,Freeware,Codeplex

Windows Presentation Foundation (or WPF)

. Tuesday, December 1, 2009
0 comments

The Windows Presentation Foundation (or WPF) is a graphical subsystem for rendering user interfaces in Windows-based applications. WPF, previously known as "Avalon", was initially released as part of .NET Framework 3.0. Designed to remove dependencies on the aging GDI subsystem, WPF is built on DirectX, which provides hardware acceleration and enables modern UI features like transparency, gradients and transforms. WPF provides a consistent programming model for building applications and provides a clear separation between the user interface and the business logic.

WPF also offers a new markup language, known as XAML which is an alternative means for defining UI elements and relationships with other UI elements.[1] A WPF application can be deployed on the desktop or hosted in a web browser. It also enables rich control, design, and development of the visual aspects of Windows programs. It aims to unify a number of application services: user interface, 2D and 3D drawing, fixed and adaptive documents, advanced typography, vector graphics, raster graphics, animation, data binding, audio and video.

WPF is included with Windows 7, Windows Vista and Windows Server 2008, and is also available for Windows XP Service Pack 2 or later, and Windows Server 2003.

Microsoft Silverlight is a web-based subset of WPF that enables Flash-like web and mobile applications with the same programming model as .NET applications. 3D features are not supported, but XPS and vector-based drawing are included.



The Silverlight

.
0 comments

The Silverlight Toolkit is a collection of Silverlight controls, components and utilities made available outside the normal Silverlight release cycle. A product of the Microsoft Silverlight product team, the Silverlight Toolkit adds new functionality quickly for designers and developers, and provides the community an efficient way to help shape product development by contributing ideas and bug reports. It includes full open source code, unit tests, samples and documentation for over 26 new controls covering charting, styling, layout, and user input.

CodePlex : an open source project hosting

.
0 comments

CodePlex is an open source project hosting website from Microsoft. It allows shared development of open source software. Its features include wiki pages, source control based on Team Foundation Server but accessible using Subversion, discussion forums, issue tracking, project tagging, RSS support, statistics, and releases. Some of the available licenses are not open source licenses according to the Free Software Foundation or the Open Source Initiative.

While Codeplex encompasses a wide variety of projects, including SQL, WPF and Windows Forms-related projects, major activities center around the .NET framework, including ASP.NET, and Microsoft's intranet collaboration server, SharePoint. The most prominent and used project that was born inside CodePlex, the AJAX Control Toolkit is a joint project between the community and Microsoft.



Get Free Image Editor Paint.NET

.
0 comments

Download free Powerful Image Editor .. Paint.net
Paint.NET is free image and photo editing software for computers that run Windows. It features an intuitive and innovative user interface with support for layers, unlimited undo, special effects, and a wide variety of useful and powerful tools. An active and growing online community provides friendly help, tutorials, and plugins.
It started development as an undergraduate college senior design project mentored by Microsoft, and is currently being maintained by some of the alumni that originally worked on it. Originally intended as a free replacement for the Microsoft Paint software that comes with Windows, it has grown into a powerful yet simple image and photo editor tool. It has been compared to other digital photo editing software packages such as Adobe® Photoshop®, Corel® Paint Shop Pro®, Microsoft Photo Editor, and The GIMP.
tag: Freeware,Image Editor,Software