|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
why use .net?We need to retrospectively justify our choice in using .NET framework for developing our site. Our techie isnt here so we cant run it past him. Can some kind, helpful person run their eye over it and tell me if I'm tellling porkies, or if there is anything I should add? Why should people choose .net (I think ours is 1.1) Thanks Gay ****************** We recognised that in order to meet our aims of producing a high quality and consistent website, we had to ensure that our system was fast, robust and able to deal with a high number of users. We chose .NET framework so that we could meet these needs now, but also so that we could best account for any future developments in a cost effective manner. This has proved the case, in that with our Stage 2 developments we will be implementing a forum system. Using .NET has meant that we can integrate new modules with ease. With .NET's cross-platform interconnectivity, we feel that we have chosen the best approach for future-proofing. brazen wrote:
> We need to retrospectively justify our choice in using .NET framework for As a technical guy, I think most of it's BS, but expected BS. However,> developing our site. Our techie isnt here so we cant run it past him. Can > some kind, helpful person run their eye over it and tell me if I'm tellling > porkies, or if there is anything I should add? > With .NET's cross-platform > interconnectivity, we feel that we have chosen the best approach for > future-proofing. this line does raise a warning flag: the benefit of .NET is not "cross-platform interconnectivity" (cross-platform is more thought of as a Java thing), I'd lean more towards broad software ecosystem, i.e. there's a lot of code / libraries / components etc. available for the platform that you can leverage, with deeper integration than was possible in the past with technologies like COM etc. -- Barry "Barry Kelly" <barry.j.ke***@gmail.com> wrote: [.NET's cross-platform interconnectivity]> the benefit of .NET is not "cross-platform interconnectivity" I disagree - I think the .Net message here is the strongest of any platform > (cross-platform is more thought of as a Java thing), current on the market. With Web Services, WSE 2 & 3, and now WCF, I think .Net has the stronges cross-platform interconnectivity of any development environment out there. The work Microsoft has done with Sun & IBM over at OASIS on these standards has been nothing short of remarkable - and WSE 3 and WCF implement many of them. As things sit now, we can flow transactions (WS-Transaction), share security contexts (WS-Security), encrypt and sign messages (XMLSig, XmlEnc WS-Security), transfer large chunks (MTOM), and a number of other things. We can easily pull data from an LDAP server running on any platform (via System.Directory Services), and pull data from just about any Data Source (via ADO.Net). Add in support for FTP, HTTP, HTTPS, SMTP, and Sockets, and I think the overall picture becomes very, very strong. I don't think even Sun's newest Java implementation (1.6?) has that strong of an "out-of-the-box" message for cross platofrm interconnectivity. Now, if you're thinking "can run cross platform", then you're (obviously) right. The .Net message with Mono isn't anywhere near as strong as the Java cross-platform message. -- Chris Mullins, MCSD.NET, MCPD:Enterprise, Microsoft C# MVP http://www.coversant.com/blogs/cmullins
Show quote
"Chris Mullins [MVP]" <cmull***@yahoo.com> wrote in message Mmm I've actually added another block to it that I think covers that.news:OiitOBGiHHA.4064@TK2MSFTNGP02.phx.gbl... > "Barry Kelly" <barry.j.ke***@gmail.com> wrote: > > [.NET's cross-platform interconnectivity] > >> the benefit of .NET is not "cross-platform interconnectivity" >> (cross-platform is more thought of as a Java thing), > > I disagree - I think the .Net message here is the strongest of any > platform current on the market. > > With Web Services, WSE 2 & 3, and now WCF, I think .Net has the stronges > cross-platform interconnectivity of any development environment out there. > The work Microsoft has done with Sun & IBM over at OASIS on these > standards has been nothing short of remarkable - and WSE 3 and WCF > implement many of them. As things sit now, we can flow transactions > (WS-Transaction), share security contexts (WS-Security), encrypt and sign > messages (XMLSig, XmlEnc WS-Security), transfer large chunks (MTOM), and a > number of other things. > > We can easily pull data from an LDAP server running on any platform (via > System.Directory Services), and pull data from just about any Data Source > (via ADO.Net). > > Add in support for FTP, HTTP, HTTPS, SMTP, and Sockets, and I think the > overall picture becomes very, very strong. > > I don't think even Sun's newest Java implementation (1.6?) has that strong > of an "out-of-the-box" message for cross platofrm interconnectivity. > > Now, if you're thinking "can run cross platform", then you're (obviously) > right. The .Net message with Mono isn't anywhere near as strong as the > Java cross-platform message. > ************ Our website incorporates and displays different types of data from several different sources. Using .NET, with its web services cross-platform compatibility, makes this very easy and very robust. ************** Is that what you meant Chris? And yes, it is a lot of blah as thats about the scope of what I can do, it probably needs to be a bit less "dumbed down" but not so techincal that an assessor cant understand it. Gay Gay Using .NET framework is a broad term. You can use it, but I think you
should also mention that you will be using ASP.NET for website as that will the precise technology you will be using. And if your technical team approves you can even mention that you will be using AJAX (http:// ajax.asp.net/) for development. Also you can check out http://asp.net/ for more info about asp.net and also if you are interested to get some ideas from casestudies, then you can check out - http://www.microsoft.com/casestudies/ Regards, Sachin Palewar (Certified Scrum Master) Palewar Techno Solutions (Mobile Solutions for Your Business) www.palewar.com Show quote On Apr 27, 3:35 am, "brazen" <g***@removetheMtoobrazen.com.nz> wrote: > Hi there, > > We need to retrospectively justify our choice in using .NET framework for > developing our site. Our techie isnt here so we cant run it past him. Can > some kind, helpful person run their eye over it and tell me if I'm tellling > porkies, or if there is anything I should add? > > Why should people choose .net (I think ours is 1.1) > > Thanks > > Gay > > ****************** > We recognised that in order to meet our aims of producing a high quality and > consistent website, we had to ensure that our system was fast, robust and > able to deal with a high number of users. > > We chose .NET framework so that we could meet these needs now, but also so > that we could best account for any future developments in a cost effective > manner. This has proved the case, in that with our Stage 2 developments we > will be implementing a forum system. Using .NET has meant that we can > integrate new modules with ease. With .NET's cross-platform > interconnectivity, we feel that we have chosen the best approach for > future-proofing. "Sachin Palewar" <pale***@gmail.com> wrote in message Thanks sachin, I'll make the change.news:1177661796.804067.44150@r3g2000prh.googlegroups.com... > Using .NET framework is a broad term. You can use it, but I think you > should also mention that you will be using ASP.NET for website as that > will the precise technology you will be using. And if your technical > team approves you can even mention that you will be using AJAX (http:// > ajax.asp.net/) for development. > > Also you can check out http://asp.net/ for more info about asp.net and > also if you are interested to get some ideas from casestudies, then > you can check out - http://www.microsoft.com/casestudies/ > Gay  |
|||||||||||||||||||||||
Other interesting topics