Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / General / December 2007

Tip: Looking for answers? Try searching our database.

asp.net vs. open source approach

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Bob Weiner - 12 Dec 2007 23:44 GMT
I am gettiner ready to start a project to create (yet another) social
networking site which will contain a mashup of local content, web services,
and open APIs.  I want the ability to easily update, or let others update
components as they become available.

I am struggling now between choosing between asp.net and a fully open source
approach to the project.

What do I need to consider?  Will I hit any limits (other than having to
host on IIS) by choosing asp.net?  Insight's will be much appreicated.

Thanks, bob
Michael Nemtsev - 13 Dec 2007 00:21 GMT
How asp.net and open source relates to each other?
open source is a type of licencing for your application, but it doesnt
relate to development tools

u can use any commercial tools and libs, for open source apps
Signature

WBR,  Michael  Nemtsev [.NET/C# MVP].  
Blog: http://spaces.live.com/laflour

> I am gettiner ready to start a project to create (yet another) social
> networking site which will contain a mashup of local content, web services,
[quoted text clipped - 8 lines]
>
> Thanks, bob
Peter Bromberg [C# MVP] - 13 Dec 2007 01:59 GMT
ASP.NET is a development Framework, not a licensing model. There are many
ASP.NET application that use the open-source approach.  I think you may be
getting hung up on semantics and definitions here.
-- Peter
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
MetaFinder: http://www.blogmetafinder.com 

> I am gettiner ready to start a project to create (yet another) social
> networking site which will contain a mashup of local content, web services,
[quoted text clipped - 8 lines]
>
> Thanks, bob
Bob Weiner - 13 Dec 2007 05:40 GMT
Yes, you guys are right.  I do understand the difference between the
development environment and licensing model; I worded my question poorly.

The project I'll be working on is for research.  Most of my content will
be contributed in the form of web parts (or something that can be
quickly converted to such) or mashed (is that a verb?) from the web
through publically available APIs.

Initially, I envisioned my site being built upon SharePoint because it
is a nice foundation for managing web parts and incorporating workflow.

A new idea came up today about creating our app as a portal to a set of
mashed-up public sites and doing as little development as possible.
That seemed like a good idea.

Upon later consideration, I had to ask myself, if we go this route, why
not go all the way and use linux, apache, mysql, javascript,
php/python/ruby/script-lang-dujour.  One clear benefit is having free
reserach replicability (SharePoint is nice but it ain't free).

So, if my end users are all going to access my site via  a web browser,
construct a web page from a web part gallery, which in turn use services
on the web then is there any advantage to purchasing Windows IIS,
SharePoint, Visual Studio, and the intractable number of CALs.

I hope this question is more clear to what I'm looking for.

Thanks for your replies.
bob

> I am gettiner ready to start a project to create (yet another) social
> networking site which will contain a mashup of local content, web
[quoted text clipped - 8 lines]
>
> Thanks, bob
Steve C. Orr [MCSD, MVP, CSM, ASP Insider] - 14 Dec 2007 02:29 GMT
Sharepoint is one thing, ASP.NET is another.  I understand your hesitation
to go with Sharepoint because of cost issues.  C# and ASP.NET, on the other
hand are essentially free and something very close to open source these
days.  And Microsoft provides free Express tools of good quality to make
development easy for everyone.

Signature

I hope this helps,
Steve C. Orr,
MCSD, MVP, CSM, ASPInsider
http://SteveOrr.net
http://iPhonePlaza.net

>I am gettiner ready to start a project to create (yet another) social
>networking site which will contain a mashup of local content, web services,
[quoted text clipped - 8 lines]
>
> Thanks, bob
Alexey Smirnov - 14 Dec 2007 19:32 GMT
> Yes, you guys are right.  I do understand the difference between the
> development environment and licensing model; I worded my question poorly.
[quoted text clipped - 41 lines]
>
> - Show quoted text -

Bob,

check this post

Enabling and managing social networks (for business use) with
Microsoft Office SharePoint Server 2007
http://blogs.msdn.com/sharepoint/archive/2007/10/24/enabling-and-managing-social
-networks-for-business-use-with-microsoft-office-sharepoint-server-2007.aspx


...but in my opinion SharePoint is a wrong tool for a social
networking site. It's a solution to everything, and you woudn't need
CALs for the internet version, but the main benefit of going to
Sharepoint is in the integration with Windows-based intranet
components: AD, Office 2007, Exchange... If you don't have all these
things - it makes no big sense to go with SharePoint, -  because there
is nothing ready out-of-the-box for the internet and you would need to
develop a custom application.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.