Are there any plans for Monocross templates for VS2012 Currently I can only download the VS2010 ones.
Stackoverflow is really for questions and answers about code problems.
For issues about product roadmaps, you would be better off looking at the individual project discussion groups.
For monocross, this means asking:
their mailing list - https://groups.google.com/forum/?fromgroups#!forum/monocross-developers
their twitter account - https://twitter.com/Monocross_net
Related
I was wondering which is the best way to deploy our typical SharePoint artifacts such as list definitions, content types and site columns that we usually design in Visual Studio to a Office365 site collection.
I have been working on O365 for more than an year now and the only solution that I came up with is to create a sandboxed solution with no code and obviously deploy it to my site.
Unfortunately many clients nowadays don't even want to hear the word "sandboxed", so is there an alternative solution?
Thanks for the help!
The Office 365 Patterns and Practices has examples on how to do that:
https://github.com/OfficeDev/PnP
Mainly in https://github.com/OfficeDev/PnP/tree/master/Samples you will find all the items you are looking for.
https://github.com/OfficeDev/PnP/tree/master/Solutions/Provisioning.Framework.Cloud.Async contains a fully built solution with an xml based templating engine to fully provision sites/site collections.
Sandbox solutions are still very applicable, especially in O365 .CSOM with PowerShell is another viable alternative solution .This thread has discussed about this topic. Please refer to below article :
Programmatically creating Site Columns and Content Types using the App Model
Previously when provisioning list, libraries, site columns, content types, list definitions etc in SharePoint I typically used SharePoint features, deployed via a WSP - or used PowerShell scripts. This meant I had a package that could be deployed to DEV / TEST / PROD.
I'm working with SharePoint within Office 365 and unsure on the best way to provision lists / libraries / features within SharePoint.
Options:
No Code Sandboxed Solutions
Trying to avoid using these as the information from Microsoft on whether they are deprecated is flaky - however sandboxed solutions would allow me to deploy features with list definitions etc. I know sandboxed solutions with c# are definitely deprecated, but the info around no code solutions is poor.
Apps
I know apps can provision at both the app and host web level, but creating lists, libraries etc using the CSOM seems like a lot of effort and a step backwards.
PowerShell
The SP Online PowerShell is nowhere near as powerful as on-prem SP. I can provision site collections through this, but not lists or libraries...
I'm keen to know how other developers are deploying to Office 365, specifically around provisioning sites with specific list definitions, libraries, content types and so on...
Thanks
Microsoft did clarify the position on No Code Sandbox solutions - http://blogs.msdn.com/b/sharepointdev/archive/2014/01/14/deprecation-of-custom-code-in-sandboxed-solutions.aspx
Also if you are looking at using Powershell to deploy then you might want to go down the route of using CSOM from within PowerShell - SharePoint Client Browser for SharePoint 2013 is good for setting up a session also very good for viewing the content of a 365 tenant - http://spcb.codeplex.com/
I have been using code based provision for almost two years without any issues at all.
Server side model works just fine, CSOM has some limitation but stil cool one and JSOM could deliver the same feature set as both CSOM and SSOM, sorta 95% :)
PowerShell is not the best option as it hard to integrate into CI, put some unit testing and regressions.
As you mentioned, this is "step back", but if only you don't have any framework or foundation for that. My libraries are internal one, but there is SPGenesis at codeplex and SPMeta2.
As community don't really care, need or with such libraries for provisioning (yep, let's face it), there are much such libraries at all, but there are lots of "MVP" samples sorta "hello world" level.
Finally, what I would suggest is to invest your time and effort in code based provision.
This is a future, that's it ;)
UPD
Struggling with SharePoint's API inconsistency, bugs, "by-design" behaviour, unaffordable amount of time to write, support and upgrade WSP packages and XML, a team of passionate SharePoint professionals decided to come up with robust, testable and repeatable way to deploy such artifacts like fields, content types, libraries, pages and many more.
Enjoy and let us know how it goes.
SPMeta2 at GitHub
SPMeta2 at Nuget
SPMeta2 Documentation Wiki
SPMeta2 Bugtracker
I am starting to do a lot of sharepoint development lately, and some of the things that I have done and I dont like is to use sharepoint designer directly for things like pagelayouts, lists definitions, master pages, etc.
From my point of view I think its more organized to do everything in Visual Studio. In that way you can connect each solution to a source control database and deploy/retract/upgrade easier with scripts.
My idea is to create a vs solution like this:
1. One for list and content type defintions.
2. One for webparts.
3. One for branding
but maybe this approach has any disadvantage, what other approaches are you using?
The real answer is going to be: it depends.
I do not think there is one best way to organize a Visual Studio solution or SharePoint solution packages. In the end, you need to find what works best for your organization and go with that.
The only guidance I have seen is from the SharePoint Online documentation:
If the development team is designing a solution that requires more than 10 WSP files, the team should reconsider its architecture. It is difficult to manage and deploy so many WSP files within a single deployment window, and the solution risks rejection because of the complexity for SharePoint Online of managing it.
A large number of solution packages (WSP files) that need to be tracked and managed pose a challenge for deployment. The more solution packages in a customization, the greater the possibility that something will not be installed correctly, the longer the solution will take to deploy, and the easier it is to mix incompatible versions of solution packages. We recommend that customers scrutinize their deployment plans and keep the number of solution packages to the minimum number needed for the project. Keep in mind that a solution package can contain several features, so there is no necessity to have one solution package for each feature.
And I would agree with this. You seem to be outlining 3 Visual Studio solutions and/or SharePoint solution packages for what really are 3 Features within a single SharePoint solution package.
I tend to create one Visual Studio solution for each project. For a very large project, that single Visual Studio solution might contain several projects where each represents a SharePoint solution package.
For Farm solutions, each SharePoint solution package will contain a number of Features and files that are all related in terms of functionality or application. If two or more SharePoint solution packages share common Features, I will put those shared Features into a separate solution package.
Sandbox solutions tend to be much smaller than Farm solutions. While my Farm solutions usually represent an application, my Sandbox solutions are more focused to solve one particular issue. So my Sandbox solutions usually only contain one Feature that does not rely on other custom Features or solutions.
As I said in the beginning, I do not believe there is one hard or fast rule. It is usually determined by the preferences and style of a particular development team. Try a couple different ways in the beginning and eventually you will find what fits your team best.
I recently started at a new job where I'll be working with Sharepoint 2010 to set up (or actually upgrade) an intranet. Unfortunately, I have no experience with SP2010, and the last time I touched SP2007 (or a virtual server for that matter) was four years ago.
I'll be attending a course soon, but until then I have to make myself useful. I've already managed to install a working Sp2010 server and have played around with some web applications and site collections, and trying to find out how Sharepoint Designer works, but I don't really have an idea what I'm doing or what goals I should set for myself to actually learn useful stuff.
I've also watched some tutorials, but most are really problem-specific (problems I don't have yet) or dive into the code (which I won't, probably).
So.. where to start?
There are a lot of great training videos on Channel9.
Sahil Malik's book is organized as what are the basic things all SharePoint 2010 developers need to know. http://www.amazon.co.uk/Microsoft-SharePoint-2010-Solutions-Professionals/dp/1430228652/ref=sr_1_1?ie=UTF8&s=books&qid=1283973447&sr=8-1
It is a good place to start.
I would suggest video tutorials because:
They are FREE!
They give you more context than just reading what to do.
A quick search will get you specific topics.
Check out Bing videos on SharePoint 2010. There's lots of great content out there to get you going fast.
when i started with SP2010, i began by searching:
New features in Lists and Document
Libraries New search capabilities
DocumentSets (they are very interesting!)
Office Web Apps (Excel and Word web access)
A little bit of FAST Search Engine
Integration with silverlight
Changes in the object model
Workflows
New tools in VS2010
(MSDN, codeplex, codeproject, stackoverflow, and several blogs from Sharepoint MVPs are good places to look for)
I don't know if this would help but that's where I started.. if you need specific help you can find several groups in linkedin.. there are a lots of MVPs helping..
Good luck!
I would recommend you to check out the SharePoint guidance on codeplex. It comes with at sample portal application that is explained and with best practices and guidance for creating a SharePoint site. I am sure that this will provider vital information and knowledge for your project.
Kr., Bernd.
Follow the below link to learn sharepoint. It contains sharepoint tutorial videos and all.
http://www.fastsharepoint.com/
Basically i started my sharepoint learning with the following examples:
Create a feature to change site title
Create a feature to change site theme
Create a feature with feature stapling
Create a feature that activates another feature
Create a site through code
Create a list through code
Populate a list with data through code
Create a lookup column in list through code
These are the basic examples that you can understand what is Sharepoint as a beginner.
Please see the below link for more beginner programs:
http://blog.sharepointhosting.com/Downloads/SharePoint-Tutorials.aspx
Litso install a dev box on you machine and get started.
Try doing some migration from one server to the other.
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 9 years ago.
Improve this question
I'm starting a new job involving Sharepoint design/development. While the job will involve training courses on Sharepoint and other technologies I haven't used, I am interested to get a headstart and learn a little more about Sharepoint.
Are there any good articles explaining Sharepoint development and what I need to know (being a beginner in the technology)? I am strong with C# and ASP.NET as I use it everyday (job or no job), it's just the Sharepoint specific stuff I wonder. I am checking out MSDN. I did check out some other threads on this, but I am not really looking for a book.
A better question would be what blogs are there which focus on code snippets and best practises?
Thanks
There are lots of SharePoint virtual labs. They are good b/c they let you get your hands on the technology without too much of the setup hassle. :)
http://www.microsoft.com/click/SharePointDeveloper/html/Default.html
This site has the information I started with when learning SharePoint: webcasts from TechEd by Andrew Connell and Rob Bogue and the hands-on-labs that go along with them.
There are very many SharePoint MVPs that have blogs that are easy to find and many of them hang around on twitter so it's easy to get help.
http://andrewconnell.com/blog/archive/2008/11/25/Free-MSDN-Webcasts-amp-HOLs-for-MOSS-2007-WCM-Development.aspx has info on some newer webcasts
http://www.sharepointpodshow.com/ and http://www.methings.com/podcast/70342/MOSS-Gone-Wild.php
are 2 excellent SharePoint Podcasts.
A few months ago I was looking for decent SharePoint articles just to get an introduction to the technology. I found an entire section on CodeProject dedicated to it. Check it out if you haven't already, I found a number of good articles there.
Also, check out the SharePoint dev wiki
In addition to all the links provided by others:
Microsoft has a Best Practices Resource Center for SharePoint Server 2007 on Technet
The official SharePoint Team Blog has some good info.
Sharepoint Joel has a list of Top 100 SharePoint blogs, though a year old provides a good starting point of blogs to look at.
Several MSDN articles such as:
Disposal Best Practices
Common Coding Issues using the SharePoint Object Model
Edit: Also just noticed that the Patterns & Practices team has a SharePoint Guidance project on codeplex.
Sharepoint was a disaster for me (as I've said before), but I'd be willing to give it another try once .Net 4.0 and VS 2010 are released.
I would definitely download the VS 2010 beta and give the new Sharepoint integration a spin. I hear that it is a big improvement over what we have now.
As for documentation, msdn was the best learning resource I could find. It was more concise than what you will get with most books, although books usually provide a storyline and cohesive progression of learning.
Hope that helps, Good luck.
Codeplex is good for examples of developement. Given the rate of change with "best practices" I have seen some books that have become out of date quite rapidly.
I personally have gained a lot of valuable knowledge from looking at questions on forums like this one, trying to replicate the issue on a developement VM. I would recommend having a VM for "play" as hands on will run you up against many of the strengths and weaknesses with different approaches.
If you can get a backup of an existing content database you are using, having lots of documents and document libraries is good for hitting real data and trying out different search configurations etc.
One additional site you shouldn't forget is myrampup.com. It's a community-based training site which will help you get the knowledge you need to develop solutions on the SharePoint platform.
Before learning SharePoint development, learn what SharePoint can do. Use it and become familiar with its features. Many people's first thought is to develop new features when much of what they want to do can be done with existing SharePoint features. It's a huge, complex product.
I've found some very good videos for learning Sharepoint at Point8020
Very good reference for SharePoint Object Model:
http://www.etechplanet.com/post/2009/08/28/Overview-of-SharePoint-Object-Model.aspx
A good starting resource is the Microsoft RampUp Site it's a free resource that has 2 tracks for SharePoint for developers. Each track consists of articles, slide casts and virtual labs to help you gain an understanding of what goes into developing for SharePoint. They are not all inclusive but it should give you a good starting point.
There is also a user centric overview on the Microsoft Office Site for SharePoint 2007 that can help get you an understanding of some of the features in SharePoint.
I don't know if any of the resources have been update yet for SharePoint 2010, but hopefully those will follow soon.
Also check Microsoft Learning with SharePoint 2010 around the corner you might find free courses. Microsoft usually releases free online courseware for new products around the time of release.
For uo to date announcements check out the SharePoint Team blog, usually there's lots of good information around there.
Good Luck.