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
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 5 years ago.
Improve this question
I had a lecture in college which shortly focused on cloud computing.
When seeing through the material, I found the professor categorized Microsoft Azure as Platform-as-a-Service.
In Addition to that, I recently gave a presentation which also partly focused on Azure, and afterwards was asked which of the three models (IaaS, SaaS or PaaS) Azure would belong to.
I replied that it offers solutions for all three models and therefore, a categorization cannot be limited to just one of the models. My professor (a different one than before) said I was partly wrong, classifying it as PaaS with additional possibilities for IaaS and SaaS.
Wikipedia also lists Microsoft Azure as an example for PaaS.
Question: Can anyone tell me why Azure is just sort of "labeled" as PaaS?
Just to clarify: The presentation I gave was some sort of oral exam with viewers, I did not have the guts to start a discussion with the prof evaluating me.
Your professor was right, especially with the statement "classifying it as PaaS with additional possibilities for IaaS and SaaS." As you said yourself, Wikipedia also lists Microsoft Azure as an example for PaaS. It comes down to this. SaaS exists on top of an underlying PaaS. What makes Azure a PaaS is their data centers allowing you access into it plus Azure Active Directory authenticating and authorizing into it on top of it. Without these you could not deliver the SaaS model such as Office 365 which sits on top of it. Microsoft Office 365 is a SaaS offering, built on top of Azure. When I interviewed for a Microsoft position a few years ago, I was asked what was "Azure"? I actually missed this question, because I wasn’t up on Azure at the time. The correct answer told to me then was "cloud platform". So there you have it.
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
I have an Excel spreadsheet and I've been tasked with displaying the data in an interesting way and adding some interactivity. I am trying to choose between creating an App for Office or using VBA macros to enhance the spreadsheet. What technology makes the most sense for my situation?
I am using Excel 2013 and Windows 7 (All users of the spreadsheet have the same environment).
I am not a software engineer, though I have some programming experience.
I do not need to access any external services (database, web API, etc.).
I do not need to access any Office documents besides the spreadsheet.
I need the code to be easily distributed along with the document.
The code needs to be available offline
I do not have Visual Studio
Primary concerns:
Ease and enjoyment of development
Ease of manipulating the spreadsheet (I am concerned that I won't have as much control over the document with the Apps for Office Javascript API)
Ease of distribution (I will not be able to setup an app store within my organization)
Attractiveness and usability of the end product
Availability of resources and documentation
Ease and enjoyment of development
this will initially depend on what you are used to: if you are familiar with the OO environment, then stick with VBA. likewise, a Java/web background will see you settle into the Apps environment more quickly
Ease of manipulating the spreadsheet
I can't speak with experience of using Apps for Office, but I can theorise that MS Office will prove to be a far more feature-rich, stable and integrated development environment for some time, if only because it's already been around for 20 years.
Ease of distribution
MS Office add-ins can be fiddley to manage if users are not based on a single network, but this has long been the case and there's plenty of solutions/work-arounds published on the web
Attractiveness and usability of the end product
unless you are going to start retailing the product, I think MS Office is more than viable here
Availability of resources and documentation
again, there's 20 years-worth of forum discussions, blogs and expert solutions for MSO at your fingertips, for free
Also, I believe the MSO software license is a one-off overhead, whereas Office 365 etc is subscription.
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
I'm looking to set up a small site for a friend that has some widgets they want to sell online. I don't think I will have much time for maintenance once it goes live (for that matter, I don't expect I'll have much time for initial setup and configuration), and I am looking for something that is dead-simple for a non-technical user to maintain (financial/payment info, add/remove/change products).
The second most important part would be good integration with a payment provider. I'm not too fussy what language it's in if it meets my other criteria (if I don't know the language I will learn enough to get the site running).
Also important is that I'd prefer to stick to open-source products, mostly because I don't think this project will have much of a budget for high-end commercial products (at least not until it makes some sales).
The last time I did this sort of stuff we were building custom sites from scratch for clients with very specific needs. I do not have recent experience with the current generation of blogging tools (Wordpress, Joomla, etc...) and I don't really know which off-the-shelf combo of platforms and plugins are best to get something up and running in as little time as possible.
Hosting your own online store is a full-time occupation, no different from running your own brick-and-mortar store. Anything that accepts online payments will be targeted by criminals for online fraud.
If your business is selling widgets and not running online stores, I strongly, strongly suggest using a hosted service with its own web integration and payment handling. I know people who have used both Weebly and Etsy and who are happy with them.
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.
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