Here’s a good set…
Here’s a good set…
I’m happy to see that Microsoft will be removing the “Shared with Everyone” folder for new users.
I haven’t used it yet, but here are a few detailed reviews of it. It looks worth trying out.
You can sign up here for a 30 day trial.
I found this link that details the OOTB webparts for SharePoint 2013. This is a good starting point that could be developed into a document to help educate your users on the available capabilities in SharePoint 2013.
You’re going to quickly find out that you need access to run PowerShell commands against your online environment. This blog summarizes how to set it up.
Developing against SharePoint 2013 Online at its core is simple. It’s really following the same pattern you did in the past. You just need Visual Studio and SharePoint 2013 Online.
Where it gets complicated is understand all the dependencies that are involved. When I started this adventure I had Visual Studio 2010 and a new SharePoint 2013 Online account. Here’s the specifics behind what I actually ended up with.
Once you have all these components, you can start developing against SharePoint 2013 Online. My next blog will detail creating a project and deploying to your SharePoint 2013 Online developer site.
This is the start of my series that will take you through the steps needed and capabilities available when you develop against a SharePoint 2013 Online site. If you’re familiar with SharePoint 2013 Online, you know that the development model has changed. You can’t just follow the same practice you followed when developing against SharePoint 2010. At this point, I’m successfully developing, packaging and deploying solutions for SharePoint 2013 Online. Getting here was an adventure that involved reading many blogs, deciphering cryptic Microsoft articles and watching bad instructional YouTube videos. All I wanted to do was create SharePoint 2013 solution that would be deployed ONLY on SharePoint 2013 Online. I didn’t want to use Azure as the place that stored my code. I didn’t want to have some other external event receiver. I just wanted a solution that was solely in SharePoint 2013 Online. Sounds simple, right? It is now, but getting here was tough.
Part 2 will detail setting up your development environment and creating a place in SharePoint 2013 to develop against.
Thanks for reading.
Up until now, my blog has been focused solely on SharePoint 2010. This is changing. SharePoint is one of the technologies I work with, but I have others too. I’m going to start including my work with mobile, development methodologies and other technologies. Below are a few topics that I’ll start blogging about next year. Hopefully, I create some content that will help others.
I’ve spent the past few months looking for a “personal mobile platform” to quickly create apps. I’ve settled on http://appery.io/ for my first POC. I’m not looking at it from an enterprise corporate solution, but as an individual that would like to create an app. I’ll document the process from idea to launch of my application.
Over the years, I’ve worked on and managed teams using different development methodologies resulting in different levels of success. I would like to really research the effectiveness of the current methodology trends. Does a methodology ensure success? Do good people overcome bad methodologies?
What are the new capabilities?
Thanks for reading!
The default people picker settings aren’t optimized for you AD environment. Take a look here to see what your options are…