Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
What is difference between Windows Sharepoint Service and MOSS (Microsoft office Sharepoint). If I have the WSS 3.0 installed in my machine, I can create a sharepoint site, using Sharepoint Designer and Inforpath. Then why do I need MOSS 2007 (WSS 3.0 being free for download).
A lot of the added functionality (and improvements, seemingly specifically with Search at least) are gained from MOSS2007. Have a nosey at the full feature comparison on the MS site for further details maybe.
http://office.microsoft.com/en-us/SharePointtechnology/fx101758691033.aspx
Specifically, I think the Workflow and document management improvements are where you may get your 'wins' from. With a bit of a setup overhead initially, it can replace a number of otherwise complicated collaborative tasks which require a number of people.
SharePoint Services provides many features not included in WSS, some examples being Web Content Management (Publishing) and Enterprise Search.
MOSS also enables you to specify audiences for your lists. Which is quite useful in an enterprise environment.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I'm a .NET developer working in Australia. I'm planning to switch my career from .NET to Sharepoint or CRM. Any suggestion please which application has better market and what is more suitable for a .NET/web developer.
Thanks
First i would say that the market for SharePoint is bigger than the market for Microsoft CRM. Nearly every Enterprise Company has SP implemented, some smaller other larger. This is my opinion.
Good CRM developers and consultants are hard to find. Therefore you would have a good daily rate when you work as a freelancer. I dont know the learning curve for CRM development.
On the SharePoint side its the same. Here you will have many developers out there but only a few which are available. We are currently seeking for about 1 year for good SharePoint developers, but could only find 1 good Junior level consultant. Currently it hard to find good experienced SharePoint developers.
But the SharePoint world is currently changing from OnPremise to Online. Many customers are thinking about Hybrid Scenarious. You would have to learn both worlds. Cause the things which are available in one world are not automatically available in the other world.
If you are a good developer with Web Development experience, then i would prefer to learn SharePoint, but its a wide system from SQL Server over IIS, SharePoint internal functionality like Services, OOTB Functionality, Server Side API, Client Side API, different Solution Types (App Model, Farm Solutions, etc.), huge differences in the versions, Workflows, Search, and many many more ...
Its nothing what you could learn in the next 6 month. If you prefer only to configure these systems, using OOTB functionaly to customize those solutions, than you will be one of many and the changes to get a good job or project will be smaller.
I think its a good chance for a .NET developer to learn additionally CRM or SharePoint. That would increase your knowledge, quality and market price. Its always good to have a look outside the box. Its a good combination. The one does not exclude the other.
Its hard to answer your question in some words. I hope, that i could give you a some idea about that. That all my personal experience and opinion.
I found a good article by Mark Rackley called How do I become a SharePoint Developer?. An incomplete list of SharePoint Ressources you can find at BOGAZCI | Sharepoint Resources.
Good starting points are always MSDN pages like
SharePoint 2013 development overview
Getting Started (SharePoint Development in Visual Studio)
and SharePoint general development
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
How to localize a Sharepoint 2010? There ara some problems with content localization, because different localized pages use same lists.
For localization of SharePoint interface, recommended approach would be to use Language Packs, that you install on top of your SharePoint server:
SharePoint Server language packs
the deployment procedure
Take note, you need to install SharePoint Foundation Language Pack in desired language before you install Language Pack for SharePoint Server.
For content localization, approach depends on the nature of your site and site template you are using. For example, if you are creating SharePoint Publishing Sites, there is an concept known as "Variations" that you can leverage for achieving localization of sites. For other templates, like Team Sites, you need to be creative, and perhaps create columns in your list that could contain appropriate content in each of your desired language.
This might also be of help: Localizing SharePoint Solutions
I hope this answers your question?
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I am moving a system from Microsoft Crm 4.0 On Premise to Microsoft Crm 2011 On Demand (hosted). What is the best way to migrate all of the data? Is there a data mapping built in for that or any tool recommendations?
There is no dedicated tool for migrating an on premise organization to Dynamics CRM Online.
The first step of such a migration would be an upgrade of your local system to Dynamics CRM 2011. This ensures that you are on the same customization level.
For the migration itself, you could use for example Scribe or you could script it by yourself. This should be rather "easy" as you only have to transfer the data. The data structure itself, remains the same.
We've just completed the development of a tool which automatically manages the transfer of data from a CRM 2011 On Premise database to CRM Online. We're in the process of making this available publicly, in the mean time if you're interested then please contact info#synchronicity-systems.com
UPDATE: Our software is now available for download, for more information check out the website here http://www.synchronicity-systems.co.uk/echo/
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
In your experience how does SharePoint as a back-end Document Management Solution (archiving included) stands compared to other proprietary document management systems.
Is it any comparison analysis out there?
One of Sharepoints main features is document management.
In my opinion, its Document Management features and its lackings:
Great metadata, integration only with msft tools, no built in functionality to capture paper docs, strong indexing, uses SQLServer as storage platform but lacks on serious document archiving, not great search and filtering, item level security, decent work flow capabilities, strong on versioning and collaboration.
SharePoint 2007 excels at being a document management solution because of it's tight integration with Office 2007. From inside of Word/PPT/Excel you can save, check out, check in, add custom fields to your SharePoint list, etc. Your non-technical users will get it pretty quickly. It can also be very nice for letting your super users create and manage their own department portals.
Things it doesn't excel at: Being an application platform.
I agree that it is a poor application platform. The database contains tables that are basically textfield1, textfield2, numericfield1, numericfield2, numericfield3...Blecch. The API is opaque. The web-facing server product is expensive. At my current employer, we considered Sharepoint, but dropped it in favor of an ASP.NET solution, since we only needed rudimentary document management capabilities.
One of the major benefits, if it is an internal application, and you can mange with Windows Sharepoint Services, is it's "free".
As an application platform Sharepoint development can be less productive than ASP.net, depending upon what you are doing.
You can however combined the two. Build your UI in ASP.Net, then call Sharepoint functionality via web services when you need it.
Here I found two very interesting case studies.
Real life document management
A Microsoft case study
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
Now that Microsoft has started giving us a glimpse of what's going to be in SharePoint 2010, I would like to know what you think is going to be the most important feature of SharePoint 2010.
Please include some information about your relationship with SharePoint (End-User, Super-User, Administrator, Developer, ...)
More refined VS integration!
The developer Dashboard looks VERY promising.
As a developer: Standards compliant HTML output!
As a developer i like the client side API and LINQ, but i guess the end users will find more use of what i could do with the new business data services.
So far I'll say that the updated BDC is the most important feature but since integration with 3rd party applications is my daytime job I might be biased
Have not seen how deployment is handled in 2010. But anything that would improve the deployment experience would be very welcome.