>>>>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?
>>>
>>>It's not neccessarily an either/or decision since you can host Silverlight content in a ASP.NET application.
>>>
>>>Also (at the risk of riling Bill :-} ) you could look at developing the desktop application using WPF - it should then be possible to port a lot of the code base to Silverlight if the need arose....
>>>
>>>Regards,
>>>Viv
>>
>>Thanks, I obviously need to do some more reading to fully grasp all the technologies involved. I am thinking of doing the web app first and then porting to a desktop, so I guess the silverlight stuff would then be easy to move to WPF (or can't Silverlight run as a desktop app anyhow, so maybe that is an advantage of going with silverlight??
>
>From you original post I got the impression that this was initially to be a desktop app ?
>Anyway, I've done very little with SilverLight, but it seems generally accepted that, since it is a 'subset' of WPF it is easier to port SL code to WPF than porting WPF to SL......
>
>Here's a link that compares feature support in WPF and SilverLight:
>
http://msdn.microsoft.com/en-us/library/cc903925(VS.95).aspxYes, I probably didn't state very clearly what I want to do initially. Basically it does not HAVE to be run using a browser, but I would prefer it to be.
Thanks for the link.
