CODEWITHSUNDEEP
asp.netsilverlightenterprise
user39880
user39880

Reputation:

Once again, Is Silverlight 4 Enterprise ready?

Does Microsoft use or plan to use Silverlight in its own web applications like MS CRM? Is there any known risk for Silverlight LOB applications instead of ASP.NET? Silverlight 4 still does not has wsHttpBinding. Is this a stupid question?

Upvotes: 0

Views: 523

Answers (5)

Grigori Melnik
Grigori Melnik

Reputation: 4107

Microsoft is also working on the Enterprise Library for Silverlight to support LOB developers.

The backlog is available for public commenting and voting here: http://entlibsl.mswish.net

Upvotes: 0

Steve
Steve

Reputation: 387

Why does Silverlight make sense? (rhetorical question)

If intranet, then just use WPF - the old arguments of deployment issues don't really stand with .net 4.0 ?

If internet, then you'd not use it - using a plug-in just makes no sense anymore - use asp.net in that case... you don't really want users - especially coming to a LOB site to run away because they have to install a new plugin - too risky!

I'm not sold on Silverlight - it's a subset of the framework and outside of a smaller .net install really doesn't provide what users want. Why not get the whole thing vs. a subset?

ie. users on the web are used to a certain web behavior - and Silverlight feels more like a glitzy plugin than a true web application.

Upvotes: 0

Doobi
Doobi

Reputation: 4842

Microsoft are working on controls for dynamics http://code.msdn.microsoft.com/mscrm4/Release/ProjectReleases.aspx?ReleaseId=203

They're building the UK NHS CUI with it: http://www.mscui.net/Showcase/Showcase.aspx

And it's the core runtime for Windows Phone 7, so I figure it's Enterprise ready ;)

Upvotes: 0

Ken Smith
Ken Smith

Reputation: 20445

Silverlight 4 finally has most of the stuff that I'd be looking for in an enterprise application. You can print (at last!), you've got decent data and web service access, and the tools (VS2010 and Expression Blend 4) are more-or-less in place. Managing and troubleshooting your data bindings is a little easier (though not nearly as easy as it should be).

That said, you still have to choose between WPF on the one hand, and ASP.NET/MVC on the other, with Silverlight being a sort of middle ground. Unless there was a specific reason to do it otherwise, for most enterprise applications, Silverlight would be my choice. Creating a great UI with JavaScript/HTML/Ajax is still harder than C#/Silverlight, and WPF doesn't generally offer anything that you can't get with Silverlight and a little bit of cleverness.

Upvotes: 1

Cylon Cat
Cylon Cat

Reputation: 7201

Not a stupid question, but you do have to remember that the cost of rewriting an application (any application, for any reason) is very expensive.

Yes, I think Silverlight 3 and 4 are enterprise-ready. There's still a learning curve, especially with services and managing performance for large applications that may need dynamic loading. But Silverlight has arrived, and I think you'll see more and more of it.

Upvotes: 2

Related Questions