I was wondering if anyone has built or know of a decent forum package for Umbraco 4.03??
I've had a little play with this but its a bit basic
http://our.umbraco.org/projects/umbraco-forum-package
and
http://our.umbraco.org/projects/uforum-basics
I've found this article on how to integrate YAF forum but would rather have one which fits a bit better..
http://dawoe.blogspot.com/2009/02/intergrate-yet-another-forum-193rc2.html
Of course I know one answer, write or extend one of the above :) Any help would be gratefully received.
uForum is used to power the Our Umbraco community - so that's the current recommended forum package.
YAF is a fully-featured forum/bulletin-board web-application, which can be integrated with Umbraco (using an ASP.NET Membership Provider). Aside from that YAF is standalone.
Update: There is a new package called nForum.
I guess it depends on your requirements.
What features are lacking, clearly you know what you want so any guidance on what the forum should include will help.
Pretty much any asp.net based forum software would work with Umbraco. I guess the main thing would be the integration with the Membership provider in Umbraco. In this case Any forum software that could use a custom ASP.NET membership provider would integrate pretty much seamlessly.
There are plenty of opensource and commercial forum packages available for ASP.NET, just find one that matches your requirements and look at integrating it or running it alongside Umbraco.
Related
When I found the OWASP Secure Coding Practices Guide, I felt like I had found a hidden gem. The information in the checklist format is great. Although I was disappointed to see that links pointed to multiple other external projects is not found and the artifacts for them just do not exist. So pointing it here hoping anyone has more information on them.
Implement a secure software development lifecycle - OWASP CLASP Project: Returns page has been deleted
ESAPI for Php link on OWASP Enterprise Security API project returns nothing
I am unsure how to find or access these.
After digging around I did find ESAPI Python Readme.
As for the OWASP CLASP Project, it looks like that project has been removed due to inactivity (these projects are maintained by volunteers) and now outdate/wrong information.
Depending on what you are looking for, I suggest look at the OWASP Project Inventory. This lists out all of OWASP's projects.
The CLASP project is no longer supported. It has been supersed by the OpenSAMM (http://www.opensamm.org) project who can give you all the things to setup a good and efficent SSDLC (Secure Software Development Live Cycle).
Anyways, as the OWASP projects are movings, i suggest you to point all the time to the home page to have a good and updated view
I've been tasked with creating a documentation website for some services that we expose externally. Part of my task is to find out what the best base software would be to build this site. One of my specific objectives is to determine whether or not the Liferay Portal software or its plugins are suitable for building what is primarily functioning as an API documentation website. It seems like Liferay is meant for more content-driving applications, such as news, wikis, blogs, etc.
If Liferay is suitable for this task, are there any pointers on what the general layout should be for the site?
Liferay itself is proving to be rather complicated to learn, so I figured that it'd be better to figure out if I'm wasting my time or not before really diving into learning how to use it.
At the same time, are there any better, non-commercial alternatives?
Thanks!
I am creating web portal using Liferay and I implemented a simple document browsing page. I was using amazon java libraries to accomplish that and it was quite easy(just download all of the jars, include them in your portlet library folder and AWS(AmazonS3) is ready to use). On the other, the programmatic part of creating this portals with Liferay is quite a lot. I suggest you if you don't like programming to chose another software :)
I hope this was helpful! Its just an advice not a concrete answer.
Good luck with developing your website :)
I was wondering if there is a website that helps with giving you a checklist for your web app, to make sure you don't miss anything!! It could be very tedious when building a large project by yourself! obviously nothing specific, just a guideline for a web app. thanks
This doesn't necessarily work for all projects, but it's a great start!
http://launchlist.net/
In light of your comment below, I recommend
http://goplanapp.net
it's free and open-source and allows you to create project milestones, have ongoing discussions on various issues, and alot more.
Trac is a website driven software that allows you to set milestones, reports, svn browsing, priorities, bug tracking, and wiki's. A lot of active open source projects use it to host their software. I use it extensively for each client project I start.
I like http://kanbanery.com/ alot.
It allows you to have tasks with subtasks, add info, attachments, comments, etc to a task and you can arrange those in multiple columns.
(I know it is targeted at scrum / kanban teams, but the app can be tailored to make it fit for your workflow)
I have a development team specialized in ASP.NET. So the solutions we provide are web based, running on IIS and using MS SQL server. Everything within the intranet of the company. The team has this expertise, and they are excellent in C#, and .Net in general.
The company is deploying SharePoint MOSS 2007. This deployment is part of a project that I am not involved in, and for which I have very little information. However I know that they have established the "thinkers" layer (those who will say what to do), the integrations layer (the who will configure, deploy and manage the production), and that they need to establish the so called development layer (those who will do things the other two can't).
I am asked to evaluate the possibility to increase my team's expertise by adding SharePoint development. This is the easy part, I just have to find the required training and send my people.
However these days the word development could mean a lot of things and sometimes I discover that configuration is used in place of development.
I don't have any objections to evolve the team by developing new expertise, but I want to be sure to keep things stimulating for my developers.
Secondly I don't want to say that we have SharePoint development expertise, and actually what we do is just modifying css or xml files. Also, I don't think that using wizards to produce a solution is the best path to push a C# developer to follow.
The questions I am asking myself first is : what is the background of a SharePoint developer? how could .Net developers feel if asked to become SharePoint developers?
Any thoughts will be greatly appreciated.
I started in Sharepoint development over a year ago when I inherited a WSS 3.0 solution at my company.
Personally I think it was a great step for me getting to know Sharepoint development a little, there are a lot of problems (e.g. security, load – balance, ghosting) that was good to see how was solved by the WSS team and helps me solve problems in other solutions I‘m working on. But I don‘t work on WSS solutions full time, so others have to anwer how it is working with WSS every day.
WSS and Sharepoint are an extension on the ASP.NET platform, so any experience in ASP.NET and .NET in general should be a good foundation for a developer that is starting creating Sharepoint solutions. I read the Inside Microsoft Windows Sharepoint Services 3.0 book in order to get the basic concepts and wss solution architecuture before I started working on WSS projects.
I quickly found out that you have to have a Virtual Machine environment for Sharepoint development, this is because it‘s a pain working on a client and attaching to a remote process on the server to get in debug mode. Therefore I recommend creating a MOSS virtual machine that has Visual Studio installed that has access to your source control system. Develop solutions on that machine and when finished then check into source control.
I also recommend looking at development tools, such as stsdev and wspbuilder to help you building your solution, these will ease you development process quite a bit. There are also quite a lot of tools available on the web, e.g. codeplex to help you out.
Sometimes it can be a pain developing these solutions, changes can require recycling the IIS pool or a brute-force IISReset, error messages can sometimes by a little cryptic and so on. But you quickly catch on and know where to look. Sharepoint also helps you out a lot, I‘ve had millions of questions from clients that can be solved with standard out-of the box web parts, so that I don‘t have to code anhything to keep my clients happy :)
Sharepoint also expects solutions to be coded in certain way, e.g. 12 hive filestructure so it helps you standardizing your solutions.
There is a serious lack of documentation, so that you have to rely on Reflector and such tools a lot, just to know what is happening within the framework, hopefully this gets better with 2010.
The initial learning curve is high, and a lot of new concepts an technologies to learn ,e.g. Workflows within sharepoint, featuers, ghosting and code access security
There is a lot of Xml configuration that sharepoint uses that developers have to learn, this includes the site definition, list templates and more. There are sometimes days when I‘m stuck in Xml edit mode and can‘t figure out why things don‘t work as they should do
These are just few of my thought, I‘ve been working mainly in WSS development and it would be great if someone could comment regarding web part configuration in Sharepoint, e.g. configuring the search. Which is something I haven‘t been doing a lot of.
From what I have heard around, the SharePoint is a popular technology from the customer point of view, but an object of hatred among developers.
Nice to see you noted Dev and Admin being used "incorrectly".
Although Developing for SharePoint could be purely that, development, like creating webparts etc., I strongly encourage you and your team to get to grips with SharePoint deployment, installation and configuration as well. I am fully SharePoint Certified (WSS Config/Dev and MOSS Config/Dev) and having knowledge of both ends has been invaluable for me.
Knowing what is configured where will help in debugging and troubleshooting along the way. I suggest taking an MCTS WSS 3.0 COnfiguration training / and or a MOSS Config training for at least 1 or 2 of your team. The rest of the team will pick up the essentials as they go along, having those 2 certified colleagues as go to guys concerning config and admin.
IMHO, being a sharepoint consultant entails knowing how to create a piece of functionality as a dev and then being able to deploy, configure and maintain that piece of functionality as an admin (or at least an informed end/power user).
Albert, take a look at this other thread titled Is a sharepoint developer technically “equipped” to do custom app dev and vise-versa. There's quite a bit of info in there about what's involved in making the leap from pure .NET to SharePoint.
My co-worker is studying SharePoint at the moment. Making fun of him all the time. Frequently he gabbles something like "wtf is that??!!". And then i feel a bit sad, because i know - there's a probability that i'll have to learn that stuff too (i guess it's not so easy to get projects nowadays).
I see it more as configuration and customization than software development (something like hunting down fing checkbox for 3 days in a row). You pick up some clay through those crazy sharepoint designers and then endlessly customize it.
For everything i know already - there's a new name (i.e. - spGridView) and unexpected behavior underneath.
Html that gets rendered is bizzare (tables and bunch of serialized viewstate everywhere).
But those configuration xml`s... o_0
Now that's a hurdle i can't get over. Even hardcore SQL stuff starts to seem like a childish game.
Maybe i'm wrong, but as i have heard - Microsoft developed 'spatial columns' (let's you expand count of columns for tables over thousandsomething) for sql mainly because of Sharepoint. That terrifies me.
Of course - my opinion is HIGHLY subjective and a bit offensive. But i hope that helps to better reveal what i think & feel about Sharepoint.
Hopefully developers you are working with sees this different.
In short:
No. I wouldn't like to become a sharepoint developer.
Edit:
I could handle that initial complexity. But the main reason i don't want to - i don't think that development in Sharepoint is the right way to go. I mean - lately people discuss that webforms provides too much abstraction. Then what to say about Sharepoint?
To be a successful SharePoint developer you must have a high threshold for pain and the patience of a Buddha.
thank you all for the answers, they are all really helpful.
from what I read here, I see two things to consider.
First is the context of utilization which I think is an important factor. In some places SharePoint "development" could go very far, and could involve developing really exciting things, in order to satisfy new customers' needs. it could involve writing code and so on. And in some other places it could be just administration and configuration, in order to maintain already established solutions.
Secondly is the personal motivation. It really depends on the person. Some .Net developers with good experience, will prefer not to go in a direction, where they will not code the "SharePoint way", and will like to write code in C# or some other languages. However there will be others that will choose this path and will be happy to have such careers. They will be motivated and thus propose really nice solutions.
For example, from my personal perspective and if I had stayed in development and programming, I would not choose SharePoint development using high level wizards and menus,as a progress path for my career. Even though I am not doing it these days, I still enjoy coding, compiling, debugging etc, but this is just me.
I am a junior developer and I have just graduated from university this year. I am working private with some people and I have just been given a music website to develop using DotNetNuke. I have a some experience using DotNetNuke which I have gained making small modules that take care of certain functionality on a webpages but I have never taken on a whole website before. I would love it if some one would give me some guidence on how to approach this project and answer some of my questions.
What are the steps involved in developing a dotnetnuke website?
How different is it from a developers perspective to develop a dotnetnuke cms website from a cms website which was developed from scratch?
When it comes to the database do you add tables to the database incrementally as you develop new functionality or do you plan everything in advance and create tables and stored procedures at once?
What are the steps involved in developing a dotnetnuke website?
Pick your version (if you're starting now, pick 5.1.1)
Installation (use Source package locally, Install package everywhere else)
Settings Configuration (performance, security, user info, etc.)
Adding & configuring core/third party modules
Adding & configuring third party skins
Custom Extension (typically module or provider) Development
Custom Skin Development
How different is it from a developers
perspective to develop a dotnetnuke
cms website from a cms website which
was developed from scratch?
Very. When you're starting with an established CMS you're inheriting solutions to tons and tons of solved problems. In the case of DNN, you have a substantial framework at your disposal. The focus will be more on learning and leveraging the existing API/features. If you're starting from scratch you're providing that foundation yourself. Using an established CMS is not necessarily better than the other - it depends on what you're trying to accomplish. If you require fine-grained control over everything and you want a great learning experience, rolling your own may be the best way to go.
When it comes to the database do you
add tables to the database
incrementally as you develop new
functionality or do you plan
everything in advance and create
tables and stored procedures at once?
No matter what your project is, I'd suggest doing things as they are needed and not before. I think "doing everything in advance" would be impossible/horrible anyway. The heart of this question is really going to be defining your development process - I don't think this would necessarily be any different than in other projects. I like to define the features I want, organize them based on their relation to each other (which should come first due to dependencies, etc) and start implementing them one at a time and give each one the attention it needs.
You may also want to look into Lee Sykes' tutorials on module development using OpenWebStudio. However, I'm more on the design end, mainly just skinning, configuring, SE optimizing sites and matching client needs to our library of licensed 3rd party modules. However, the DNN community is VERY supportive and VERY helpful. There are some great resources out there, and I've found several blogs by the core development team to be essential for helping me wrap my head around the DNN framework.
Keep with it, and don't be scared to ask questions.
References:
www.dnncreative.com - Lee Sykes' Site, many tutorials on the how-tos of the DNN system. It's well worth the yearly subscription IMHO.
www.dotnetnuke.com - The main site for the DNN community
www.snowcovered.com - Central (AFAIK) site where many module developers sell their products, everything from skins to modules.