i am working on a web application that now requires a CMS.
Could you suggest me a product that grant integration with my existing application.
The latter is implemented using .Net framework 3.5 Linq to sql and SQL Server 2008
I may consider even not open source product (affordable price)
i want to create a Master page and allow the application's users to modify the content.
Ideally give them the ability to add controls such as image sliders (but this is not the main scope)
Main objective is the ability to modify the content usually text. Bu more is always better........
Thanks
http://n2cms.com/ is very powerful cms that can be integrated with your application.
http://www.dotnetnuke.com/ is a good open source choice.
Graffiti is now Open Source. I'm not sure how it integrates with an existing application.
SharePoint is the obvious answer, considering it's an ASP.NET application itself. It's free with Windows Server 2003 or 2008.
Umbraco is fantastic and free. Allowing you to integrate many plugins. If you are a developer you will probably fall in live as it offers a lot of integration.
DotNetNuke has a great (if not long winded) video intro and online demo so you can see how it works.
Related
I am using a free account in somee.com.
I have few queries related to this.
How can I configure and view the style components of telerik on web.
(if someone tried) Where can I find IIS settings in somee.com so If I want to modify anything there.
If you guys have any information about free asp.net hosting sites/server so please share.I am a student and I want to try website which was build in asp.net
How can I configure and view the style components of telerik on web.
Telerik RadProgressArea requires Full Trust level.
As long as you do not use RadProgressArea, it should be fine with most share hosting site.
If you have questions regarding server, you can ask at Server Fault.
Googling did not result any useful answers so I'm trying you.
Has anyone out there ever done an integration of a Sharepoint Blog into an ASP.NET web application? Or, do you know of any sharepoint web services available for retrieving and updating sharepoint blog content? Any info is appreciated.
Sharepoint is MOSS 2010
The web application is a sitecore intranet
portal 3.3 but this may be inconsequential
There wouldn't be a simple solution to this, however here are a couple of approaches you could explore:
1) Consume the SharePoint Blog RSS feed in your .NET application to get the blog posts
2) Use the SharePoint Client Object Model to interact with SharePoint via custom code. Using the object model (through C# or VB) you could create new posts (which are just list items) as well as retrieve them. Here is a good place to start on writing custom code with the Client Object Model: http://msdn.microsoft.com/en-us/library/ee857094.aspx
Check this open source web part
http://www.bendsoft.com/downloads/sharepoint-web-parts/sharepoint-blog-reader/
It would be very simple to convert to generic .net usage, contact Bendsoft at their forum (http://forum.bendsoft.com), maybe they will help you with some of the work. It isn't very difficult when using a connector.
The solution is compatible with both SP 2007, 2010 and also feature versions like 2013.
We need to select a CMS for our company's website which will allow the designers to make changes to the pages, add pages, view and publish them.
We r using Visual Studio 2010 for web development and includes Global.asax, Masterpages, User-/Custom-Controls, Security (FormsAuthentication, custom Membership-/RoleProvider). W ehave SQL server 2008 for the DB.
I have looked into various CMS like Sitefinity,N2CMS, Umbraco, DotNetnuke. We kinda liked playing with the demo of N2CMS. We don't want to start developing the site from scratch. We want to integrate some CMS into our application for the designers to use. However, I can't find any helpful documentation regarding the integration. Everyone starts talking building from sctrach. The documentation for N2CMS seems so outdated.
If anyone can guide me how to set a CMS into exsiting application, I will really appreciate it.
Thanks
I want to build a custom document management web application that ties in with sharepoint for the actual document versioning and storage. I'm hoping for something like a sharepoint widget that I can plug into my web application that would allow me to tie in with sharepoint and download documents, make edits to them, and upload them back to sharepoint, with sharepoint handling all of the versioning and storage.
Basically I'm looking for a sharepoint API.
If WSS is the answer to this, are there licensing issues that I need to consider?
Thanks.
The best way forward is probably to use SharePoint's web services as that way your application can run on a server that doesn't have SharePoint installed.
Regarding Licensing, as long as you are licensed for Windows Server then WSS is free. However, depending on what database you use you may need to make sure that your users are licensed for SQL Server. Have a look at these links:
SharePoint Connections
Technet
Eggheadcafe
Wouldn't it be easier to do some development to customize SharePoint to your needs instead of just using it as a backend?
If it's SharePoint 2007 you're talking about, then on the server side you have the SharePoint API (Microsoft.SharePoint.dll) and on the client side, SP provides web services for manipulating lists, libraries, users and most other things you might need.
As Jeremy said, getting data to and from SharePoint through the Web Services, requires you to write CAML queries, but it's made easier by the help of tools such as this free CamlQueryBuilder
There's loads of documentation on both the API and the web services online.
If you're planning on using SharePoint 2010, all this will be quite easier, as more options are available for developers, e.g. API for the client side as well as the server side. Also new in 2010 is LINQ for SharePoint, which IMO really rocks!
Sharepoint is accessible with CAML Queries in that you can create, modify, and delete any object in Sharepoint with this.
You could create your own front end and just communicate to sharepoint.
As far as licensing, WSS comes with any Windows Server OS, so your client would just buy a license to the OS and be fine.
I'm new to developing in SharePoint and would like some tips please. I want to develop a WebPart. I understand that I effectively need to do this on a machine with SharePoint Server installed and create the web part as an ASP control. Once the control is created, how do I link it into SharePoint?
I would recommend you to take a look at the WSP Builder extensions for Visual Studio. It will simplify the development and deployment process for you, since it contains both templates for web parts, features and it will also package it up in a WSP solution for you.
I would read though this:
http://msdn.microsoft.com/en-us/library/ms452873.aspx
It will answer a lot of your questions about creating a web part, deploying etc.
If you're using the Microsoft Provided WebPart Visual Studio template...it will automatically be deployed to your site when you build it.
If you need to deploy to a test/production environment, you need to create a SharePoint Feature and then deploy the Feature to the server.
http://www.allaboutmoss.com/index.php/2010/03/22/hello-world-sharepoint-webpart-for-beginners/ helps you to create simple webpart and shows how it deploy in server.
You are able to build Web Parts in a number of different ways, through Visual Studio .NET using either the SharePoint Web Part Namespace or the normal ASP.NET Web Part Namespace further you are able to build Web Parts in SharePoint Designer using a combination of different technologies, such as XML Web Services.
XML Web Services will allow you to hook directly into SharePoint using SharePoint's Native Web Services, you can then create a Data View Web Part which will enable you to view, collate, filter and group List Items. This, of course, will also allow you to mingle normal HTML as well as XSLT syntax, allowing you to build logic into the Web Part.
The good thing about doing it this way is there is no "real' coding, i.e. no Code Behind page etc as there would normally be in ASP.NET. This also allows you keep things more or less SharePoint Centric, which is important because you may or may not have access to Central Admin or SSP nor indeed the Server itself, the 12 hive or the GAC.
How you decide to develop Web Parts should include thinking about all of the above, you may have a very restricted development environment. Further, you can also use Namespaces provided directly from GAC assemblies provided by Sharepoint, you may either need access to a development environment which has a MOSS or WSS Server on it or the PIA's or Assemblies from a MOSS/WSS Server.
I am a software developer, however, it is important for me to develop applications which are as SharePoint centric as they can be, which is why I decided to develop my Web Parts in SharePoint Designer. However, there have been times when using full VS.NET is the way to go, I would suggest you look at SharePoint Designer first, get a feel for the interface, XML Web Services, XSLT and HTML once you have created a SharePoint Designer Web Part and Provided this Web Part exists within a Web Part Zone, you can export the Web Part and reimport it into any number of Site Collections.
I must add that the above relates to SharePoint Lists and Libraries but it gives you a grounding to understand how it all fits together. it helped me understand more and made development of more coded Web Parts easier, It may not suit your individual requirements, SharePoint is a huge environment offering many paths.
Hope this Helps you out, search for SharePoint Designer... at least as a starting point.
Cheers