Of course, you have the option to virtualize everything yourself, maintaining this all-in-one mentality in your development environment. If you are already in the Windows 8 era, you might be able to use Hyper-V as the virtualization platform, but VMWare works quite well for this purpose too. If you put up your own environment, the set of required software is pretty much the same as before, only the version numbers and/or SP-versions differ. You still need a 64x
- Windows Server
- SQL server instance (for stand-alone, express is ok)
- SharePoint 2013 (currently Preview) pre-requisites
- SharePoint 2013 Server or Foundation
The lighter option for a development environment is now, as stated, the option to have SharePoint elsewhere - e.g. a remote installation within your company, or you can utilize SharePoint Online for this! SharePoint Online is pre-configured to support testing and debugging; if you use a remote installation of your own, some additional configuration is needed:
- the installation must be configured to use OAuth
- SharePoint Client Components the need to be installed on the target installation
- Visual Studio 2012 (can be installed side by side with VS2010)
- SharePoint 2012 development tools for SharePoint 2013 (actually tools for all Office development)
You might need to install .net framework 4.5 before the installation of Visual Studio 2012, at least I needed to. VS2012 should be compatible with any Windows version since XP and Server 2003, but all of the components that come with it may not be. The Office development tool require Win 7 to be on SP1 level. For full compatibility and support list, see Visual Studio 2012 compatibility page.
No comments:
Post a Comment