Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 386
  • Last Modified:

SharePoint 2013 Development Installation

Hello all - I have a few questions about a development environment I am putting together for SharePoint 2013 Business Intelligence development. Please see the environment details below:

- Host OS: Windows 8.1 Pro
- Host Applications: Office 365, Visual Basic Studio Professional, SQL Server 2014 Enterprise (with all features enabled);
- Host Hypervisor: VMware Workstation 10;
- Guess OS: Windows Server 2012 R2;
- Guess Applications: None, apart from SharePoint. I other words, the only application installed in the guess will be SharePoint 2013, with its shipping database (which I think is SQL Server 2008 Express edition).

The questions about this setup are:
1. Will this environment allow the configuration of SharePoint 2013 for Business Intelligence?
2. Will SharePoint Designer be available for developing PerformancePoint dashboards?
3. Will SharePoint Designer run in the Guess OS (or in the Host, where Microsoft Office products are actually installed).
4. Can the applications in the Host (Excel and Visual Studio) connect / work with the SharePoint 2013 Installation in the Guess?
5. Can web parts and reports built in Visual Studio (in the Host) be deployed to the SharePoint 2013 (in the Guess)?

Thanks!
0
Juan Villanueva
Asked:
Juan Villanueva
  • 2
1 Solution
 
Jamie McAllister MVPArchitectCommented:
1. Yes
2. Needs to be installed. Free download. Dashboard Designer will be your main tool though?
3. Could be either. Best practise is outside the SP server.
4. I tend to put Visual Studio in the VM in order to have references to the SharePoint DLLs etc. Excel should be able to interact with the VM if the VM DNS and virtual network settings have been done.
5. You can package these as WSP files from within Visual Studio and deploy remotely. However for development I'd tend to develop on the dev server instance itself. In this case, Visual Studio can do the deployment for you.
0
 
Juan VillanuevaAuthor Commented:
Jaimie - Sorry for my late reply and thanks for your answer.

Some follow up answers / questions:

1. Great!
2. Ok. No it will only be one of the tools I will using.
4. You made an interesting point. What are the benefits of having the SharePoint DLLs for reference? Do I miss those benefits if I choose developing on Microsoft SharePoint Online for Office 365?
5. Is remote deployment the norm when developers are developing on Microsoft SharePoint Online for Office 365?
0
 
Jamie McAllister MVPArchitectCommented:
Aha. When I saw your question I fixated on the SharePoint 2013 bit. Actually dev on Office 365 is different. You do not deploy compiled code to Office 365 and this changes the development paradigm. So you won't be putting Visual Studio anywhere near Office 365.

To deploy solutions to Office 365 you can use the new App Model. This allows you to create solutions that are mainly javascript/CSS/HTML based. Any compiled oart of the solution will exist on your own environment or in Azure (MS Dev Cloud).

http://msdn.microsoft.com/en-us/library/office/jj163980(v=office.15).aspx

For best effect you'll want an Office 365 Developer Site where you can cut code and try things out. You can get one here;

http://msdn.microsoft.com/en-us/library/office/fp179924(v=office.15).aspx

Remote deployment is the norm for solutions for O365. The Dashboard Designer and SharePoint Designer changes can be done in place - though it's best to try things out in another environment first if in doubt.
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now