>>>>Hi,
>>>>
>>>>it looks like I am about to get a job developing a new system to administer an Insurance Company's handling of Life Insurance. I am looking at using .Net for this system, but am unsure as to what specifics I should go with. I have used CSLA.NET before and liked it so will probably stick with that as my "business framework", SQL Server will be my data store (I might consider PostgreSQL or MySQL). The application does not need to be accessible over the internet, but I would like the possibility to be there. I am leaning towards using Silverlight (CSLA.Net for Silverlight), but I am unsure of the advantages/disadvantages of going this route. Maybe Silverlight is too young/new? Should I go with ASP.NET instead?
>>>
>>>Stick to ASP.NET for a line of business application if you want it accessable over the internet. You have a mature framework, tools, controls, and development environment.
>>
>>Thanks William,
>>
>>If I want to have the option of eventually putting another type of UI on the application, say to make it accessible through a desktop application, is ASP.NET still the best way to go? In other words, can I develop my middle tier and data handling separate from the ASP.NET front end?
>
>Sure. One intriguing new option is SQL Data Services (SDS), a.k.a. SQL Azure. It is a version of SQL Server which will be hosted in the cloud rather than on a traditional server. It isn't fully baked yet -- it was only introduced last year -- but what Microsoft is saying is from a developer's standpoint it will be identical to SQL Server other than the connection string.
>
>Here is some info on it at the MSDN site -- http://msdn.microsoft.com/en-us/sqlserver/dataservices/default.aspx

Thanks Mike,

I think I have enough confusion in my head already :) If that's newer than Silverlight I'm not sure I want to be on the bleeding edge ;)