I m working on a facebook ap with Facebook C# SDK and MVC 3.
One of the problem I m having is: multiple versions of Facebook SDK API with several inconsistent versions. Almost every version there is a change in the API and something that works in one version doesnt work in another. There are also major changes between API versions.
I m using the latest version. (6.0.12). I cant find any documentation on how to use the API.
API website has lot of TODO pages. (http://csharpsdk.org/) and documentation is not concise.
Should I use another SDK ? What do you recommend? or are there any samples I can use for this version?
Thanks.
I'm much in the same boat as you.
I've followed the blog posts from the members of the Facebook c# SDK team, and their reasoning behind doing the latest major re-work of the API. I'm optimistic and think it's a healthy decision, leveraging the majority of the work from the server to the client instead.
In the end, I think it will benefit our applications with a much more scalable and performant solution than before with the earlier SDK. A good thing if your application gets viral.
The earlier versions had good and plenty samples and documentation, I only hope that in time the team will be able to provide that with the newer version as well.
For me, I currently have a v5.0x solution in prod, and I'm very eager to jump on the newer SDK, but I'm holding on for good samples as well, hoping for some magic during the upcoming months.
It's really a question on how long you can wait, I think it's the best SDK out there at this point.
If anyone is having problems with FB breaking old versions like I did, here is a small and brief tutorial I created
http://theocdcoder.com/tutorial-integrating-facebook-authentication-asp-net-mvc-3/
Related
I am looking to integrate a bot made with the Microsoft Framework Composer to one made in the SKD with C# dot net. Is there any documentation anywhere or anyone that knows how to do this?
AFAIK that's "not doable" (in a "reasonable" amount of time).
The point is that SDK 3, lacks support for Adaptive Dialogs, which are THE cornerstone of Composer.
Also, Adaptive Dialogs have a large set of new features, like Adaptive Expressions, Language Generation, Interruption handling and so many others, that have no equivalent in SDK v3, that you could end with a nice bot design in Composer that wouldn't "run" in SDK v3.
Not to mention that you can't deploy new v3 bots anymore.
Even though Adaptive Dialogs have a steep learning curve, specially coming from v3, it's worth taking your time to learn them, because they can make you work much more faster than v3.
So, take the plunge 😉
I am looking into the opposite problem, i.e. I would like to use the full SDK features in a Composer-generated bot.
However during my search I encountered various hints that might just help with what you are trying to achieve:
Adding Bot Framework Composer dialogs to a Skill: still marked as experimental, but seems that you can have a root bot and integrate a Composer bot while still being able to continue working with Composer. Looks promising to me.
Another option I see is to consume the Composer-bot as a skill in the SDK-bot as the root. However I have not seen any documentation thereof (only the other way round).
I moved to Kinect for Windows 2.0, and I want to run a sample from the 1.x series, and obviously Visual Studio shoves me 80++ errors.
Searching on the web was useless, I found no documentations for porting old code to 2.0, or at least, I wasn't able to find any good source.
Has anyone succeeded in running old examples on the new KFW2?
Thanks!
API has certainly changed, you will have to create wrapper (adapter pattern) around sdk 2.0 or correct your code to use newer API. In every case you will have to alter our original code to some extend. Altho there are some similarities there is no simple "converter-like" solution.
There are various questions (mainly around 2009 to early 2010) discussing use of the Mono framework to write apps in C# and deploy them to iPhone. Also there is some discussion of the Unity Framework, but I'm more interested in a fairly standard UI app.
Has anyone successfully developed and released a commercial quality app using C#/Mono? If so, what were the lessons learnt? Pain points? If you know of other people who have done so, how have they fared?
Thanks!
Mark
The basic answer is yes, there are a lot of applications out there that have been developed using MonoTouch. You can find some nice numbers on Novell's site but there are a ton of games and other application is the AppStore that were developed using MonoTouch.
I would start your investigation by going to review articles that walk through the good and bad of MonoTouch. For example, here is a good starting place:
http://www.bryanthankins.com/techblog/2010/01/17/monotouch-review-porting-an-obj-c-app/
http://www.devproconnections.com/article/mobile-development/review-monotouch-enterprise
Then I would look through some tutorials to see how exactly this is done so you can see if it will fit in your environment. There are a lot out there that show off how to use MonoTouch, including these:
http://vimeo.com/6689472
http://blog.keen-edge.com/category/monotouch/
Finally, I would look at what is happening currently with Attachmate and the takeover of Novell. There are some real issues there that may cause you to reconsider going with MonoTouch. For example, while Mono's future may be unclear at Attachmate, it seems that it might be continued through another company:
http://ostatic.com/blog/mono-continues-without-novell-attachmate
This uncertainty might not be what you want in a project you are counting on so you need to work through that before committing.
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.
At my place of work I've been put in charge of creating a coding standards document. Generally we follow what FxCop and StyleCop tools report to some degree but what we really require is document that will explain when to use a convention, why and maybe even a simple example.
This could be extended in the future for other purposes as well.
The first thing that came to my mind is to have an internal wiki site that we could build up and change easily over time but I've never used a wiki-based engine before and would like some recommendations.
If possible the engine should be in C# so we're able to tweak it to our needs if required.
If you think a wiki solution is the wrong way to go about this then please give an alternative :)
Update
I've just been informed, although we do have a php server it wont be staying, so I'm afraid php-based wiki ideas are off the table.
Update 2
Could you also (if possible) let me know if any of these solutions work with Active Directory?
Cheers
Tony
ScrewTurn Wiki is an free and open-source wiki made in C# and ASP.Net. Different database back-ends can be used, like MSSQL and MySQL, but also works without any database. It has several plugins to work with Active Directory.
Mindtouch Deki
Great wiki and it's built on C# and PHP, so you can use it on Mono or .NET
It also has Active Directory integration.
Download their ready-to-use VMware image. It started using it on my own PC then moved it to the company's VMware server when they had it ready.
We keep an internal wiki at my shop that has almost all of our documentation (not just coding standards). We didn't really see the need to roll our own so we just used MediaWiki...
We use JAMWiki and love it.
It is a solid application, we have had nothing but good interaction with both the application and the developers.
The guy you maintains the code does a great job answering questions and helping users out.
Brad Abrams has published an online set of C# coding standrds:
http://blogs.msdn.com/brada/articles/361363.aspx
If you go to the starter kits section of the Microsoft ASP.NET site, you will find several wikis to download such as ScrewTurn and Flexwiki. A wiki would be ideal for your needs by the sound of it :-)
I second MediaWiki. It's not C#, but it can be a nice excuse to sneak some free software in through the backdoor.
If you guys are a Microsoft shop, though, and are using Sharepoint, it has some built-in wiki-esque functionality.
In one project that I develop, I set up one MediaWiki wiki for development documentation, and one for online help.
I even generate part of the development documentation right from source code and database.
At the shop I'm at they use a commercial package which is really good: Confluence. What's especially nice is that it integrates with LDAP/AD so that you don't need a seperate login and it's build especially with business use in mind and has lots of free plugins. We couldn't live without it.
I am confused by what you mean when you say you don't have a php server. It runs on every platform known to man. I am noticing most Visual Studio Developers don't know that PHP runs on IIS.
I would go with mediawiki It has the biggest feature set and most add-ons developed for it in case you ever need to port your data elsewhere. If you need to modify your wiki you are doing it wrong.