스터디 1기 3조 프로젝트! 프리젠터(Presenter)
윈도우폰7 첫만남 세미나
http://onoffmix.com/event/1895
윈모데브(http://www.winmodev.net) & 실버라이트 코리아(http://cafe.naver.com/mssilverlight)
연합 세미나
키노트세션에서 발표했던 프리젠터!
데모신에게 딱걸려 보여줬던 그영상 ㅜ.ㅜ
실제 폰(옵티머스7)에서 테스트 했던 Presenter
| 2007 병원 영상편집 프로그램 (0) | 2010.11.12 |
|---|---|
| 2006 워커힐 서베일런스 센터 (0) | 2010.11.12 |
| 2009 IP-USN 연계검증 선도사업 (0) | 2010.02.04 |
| 2008 방송통신망 기반 IP-USN 통합 시험환경 구축 사업 (0) | 2009.08.07 |
| 2008 한국도로공사 무선랜 사업(무선메쉬) (0) | 2009.08.07 |
Both MonoDroid and MonoTouch bring the core of .NET to the iPhone and Android platforms, but we do not offer a UI cross-platform solution. Each operating system offers slightly different services for building user interfaces, interacting with the phone, the address book, the built-in GPS and audio systems.
Our recommendation for users that want to target all three mobile platforms is for developers to separate the business logic of their application from the user interface and hardware interface layer.
This means that both the user interface layer and any hardware integration components will have to be written once for each platform.
Your business logic can consist of anything that uses the core APIs in: mscorlib, System, System.Xml, System.Core, System, System.Data, System.Json, System.Runtime.Serialization, System.ServiceModel, System.Web.Services and System.Xml.Linq as well as
In addition, OpenGL code between the iPhone and Android can be shared as we support the OpenTK API, an object-oriented wrapper for C# developers to access OpenGL libraries.
Since the core MonoDroid and MonoTouch libraries are supersets of the Silverlight APIs, you might have to factor those features out.
MonoDroid supports a subset of WCF, but this support is not battle tested like our standard System.Web.Services stack (old .NET 1.0 SOAP).
The WCF subset is the same subset exposed by Silverlight. This is because MonoDroid's WCF stack is derived from the work we did for our open source Silverlight implementation, Moonlight.
You should consider our WCF support "alpha" quality, as it is known to have various missing features. Although we are working to resolve those, it is best to not depend on these features being ready until we actually ship and announce them.
If all you want is an RPC system across systems, we recommend that you use one of the various .NET versions of Google's Protocol Buffers:
| 소설같은C# Third Edition 소스코드와 강의자료 (0) | 2010.11.22 |
|---|---|
| .NET 서비스팩,재배포 (0) | 2009.04.30 |
| Generics & Template(그리고 STL) (2) | 2009.04.24 |
| 베일 벗은 오픈소스 닷넷 개발툴「모노 1.0」 (0) | 2009.04.22 |
| SharpDevelop v1.1&2.1 (&Mono) (2) | 2009.03.17 |
