Ado.NET "Disconnected Architecture" for web development - ado.net

I am new to asp.net and ado.net. I must to develop a content management system with .net and I wonder which option is right for me, disconnected or connected architecture for web?
I dont understand why I should use dataset on online applications.

It sounds like you are getting started with ASP.NET so depending on which technology you prefer (MVC or Web Forms) either of these two tutorials provided by Microsoft will be of great help on general data access.
MVC: http://www.asp.net/mvc/tutorials/getting-started-with-ef-using-mvc
Web Forms: http://www.asp.net/web-forms/tutorials/data-access

Related

Recommendations for a Full-stack Framework for REST?

I am looking for a robust REST framework to eliminate all that boilerplate code with starting up a new REST-only web service (mobile clients). Is there a framework that already has this built-in where I could, for example, simply build the domain models and run with it? I would like to see:
Authentication & User Model
Logging
Basic CRUD
Permissions (for model access)
Scalability
It seems every web service at a minimum needs the above capabilities. Somebody, somewhere must have written a good re-usable framework with the above capabilities. Any ideas? I would prefer Node.js, Java or even hosting with a PaaS service provider that offers these features.
Spring 3 MVC provides a very nice and simple annotation based framework for REST.
See http://blog.springsource.org/2009/03/08/rest-in-spring-3-mvc/ it can be deployed on any java web server like Jetty or Tomcat.
A framework like XAP provides a combined solution of Spring and Jetty plus it's built for dynamic scaling.
See http://www.gigaspaces.com/xap.
Last if you want to easily on board this solution on any cloud CloudifySource provides an open source project which includes XAP capabilities and PaaS.
See http://www.cloudifysource.org
I use Symfony 1.4 for this. It is an PHP framework. It generates most of what you need for free. The database stuff is also quite easy as the Symfony uses ORM libraries (you can choose but I can recommend Doctrine: http://www.doctrine-project.org/).
For example the whole backend site(admin) generating is a matter of running one command. They have a great e-book fro free. More info here:http://www.symfony-project.org/.
There is also Symfony 2.X (http://symfony.com/), which have a lot of new features (e.g. new Doctrine 2.0). Especially with the bundle (plugin) https://github.com/FriendsOfSymfony/FOSRestBundle is the RESTful service quite easy.

Chat application in Rhomobile with asp.net server

I want to integrate a chatapplication in an existing app in Rhomobile (ruby) and my server is a RESTful asp.net mvc server. I didn't find much useful information on how it's done using Rhomobile.
I already did some research and found that many people use xmpp/jabber.
But i don't realy know how to start and how to notify the user when there's a message waiting (if the user is not on the 'chatpage').
I can do polling, but that requires an open connection for every user and i worry about the battery of the mobile device.
Some questions:
What to use with a ruby client and an asp.net mvc sever?
Should i save the chatdata in the database on the central server since asp.net mvc is stateless?
If anyone knows a good guide or tutorial to help me through this, it would be nice - i'm a nembie on this
Thanks!
This is what RhoMobile have on their site.
http://docs.rhomobile.com/rhodes/connect-to-web-services
I also presume you can use whatever ruby and JavaScript/Jquery code you want.

Is ASP.NET MVC a Good Fit for an Event Ticketing Site?

Good Afternoon,
I'm rebuilding an event ticketing site originally developed using ASP.NET 3.5 WebForms and am considering using ASP.NET MVC2 for the rebuilt solution. I like the idea of friendly URLs as the current site has very long query string URLs for each specified event. MVC2 also appeals from a separation of concerns point of view as well. The biggest unknown for me is will MVC2 handle calls to 3 separate web services (SOAP and REST) to get ticket availability? That is, does the controller functionality permit use of such web services? Finally, MVC3 is due to RTM in January. Am I better off waiting for MVC3, or can I start the project in MVC2 and port it later?
Thanks for all your advice and insight.
MVC can handle any HTTP request as ASP.NET forms does. Indeed you should consider to use WCF for handling SOAP queries. And yes, sure you can easely create REST API with MVC.
It is better to start now, with ASP.NET MVC 3 RC2. It is very stable and nice. This will minimize migration work. Welcome to MVC happy world!
The controller will let you run pretty much any code you want.
I just started using MVC in a big project and it's turning out well. We went with MVC 3 and it's been a little tricky living on the edge, but it seems to have a lot of nice improvements. I'm extremely happy to be using MVC instead of Web Forms. To me, it seems to flow smoothly instead of fighting with the way the web works.

LightSwitch vs WCF RIA

I've just found out about Visual Studio LightSwitch, Microsoft's new Silverlight-centric RAD tool.
Does this occupy the same space as WCF RIA Services?
Is WCF RIA effectively dead?
I've been doing some reading, and it seems that LightSwitch actually builds on top of RIA. I saw the following in a review in The Register -
Database connectivity and user
authentication in LightSwitch uses WCF
RIA Services, Microsoft's web service
framework for Silverlight, though
developers are shielded from the
details. This means there is a middle
tier running on Microsoft's IIS web
server.
Lightswitch does not make RIA Services obsolute. They are both valuable but are aimed at different audiences. RIA Services is aimed at professional programmers that want a high degree of control. Lightswitch is aimed at non-professional programmers. You can think of it as a Microsoft Access for building Silverlight applications.
I don't know where you found that quote "LightSwitch is targeted at professional developers and power users looking to create custom LOB applications", but that's NOT what LightSwitch was intended for at all. Power users, yes, professional developers, no.
LightSwitch is targeted at the non-developer, the type of user who creates "departmental" apps, who would perhaps currently use Excel, or Access. Though a number of professional developers (myself included) have recognised that LS is a fantastic tool for us to use as well, we were NOT the target audience at all.
As for RIA services being dead? Not at all! In fact RIA services is one of the main ways of accessing data that LS currently has trouble with (aggregation, projected entities etc). Using RIA services in LightSwitch is VERY easy. We're hoping, with the interest expressed by developers, that things will improve in that direction in future versions.
I agree with Phil, I tend to think of LS as Access.NET, even though it's far more than just that. Think of "forms over data" with all the latest technologies. Silverlight (both in browser & desktop), MEF, Entity Framework, RIA services etc.
Yann

iPhone/iPad apps with backend databases?

We're investigating the iPhone Enterprise Developer Program as a way to develop and distribute in-house apps. Since our backends are all Windows, SQL server and Oracle databases, we have to find out a way to make our data available for the coming in-house apps.
As far as I know that Core Data is mainly based on SQLite as persistent store. I am not sure if there are any APIs available in iPhone SDK for SQL server or Oracle database? Another possibility, or very attractive strategy, is to build our own web-based REST services as CRUD gateway to our databases.
Personally, I prefer to integrate in-house apps with our ASP.NET based web services. I am not sure if this is possible. Are there any examples or documentations about this strategy?
an interesting option is to expose your data from your server using asp.net OData then use this project to generate a client in objective-C to consume your OData service.
As far as I am aware there are no approved API's to access a server based database. The way we do it in our organisation is pretty much the way you are suggesting. In some instances we are using SOAP but typically we just use a custom JSON or XML web service to access the data.
With regards to ASP.NET are you talking about making native iPhone Apps with ASP.NET or getting a native iPhone App to talk to an ASP.NET web service? If its the first then have a look at monotouch (don't know much about it), if its the later then this shouldn't cause issues. Just use NSURLConnection and deal with the resource structure on the App (be it JSON or XML).
The added advantage of using a web service rather than a straight database connection is that you get encryption for free using https.
Hope that helps
There's a product called SUP (Sybase Unwired Platform), it provides a framework to handle access to databases but has the advantage that there doesn't need to be an online access all the time, it stores persistent data locally and then can sync up with the host database using messaging.