According to the MS documentation Sync Framework Toolkit (https://code.msdn.microsoft.com/Sync-Framework-Toolkit-4dc10f0e) is a legacy open source product which MS no longer support:
https://msdn.microsoft.com/en-us/library/jj839436(v=sql.110).aspx
That's fine, but how about Microsoft Sync SDK which is not open source?
Does it mean that open source part useless because server part can be removed by MS in the future?
The question is does it mean that Sync Framework SDK (Server side library) is dead? (Green Part)
I am not sure what do you mean by dead.
As long as you know Sync Framework Toolkit is not supported and you know the consequences of using it.
As to Sync Framework SDK
Some Federal agencies did approve the usage of that SDK.
This link might be the answer to your question.
According to the US department of Veteran Affairs
https://www.oit.va.gov/Services/TRM/ToolPage.aspx?tid=11403
Microsoft Sync Framework Software Development Kit (SDK) Technology is approved with constraints in 2019, 2020, 2021
Approved w/Constraints: The technology/standard can be used within the
specified constraints located below the decision matrix in the
footnote1 and on the General tab.
However, these constraints are not met.
Technology must remain patched and operated in accordance with Federal
and Department security policies and guidelines in order to mitigate
known and future security vulnerabilities.
You might notice this announcement which does not seem to still be valid,
Microsoft Sync Framework 2.1 is now in extended support!
Starting from January 12, 2016, Microsoft Sync Framework 2.1 (including SDK and redistributables) has entered extended support. This change has an impact on how you receive software updates and support for Microsoft Sync Framework. For more detailed information, refer to the Microsoft Support Lifecycle.
I hope that can be an acceptable answer to your query.
Microsoft has stopped supporting Sync Framework. We'd a ticket opened with MS for one of the framework issue, and got to know from MS that the team which has originally developed the framework is disbursed and there is no support available.
Does it mean that open source part useless because server part can be
removed by MS in the future?
You can always download the SDK and keep a copy, so I don't see a problem on the "Microsoft removing it" question.
The question is does it mean that Sync Framework SDK (Server side
library) is dead?
In my opinion, yes. It is only a matter of time before the software won't work with an updated version of windows (last update to the SDK was August 2010). Once that happens or you discover a critical bug, you are stuck.
Related
Do you know of any successful implementations of the Customer care Accelerator framework for Dynamics CRM 2011? The powerpoint demos look great, but when I try to find information on this I really don't find a lot.
The reason I ask is because one of my customers wants me to look into this. The purpose is to create a Composite UI tighlty integrated with Dynamics CRM.
After downloading the CCA I tried to compile the code but it requires a missing DLL that is not distributed with CCA. It turns out this is an old version of WPFCAB which I understand is no longer maintained (http://wpfcab.codeplex.com/) but is now part of the Smart Client Contrib (also, from 2008). My colluegue believes this too is old and has been replaced by PRISM.
My question is simply, are there any (successful) implementations of CCA for CRM 2011 and is it actively maintained?
Historically I've found most of the MS-provided Accelerators to be rather unsatisfying: Either too incomplete, or very feature-complete but inflexible. There's a few exceptions (in CRM v4 the Event accelerator provided a nifty set of pre-configured entities, but the portal side was junk) but overall I think they're a good demo of what MSCRM is capable of but not in a customer-usable scenario.
For CRM2011 the Accelerators I've tried using have just taken the old CRM4 code and pushed it through a 4>2011 converter with little or no tidy-up.
If you're a competent coder, I'd skip the accelerator and write something from scratch either using the MS SDK or in HTML/JavaScript using the oData APIs.
(Note: I'm a CRM consultant for an MS partner, and I do next to no server-side coding - a developer may have a different take on this)
Yes there are many successful implementations of CCA (Customer care Accelerator). You can yourself try installing it from the links given below. Here are a few links that you can check http://crmmongrel.blogspot.in/2011/08/customer-care-accelerator-for-dynamics.html http://community.dynamics.com/crm/b/crminogic/archive/2012/08/07/tips-to-install-cca-for-crm-2011.aspx
Please note - you must do this from the server where CRM is installed.
PS - This also works for CRM 2013.
Hope this helps.
I'm looking to create an IM bot for OCS which will provide users with certain pieces of information based on a series of external triggers. We use OCS exclusively in our environment, so building a bot on another platform is most likely out of the question. From my research, I found some documentation from Joe Calev on UCMA, but it's very scattered and I would prefer something I can read offline. Plus, it seems a bit unfriendly for those who've never worked with UCMA before. I can't seem to find any other good documentation aside from this.
Does anyone know a good book or series of PDFs I can refer to for a project like this? Or is it not recommended considering I've never done any work with UCMA?
Thanks!
I'd highly recommend Programming for Unified Communications by Rui Maximo and others on the OCS team.
As well as UCMA, it also has some great information about the other APIs, and walks through how to build a development environment, which is essential if you're serious about OCS development.
At one point, i'm fairly sure this book was available as a free PDF download, so might be worth searching for (I did a quick search, but couldn't find it)
If you're interested in developing against Lync (latest release of OCS) then George Durzi and Michael Greenlee will be releasing a book in the coming months - definitely one to watch out for
Edit: I originally assumed you were talking about UCMA 2.0, as the post was tagged OCS, but noticed the title mentions UCMA 3.0. (1.0 is for OCS 2007, 2.0 is for OCS 2007 R2, 3.0 is for Lync Server 2010). if your infrastructure is Lync Server 2010, then the help files in the server SDK are the best resource until the Durzi/Greenlee book is released
Edit: Professional Unified Communications Development with Microsoft Lync Server 2010 is now available. Consider it the bible if you're doing Lync development.
Does tooling exist for Visual Studio that makes it possible to create a Symbian mobile application using .NET?
In the past, Visual Basic, VB.NET, and C# development for Symbian were possible through AppForge Crossfire, a plugin for Microsoft Visual Studio. On 13 March 2007 AppForge ceased operations; Oracle purchased the intellectual property, but announced that they did not plan to sell or provide support for former AppForge products. Net60, a .NET compact framework for Symbian, which is developed by redFIVElabs
http://en.wikipedia.org/wiki/Symbian#Other_languages
I guess RedFiveLabs (the maker of .NET for Symbian) is out of business. Except for links to their website, I can't find anything anymore from them. Their website is unreachable ( http://www.redfivelabs.com ) Their product is/was called Net60.
Silverlight is available for the S60 5th gen devices: http://www.silverlight.net/getstarted/devices/symbian/
Symbian itself is also almost dead, their Symbian^3 isn't good enough, and I guess Nokia put their bets on MeeGo (although I read somewhere that even Windows Phone 7 was an option).
This makes the development of anything for Symbian not really worthwhile, also since the current user base doesn't interact with the OVI appstore like users of other phone OS's.
AFAIK the only .NET platform is Windows.
There is also Mono for linu, but I am almost sure, that you can't code in c# for symbian.
There's an article on that here: http://www.danielmoth.com/Blog/net-compact-framework-on-symbian.aspx
It contains a link to an interesting article on porting the .NET Compact Framework to Symbian phones. http://www.jot.fm/issues/issue_2006_04/article4/
That article stated:
Our analysis shows that the specifics
of the Symbian OS and the resource
constraints of today’s smartphones
make porting difficult but not
impossible.
In other words, it's POSSIBLE but probably not worth your effort.
My team is using the Mere Mortals .NET framework from Oak Leaf. Being used to working with primarily open source software, I found it excruciatingly painful to find ANY community support for MM.NET. When I asked if there was any, the only place I was given to look for support was Universal Thread, which is a site which requires a membership for search on archived questions. It seems like a third party, pay-for site should not be the primary source of support for anything like this, especially MM.NET which costs $700 per developer. It doesn't seem to me like an entire community around MM.NET would choose to all pay on top of the license just to use a forum. If not Universal Thread, then what is the "official" place to find support for the Mere Mortals .NET framework?
I would suggest investigating this stuff before you invest, the only problem worse than trying to get support now, is trying to get support in a few years time.
Having said that, if they're taking money for the product they should be giving you direct support via email or otherwise, you shouldn't have to find "community support".
I just found in the MM.NET Developer's Guide that Universal Thread is the "official" community support site.
I've been looking for this information for my commercial desktop product, with no avail.
Specifically, what I'm look for, is deployment statistics of the .NET framework for end-users (both granny "I'm just browsing the internet" XP, and high-end users, if possible), and in the commercial/business sector.
Edit: Other than the data points below, here's an interesting blog post about .NET deployment rates.
Some statistics from 2005 I found at Scott Wiltamuth's blog (you can be sure these numbers are much higher now):
More than 120M copies of the .NET Framework have been downloaded and installed using either Microsoft downloads or Windows Update
More than 85% of new consumer PCs sold in 2004 had the .NET Framework installed
More than 58% of business PCs have the .NET Framework preinstalled or preloaded
Every new HP consumer imaging device (printer/scanner/camera) will install the .NET Framework if it’s not already there – that’s 3M units per year
Every new Microsoft IntelliPoint mouse software CD ships with the .NET Framework
It is also worth pointing out that Vista and Windows Server 2008 both ship with the .NET Framework. XP gets it via Windows Update.
It depends a lot on which version of the framework you are targeting. I believe 1.1 (and even 2.0) are widely deployed. The later versions are not.
You should also visit this site for some very good information on .Net Framework Deployment: http://www.hanselman.com/smallestdotnet/
I don't have any hard numbers, but these days, it is pretty safe to assume most Windows XP and Vista users have at least .NET 2.0. I believe this was actually dropped via Windows Update for XP, and Vista came with at least 2.0 (apparently with 3.0 as pointed out in the comments to this answer).
I needed that same kind of information at my last job, where I was attempting to convince my manager to allow .NET development. The customer base was primarily dial-up users, so requiring a 20+ MB download was a tough sell. Unfortunately, I wasn't able to find any sort of statistics, either from Microsoft or from a research firm.
What I was able to get, however, was web analytics from the company's home page. .NET inserts its version number into the User Agent field, which I was able to log using our analytics package. From there, some Excel gruntwork was able to give me a rough idea of how many customers already had .NET installed, and which version(s).
Unfortunately that won't help you answer the broader question of deployment rates across multiple demographics, but it might be a useful technique for a single customer base.